Feature request: A multi-container, one process per container, deployment of PMM3

[laundmo]

Description

Currently, PMM3 runs many services in a single container, including its own nginx, multiple databases, etc. This makes it a lot harder to adjust a deployment of PMM3 to the needs of a specific situation. See #3954 for one case where, if PMM3 was a collection of single-process containers like so many other services, there would not have been any issue.

Suggested solution

I suggest documenting, or maybe making possible if it is not currently possible, a deployment of PMM3 which consists of many interconnected containers.
There would ideally be individual containers for: pmm-manged, pmm-agent, grafana, clickhouse, clickhouse-watchdog, victoriametrics, vmalert, vmproxy, nginx, and probably more. I dont exactly know PMM3 very well, i just failed to get it working for the first time, so i just read the list of processes docker compose top shows me.

Additional context

Once services become complex and need multiple different tools to run, i've only ever seen a split across multiple containers. PMM3 is the first time i've come across a single container running many big processes.

I'd love to just have a docker-compose.yml i can adjust, or hell, maybe even a nix flake at some point.

Code of Conduct

• I agree to follow this project's Code of Conduct