MacOS本地PostgreSQL占5432端口，Docker Compose映射同端口为何未报错？

Great question—this is a common gotcha with Docker on macOS, and it boils down to a few key details about how network bindings and Docker Desktop operate under the hood:

• Your local PostgreSQL is probably only bound to localhost
  By default, most PostgreSQL installs on macOS are configured to listen only on the 127.0.0.1 (localhost) interface, not all available network interfaces (0.0.0.0). When you set ports: "5432:5432" in your docker-compose.yml, Docker automatically binds to 0.0.0.0:5432 (all interfaces) on your host. Since 127.0.0.1:5432 and 0.0.0.0:5432 are technically distinct bindings (even though they share the same port number), there’s no actual conflict here. You can confirm this by running lsof -i :5432 in your terminal—look for the LISTEN entries; if your local PostgreSQL shows 127.0.0.1:5432 and Docker shows *:5432 (shorthand for 0.0.0.0:5432), that’s exactly what’s happening.

• Docker Desktop runs in a hidden virtual machine
  Unlike Docker on Linux, which runs directly on the host kernel, Docker on macOS uses a lightweight HyperKit VM to host the Docker daemon. When you map a port, the traffic flows like this: Mac host → VM → container. Even if your Mac’s port 5432 is occupied, the VM’s port 5432 might still be free, so Docker can successfully map the VM’s port to the container. The failure to forward traffic from your Mac to the VM won’t trigger an error during docker-compose up—you’ll only notice it when you try to connect to the container’s PostgreSQL via localhost:5432 (you’ll end up hitting your local instance instead).

• Port conflict detection isn’t always strict
  Docker Desktop for Mac doesn’t always catch port conflicts during startup as aggressively as Linux does. The daemon might not fully check all host interfaces for the port, so it proceeds to launch the container even if part of the port mapping fails. The issue only becomes obvious when you try to access the container’s service and find it unreachable.

To test this out for yourself, try these steps:

1. Run lsof -nP -i :5432 | grep LISTEN to see which processes are listening on port 5432 and which interfaces they’re bound to.
2. Try connecting to your container’s PostgreSQL using your Mac’s external IP address (e.g., psql -h <your-mac-ip> -U admin). If this works but psql -h localhost -U admin connects to your local instance, that confirms the interface binding difference.
3. If you want to force a conflict, reconfigure your local PostgreSQL to listen on 0.0.0.0 (edit postgresql.conf and set listen_addresses = '*'), restart it, then run docker-compose up again—this time you should see an error about the port being already in use.

内容的提问来源于stack exchange，提问作者Kurt Peek