What does docker:cannot_connect_to_daemon mean?

The Docker CLI cannot reach the Docker daemon, usually because the engine is stopped, the context is wrong, or the socket is unavailable.

How can I manually validate docker:cannot_connect_to_daemon?

On Linux, check socket permissions: `ls -la /var/run/docker.sock`. Confirm your user groups include `docker` (then re-login): `groups`.

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

Q: How do I prevent docker:cannot_connect_to_daemon in CI?

Keep Docker Desktop / Docker Engine updated on build machines. Avoid hardcoding `DOCKER_HOST` unless you truly need remote contexts. Monitor daemon health on CI runners.

Fix it fast

Most likely: Docker itself is not reachable from this shell: the daemon is stopped, Docker Desktop is still starting, or the CLI is pointed at the wrong context or DOCKER_HOST.

Confirm this is your error

Match the output and confirm you are troubleshooting the same failure.

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

Check the cause

Run focused checks to identify what is failing in this environment.

docker version
docker context show
docker context ls
echo "$DOCKER_HOST"

Apply the safe fix

Use the smallest safe change that addresses the confirmed cause.

# Docker Desktop: start Docker Desktop and wait until it reports that Docker is running.

# Linux systemd hosts:
sudo systemctl start docker

# If the CLI is pointed at the wrong daemon, return to the default local context.
docker context use default
unset DOCKER_HOST

Verify it works

Repeat the relevant checks and confirm the original error is gone.

docker info
docker version

Avoid unsafe shortcuts

Keep security and data protections in place while troubleshooting.

Do not troubleshoot image names, tags, or registry credentials until docker info can reach the daemon.
Do not use sudo docker ... as the long-term fix for a normal user setup, fix group or socket access instead.
Do not leave a stale DOCKER_HOST value in your shell or CI job if you no longer use that remote daemon.

What Docker Could Not Reach

Read this as a precise clue about which part of the workflow broke first. Once you know the failing layer, the fix path gets much shorter.

Restore Docker daemon access

Check daemon connectivity:docker version (server section should appear).

If Docker is not running, start/restart it (Docker Desktop, or sudo systemctl start docker).

Check active context:docker context ls and docker context show

If using a remote daemon, validate DOCKER_HOST and TLS settings.

Check the daemon endpoint and socket

On Linux, check socket permissions with ls -la /var/run/docker.sock, and confirm your user groups include docker (then re-login): groups.

Why It Happens

Usually this comes down to the Docker daemon is not running, you are pointing at the wrong Docker context/host (DOCKER_HOST / context mismatch), or you do not have permission to access the Docker socket.

Prove the Failing Environment Can Reach It

Run docker info and confirm it returns daemon details, and retry the original Docker command.

How Docker reaches the daemon

The Docker CLI is a client that talks to the Docker daemon via a Unix socket or TCP. When the daemon is down, unreachable, or blocked by permissions, the CLI fails immediately.

Prevent It From Coming Back

To prevent this, keep Docker Desktop / Docker Engine updated on build machines, avoid hardcoding DOCKER_HOST unless you truly need remote contexts, and monitor daemon health on CI runners.