> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Troubleshooting Docker Daemon
> This article provides steps to diagnose and resolve issues when Docker commands fail to communicate with the Docker daemon.
When Docker commands fail to communicate with the Docker daemon, follow these steps to diagnose and resolve the issue.
## 1. “Cannot connect to the Docker daemon” Error
If you encounter:
```bash theme={null}
$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```
the Docker Engine service (daemon) isn’t reachable. Determine if you’re targeting a local socket or a remote host.
### a. Remote Access via `DOCKER_HOST`
Set the `DOCKER_HOST` environment variable to point at your remote Docker endpoint:
```bash theme={null}
export DOCKER_HOST="tcp://192.168.1.10:2376"
docker ps
```
| Port | Encryption | Description |
| ---- | ---------- | ------------------- |
| 2375 | None | Unencrypted traffic |
| 2376 | TLS | Secure, encrypted |
When using port 2376, ensure you have valid certificates configured on both client and server.
If the error persists, SSH into the remote host and check the Docker service status.
## 2. Checking the Docker Service Status
On most Linux distributions with `systemd`, Docker runs as a service. Verify its state:
```bash theme={null}
sudo systemctl status docker
```
A healthy daemon appears as:
```plaintext theme={null}
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: active (running) since Wed 2020-10-21 04:21:01 UTC; 3 days ago
Docs: https://docs.docker.com
Main PID: 4197 (dockerd)
Tasks: 13
Memory: 130M
CPU: 9min 6.980s
CGroup: /system.slice/docker.service
└─4197 /usr/bin/dockerd -H fd:// -H tcp://0.0.0.0 --containerd=/run/containerd/containerd.sock
```
If you see **inactive** or **dead**:
```plaintext theme={null}
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: inactive (dead) since Sat 2020-10-24 07:42:08 UTC; 21s ago
Docs: https://docs.docker.com
Process: 4197 ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0 --containerd=/run/containerd/containerd.sock (code=exited, status=0/SUCCESS)
```
Start or restart the service:
```bash theme={null}
sudo systemctl start docker
```
## 3. Inspecting Service Logs
Use `journalctl` to pinpoint errors and warnings:
```bash theme={null}
sudo journalctl -u docker.service --since "1 hour ago"
```
Example log excerpt:
```plaintext theme={null}
Oct 21 04:05:42 ubuntu-xenial systemd[1]: Starting Docker Application Container Engine...
Oct 21 04:05:42 time="2020-10-21T04:05:42.565Z" level=info msg="parsed scheme: \"unix\""
Oct 21 04:05:42 time="2020-10-21T04:05:42.847Z" level=warning msg="Your kernel does not support cgroup cfs"
Oct 21 04:05:43 time="2020-10-21T04:05:43.873Z" level=error msg="Error (Unable to complete operation)"
```
Adjust the `--since` flag to narrow down log entries for faster troubleshooting.
## 4. Verifying Daemon Configuration
Inspect `/etc/docker/daemon.json` for JSON syntax errors or conflicting settings:
```json theme={null}
{
"debug": true,
"hosts": ["tcp://192.168.1.10:2376"],
"tls": true,
"tlscert": "/var/docker/server.pem",
"tlskey": "/var/docker/serverkey.pem"
}
```
A conflict between daemon flags (in `daemon.json`) and CLI or systemd overrides can prevent Docker from starting. Remove duplicate host or TLS settings.
After any change, reload and restart:
```bash theme={null}
sudo systemctl daemon-reload
sudo systemctl restart docker
```
## 5. Ensuring Sufficient Disk Space
Docker stores images, containers, and volumes under `/var/lib/docker`. A full filesystem can crash the daemon.
1. Check disk usage:
```bash theme={null}
df -h
```
Example:
```plaintext theme={null}
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 14.7G 15M 99% /
tmpfs 369M 0 369M 0% /dev/shm
```
2. Clean up unused resources:
```bash theme={null}
docker container prune # remove all stopped containers
docker image prune # remove dangling images
```
| Command | Description |
| ------------------------ | -------------------------------- |
| `docker container prune` | Delete stopped containers |
| `docker image prune` | Remove dangling or unused images |
| `docker volume prune` | Clean up unused volumes |
Pruning operations are irreversible. Use `docker system df` to preview reclaimable space.
## 6. Examining System Information and Events
Once the daemon is running, validate your environment:
```bash theme={null}
docker system info
```
Sample output:
```plaintext theme={null}
Client:
Debug Mode: false
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 19.03.5
Storage Driver: overlay2
Backing Filesystem: xfs
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
```
To view real-time Docker events (container lifecycle, network changes, etc.):
```bash theme={null}
docker system events
```
## Further Reading
* [Docker Engine overview](https://docs.docker.com/engine/)
* [Docker daemon.json reference](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file)
* [Docker CLI commands](https://docs.docker.com/engine/reference/commandline/cli/)
* [Managing Docker storage](https://docs.docker.com/config/pruning/)
With these steps—verifying connection methods, service status, logs, configuration, disk space, and system information—you can reliably troubleshoot Docker daemon issues.