DevOps & Docker · Developer Error Resolution Lab

Fix Docker Error: 'Bind for 0.0.0.0:port failed: address already in use'

Identify and terminate conflicting host processes or adjust Docker port mapping to resolve port bind collisions.

Fix Guide:

Triggered Error Message:

Error response from daemon: driver failed programming external connectivity on endpoint web: Bind for 0.0.0.0:5432 failed: port is already allocated

Customize Solution for Your Environment

Conflicting Host Port

Alternative Host Port

Container Internal Port

# Step 1: Find which process is locking port 5432
# Linux / macOS:
lsof -i :5432
# Windows (PowerShell):
Get-Process -Id (Get-NetTCPConnection -LocalPort 5432).OwningProcess

# Step 2: Stop existing Docker containers holding the port:
docker stop $(docker ps -q --filter "publish=5432")

# Step 3: Or remap to non-conflicting host port 5433 in docker-compose.yml:
services:
  app:
    ports:
      - "5433:5432"

Root Cause & Mechanism Analysis

Why does this error occur?

A local service running on the host OS (such as local PostgreSQL, Nginx, Apache, or a previous unstopped Docker container) is already bound and listening to the requested host port.