Docker Core
The Docker CLI reached no daemon, so every command stops before doing any work.
cannot-connect-to-the-docker-daemonReviewed for reference consistency: August 11, 2026
The Docker CLI reached no daemon, so every command stops before doing any work.
What cannot-connect-to-the-docker-daemon Means
The cannot-connect-to-the-docker-daemon error on the Docker Core indicates the docker cli reached no daemon, so every command stops before doing any work.. This typically occurs due to the docker daemon service is stopped or failed during boot.
The docker binary is a client that forwards every request to a background daemon over a Unix socket or a TCP endpoint. When the socket file is missing, the daemon process is stopped, or DOCKER_HOST points at an unreachable host, the client prints this message and exits without attempting anything.
How to fix cannot-connect-to-the-docker-daemon
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Ask Docker itself whether an engine answers
The info command is the engine-agnostic liveness probe; a working daemon replies with system details, a dead one reproduces the error.
docker infoShow both sides of the client-server split
The version output lists client and server sections separately; an empty or missing Server block confirms the client has no daemon connection.
docker version
Technical Background
This message is a transport failure, not a verdict about images or containers: the client never got a response because no daemon answered on the endpoint it tried.
The endpoint is printed in the error itself, most often unix:///var/run/docker.sock on Linux. Desktop products and rootless installs keep their sockets under user-specific paths, and remote workflows replace the socket with a TCP URL or an SSH-based context.
Because the failure sits below every Docker feature, the same line can appear for any subcommand, which makes it among the most frequently reported Docker messages overall.
Common Causes
- The Docker daemon service is stopped or failed during boot
- The daemon socket path printed in the error does not exist on this host
- DOCKER_HOST or the active context routes the client to an unreachable remote engine
- Rootless or Desktop installs keep the socket at a nonstandard path the client is not using
Typical Scenarios
- Running docker ps on a machine where the Docker service was never started
- A CI job executing docker commands inside a container that never received the daemon socket
- A terminal session where DOCKER_HOST still points to a retired remote engine
What to Know
The fastest observation is whether the failure is total or partial: when every docker command returns this line, the daemon endpoint is wrong or the engine is down; when only remote-targeted commands fail, the local engine is fine and the context selection is the moving part.
Frequently Asked Questions
Common questions about Docker cannot-connect-to-the-docker-daemon error
They were not. Container state lives on the daemon side and survives client-side connection failures; once the engine is reachable again, prior containers reappear in listings.
The CLI prints the endpoint it actually attempted, which follows DOCKER_HOST and the active context; a tcp:// line means the session is targeting a remote engine rather than a local socket.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems