Cannot connect to the Docker daemon & Port is already allocated

[aditi5050]

Discussion Type

Question

Discussion Content

Port is already allocated and Cannot connect to the Docker daemon

[aditi5050]

1. Cannot connect to the Docker daemon

What it means

The Docker CLI (docker) is trying to communicate with the Docker daemon (dockerd), but it cannot reach it.

Think of Docker as having two parts:

• Docker CLI → the command you type (docker run, docker ps)
• Docker Daemon → the background service that actually creates and manages containers

If the daemon isn't running or accessible, Docker commands fail.

Example Error

Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
Is the docker daemon running?

Common Causes

1. Docker service is not running

Linux:

sudo systemctl status docker

Start it:

sudo systemctl start docker

Windows/Mac:

• Docker Desktop is closed.
• Docker Desktop is still starting up.

2. Permission issue

You may not have permission to access Docker's socket.

Error:

permission denied while trying to connect to the Docker daemon socket

Check:

ls -l /var/run/docker.sock

Add your user to the Docker group:

sudo usermod -aG docker $USER

Then log out and back in.

3. Docker daemon crashed

Check logs:

sudo journalctl -u docker

You might find:

• disk full
• configuration errors
• startup failures

Real-world Scenario

You open a terminal and run:

docker ps

Output:

Cannot connect to the Docker daemon

You check:

systemctl status docker

Result:

inactive (dead)

Start Docker:

sudo systemctl start docker

Now:

docker ps

works correctly.

---

2. Port is already allocated

What it means

A container is trying to use a host port that is already being used by another process.

A host machine can only have one process listening on a specific port.

Example Error

docker: Error response from daemon:

Bind for 0.0.0.0:8080 failed:
port is already allocated.

Why it happens

Suppose you start a container:

docker run -p 8080:80 nginx

Meaning:

Host Port 8080  ---> Container Port 80

Docker reserves port 8080 on your machine.

Now you try to start another container:

docker run -p 8080:80 apache

Docker cannot use 8080 again.

Result:

port is already allocated

---

How to find what's using the port

Linux

sudo lsof -i :8080

or

sudo netstat -tulpn | grep 8080

Example:

docker-proxy  12345  LISTEN  8080

Another container is already using it.

---

Check Docker containers

docker ps

Example:

CONTAINER ID   IMAGE   PORTS
abc123         nginx   0.0.0.0:8080->80/tcp

Stop it:

docker stop abc123

---

Use a different port

Instead of:

docker run -p 8080:80 myapp

Use:

docker run -p 8081:80 myapp

Now:

http://localhost:8081

will reach the container.

---

Real-world Scenario

You have a Node.js application:

docker run -p 3000:3000 my-node-app

It works.

Later you start another copy:

docker run -p 3000:3000 my-node-app

Docker returns:

Bind for 0.0.0.0:3000 failed:
port is already allocated

Because the first container is already using port 3000.

Solutions:

docker stop <container-id>

or

docker run -p 3001:3000 my-node-app

---

Quick way to remember

Cannot connect to Docker daemon

Ask:

"Can my Docker command reach the Docker service?"

Check:

docker info
systemctl status docker

Port is already allocated

Ask:

"Is someone already using this port?"

Check:

docker ps
lsof -i :PORT

These two errors alone account for a large percentage of beginner Docker troubleshooting sessions.