Docker / Docker

Docker bind: address already in use

Fix Docker bind address already in use errors by finding the host process or compose stack occupying the port, then stopping it or remapping the host port.

General troubleshooting guidance Last updated May 10, 2026 0 sources Needs local verification

Category: Docker
Error signature: bind: address already in use
Quick fix: Find the process or container using the host port, stop it if appropriate, or change the host-side port mapping such as 3001:3000.
Updated: May 10, 2026
Verification status: General troubleshooting guidance
Evidence: 0 public source URLs

Before you change production

This page does not expose source URLs in the page body. Treat it as general troubleshooting guidance and verify against official documentation before changing systems.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Docker, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

bind: address already in use means Docker tried to publish a container port onto a host port that is already occupied. The conflict is on the host machine, so the fix is to find the process or older compose stack using that port, then stop it or map the container to a different host port.

Why this happens

Port publishing uses the host network namespace. If another process already owns localhost:3000, 0.0.0.0:5432, or any other requested host port, Docker cannot bind that address for the new container.

For Docker bind: address already in use, focus on host port ownership and compose state. Docker daemon health, disk usage, and image contents are usually secondary unless other Docker commands also fail.

Common causes

Host port is already used by another local process
An old Docker Compose stack is still running
Another container already publishes the same host port
Compose maps multiple services to the same host port

Quick fixes

Read the error line and identify the host port Docker tried to bind.
Run lsof -i :3000 with the actual port from the error.
Stop the old process or compose stack that owns the port.
If both services must run, change the left side of the compose port mapping, such as 3001:3000.

Copy-paste commands

List running containers with published ports

docker ps --format "table {{.Names}}\t{{.Ports}}\t{{.Status}}"

Check compose services in this project

docker compose ps

Find the process using port 3000

lsof -nP -iTCP:3000 -sTCP:LISTEN

Stop the current compose stack

docker compose down

Check whether Docker itself is reachable

docker info

Real-world fixes

A previous docker compose up may still be running from another terminal. Run docker compose ps in the project before starting a second stack.
Local dev servers commonly occupy ports like 3000, 5173, 8000, and 8080. Stop the dev server or remap the Docker host port.
For databases, avoid deleting volumes just to free a port. Stop the container first; the volume may contain local data.

Step-by-step troubleshooting

Find the port mentioned near bind: address already in use; it is usually shown as the host-side bind address.
Run docker ps --format "table {{.Names}}\t{{.Ports}}\t{{.Status}}" to see whether another container already publishes that port.
Run lsof -nP -iTCP:<port> -sTCP:LISTEN or the platform equivalent to find non-Docker processes.
Stop the old container, compose stack, or local process that owns the port.
If the port is intentionally in use, change only the host side of the mapping, for example 3001:3000, then retry docker compose up.

Platform-specific fixes

macOS

Use lsof -nP -iTCP:<port> -sTCP:LISTEN to find apps, dev servers, or Docker Desktop proxies holding the port.

Linux

Use ss -ltnp | grep :<port> when lsof is unavailable, then stop the owning service with the normal service manager.

Windows

Use netstat -ano | findstr :<port> in PowerShell or Command Prompt, then match the PID in Task Manager.

How to prevent it

Reserve predictable host ports per project and document them in the compose file.
Run docker compose down when switching branches or projects that publish the same ports.
Use project-specific compose project names when running multiple stacks at once.

Diagnostic flow for this page

Match bind: address already in use exactly before applying the quick fix.
Compare the failing environment with Docker versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does bind: address already in use mean in Docker?

bind: address already in use indicates the workflow described by "Docker bind: address already in use" failed in a Docker context. Start by confirming the exact signature and the component that emitted it.

What should I check first for bind: address already in use?

Check whether this cause matches your environment: Host port is already used by another local process

Is the bind: address already in use guidance source-backed?

The "Docker bind: address already in use" page is labeled general troubleshooting guidance. It has no public source URLs in the current Markdown record, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for bind: address already in use?

For "Docker bind: address already in use", avoid applying "Find the process or container using the host port, stop it if appropriate, or change the host-side port mapping such as 3001:3000." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging bind: address already in use?

For "Docker bind: address already in use", collect the failing Docker command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.