Port conflict when running docker compose with local PostgreSQL instance

[Syedowais312]

When running docker compose -f ./docker/docker-compose.yml up --detach, if a local PostgreSQL instance is already running on port 5432, the setup fails with:

failed to bind host port 0.0.0.0:5432/tcp: address already in use

This is a common scenario for developers who have PostgreSQL installed locally. The user has to manually stop their local instance (sudo systemctl stop postgresql) to proceed, which is not obvious.
Possible fixes I'm considering:

• Add a comment in compose.postgres.yml documenting the conflict and how to resolve it
• or may be use ${PGWATCH_POSTGRES_PORT:-5432}:5432 with a wrapper script in docker/scripts/ that auto-detects port conflicts and sets the env var before invoking compose

Would love to hear your thoughts on this.

CC: @pashagolub @0xgouda

[pashagolub]

Not a bug. Just know what you're doing.