What causes "Error: Bind for 0.0.0.0:3000 failed: port is already allocated"?

Another Docker container is already using the same port A local development server (Node.js, Nginx, etc.) is running on that port A previous Docker container wasn't properly stopped

Docker Error3 Fixes Available

Docker: Bind for 0.0.0.0:PORT failed — port is already allocated

Error: Bind for 0.0.0.0:3000 failed: port is already allocated

What does this error mean?

Docker cannot bind to a port that is already in use by another process on your host machine. Either another Docker container or a local process is already listening on that port.

Common Causes

Another Docker container is already using the same port
A local development server (Node.js, Nginx, etc.) is running on that port
A previous Docker container wasn't properly stopped

How to Fix It (3 Solutions)

Find what is using the port

Use lsof or netstat to identify the process.

Code

# On Linux/Mac
lsof -i :3000

# On Windows
netstat -ano | findstr :3000

Stop the conflicting Docker container

List running containers and stop the one using the port.

Code

docker ps
docker stop <container-id>

Use a different host port

Map to a different host port in your docker run command.

Code

# Map host port 3001 to container port 3000
docker run -p 3001:3000 your-image

Fix this error faster with our free tool

Docker Run to Compose Converter

Open Docker Run to Compose Converter

Related Errors

Docker

Error: Bind for 0.0.0.0:PORT failed — port is already allocated

View fix

Docker

Error: no space left on device

View fix

Docker

Got permission denied while trying to connect to Docker daemon socket

View fix

Browse all error fixes