Cannot Connect to the Docker Daemon— Causes, Fixes, and Troubleshooting Guide
DevOps
Last Updated: Jul 22, 2026
Total View: 90
Docker Daemon Not Responding on Your System?
If Docker cannot connect through docker.sock, the daemon may be stopped, permissions may be incorrect, or the service may be misconfigured. Fix the root cause and get your containers running again.
- Docker service status check
- Socket permission fixes
- User group configuration
- Daemon startup troubleshooting
The “Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” error is one of the most common issues Docker users encounter on Linux, macOS, and Windows (via WSL). It indicates that the Docker CLI cannot communicate with the Docker daemon (Docker Engine), which is responsible for building, running, and managing containers.
This error can occur because the Docker service is stopped, the current user lacks permission to access the Docker socket, the Docker daemon failed to start, the socket file is missing, or the Docker context is misconfigured.
In this guide, you’ll learn what this error means, its common causes, step-by-step solutions, platform-specific fixes, and best practices to prevent it.
What Does “Cannot Connect to the Docker Daemon” Mean?
Docker consists of two main components:
- Docker Client (CLI) – Executes commands like docker run, docker ps, and docker build.
- Docker Daemon (dockerd) – Runs in the background and manages containers, images, networks, and volumes.
When you execute a Docker command, the CLI communicates with the daemon through the Unix socket:
/var/run/docker.sock
If the daemon isn’t running or the client cannot access this socket, Docker returns:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
Is the docker daemon running?
Why Does This Error Occur?
Several factors can prevent the Docker CLI from communicating with the daemon. Identifying the root cause is the first step toward resolving the issue.
Docker Service Is Not Running
The most common reason is that the Docker daemon is simply stopped.
Without the daemon running, every Docker command fails because there is no process listening on the Docker socket.
Docker Was Not Installed Correctly
An incomplete or corrupted Docker installation may leave the daemon unavailable.
This sometimes occurs after interrupted package installations or partial upgrades.
Insufficient User Permissions
The Docker socket belongs to the root user.
If your user isn’t part of the docker group, you’ll receive permission-related connection errors.
Docker Socket Is Missing
The socket file:
/var/run/docker.sock
is automatically created when Docker starts.
If the daemon fails during startup, this socket may never be created.
Docker Context Is Incorrect
Docker supports multiple contexts.
If the current context points to a non-existent daemon, the CLI cannot establish a connection.
How to Fix “Cannot Connect to the Docker Daemon”?
Follow these troubleshooting steps in order.
Step 1: Check Whether Docker Is Running
Linux:
sudo systemctl status docker
If running, you’ll see:
Active: active (running)
If stopped:
Active: inactive (dead)
Step 2: Start the Docker Service
If Docker isn’t running:
sudo systemctl start docker
Verify:
sudo systemctl status docker
Enable automatic startup:
sudo systemctl enable docker
Step 3: Verify Docker Is Working
Run:
docker version
or
docker info
If Docker responds with server information, the daemon is running.
Step 4: Check Docker Socket Permissions
Verify:
ls -l /var/run/docker.sock
Example:
srw-rw---- 1 root docker
Notice the group:
docker
Users must belong to this group.
Step 5: Add Your User to the Docker Group
Check groups:
groups
If docker is missing:
sudo usermod -aG docker $USER
Apply changes:
newgrp docker
Or log out and log back in.
Verify:
docker ps
If successful, the permission issue is resolved.
Step 6: Restart Docker
Sometimes Docker hangs.
Restart it:
sudo systemctl restart docker
Verify:
docker ps
Step 7: Check Docker Logs
If Docker refuses to start:
journalctl -u docker
Or:
sudo journalctl -xeu docker.service
Look for errors involving:
- Storage driver
- Missing configuration
- Permission denied
- Disk full
- Invalid daemon.json
Step 8: Verify Docker Context
List contexts:
docker context ls
Example:
default *
desktop-linux
Use the default context:
docker context use default
Fix on Ubuntu/Debian
Start Docker:
sudo systemctl start docker
Enable:
sudo systemctl enable docker
Check:
docker infoIf Docker isn’t installed:
sudo apt update
sudo apt install docker.io
Fix on CentOS/RHEL
Start Docker:
sudo systemctl start docker
Enable:
sudo systemctl enable docker
If missing:
sudo yum install docker
Fix on macOS
Docker Desktop must be running.
Verify:
docker info
If it fails:
- Open Docker Desktop.
- Wait until Docker reports Engine Running.
- Retry:
docker ps
Fix on Windows
Ensure Docker Desktop is started.
Verify WSL integration if using Linux containers.
PowerShell:
docker info
If Docker Desktop isn’t running, start it first.
Fix Inside WSL2
If using Docker Desktop with WSL:
Verify Docker integration is enabled.
Check:
docker version
If the client appears but the server doesn’t, restart Docker Desktop.
Fix for Remote Docker Hosts
If using:
export DOCKER_HOST=tcp://server:2375
Verify:
- Server is reachable
- Docker daemon is running
- Firewall permits access
- TLS settings are correct
Common Docker Daemon Errors
Permission Denied
permission denied while trying to connect to the Docker daemon socket
Usually fixed by joining the docker group.
Socket Does Not Exist
dial unix /var/run/docker.sock:
connect: no such file or directory
Usually means Docker isn’t running.
Docker Service Failed
Job for docker.service failed
Inspect:
journalctl -u docker
Common Mistakes to Avoid
Many Docker daemon issues stem from configuration or permission mistakes. Avoiding these common pitfalls can save significant troubleshooting time.
Running Docker Without Checking the Service
Before changing configurations, always verify that the Docker daemon is actually running.
systemctl status docker
Using sudo Inconsistently
If Docker works with:
sudo docker ps
but fails without sudo, the problem is likely your user permissions. Add your user to the docker group instead of running every command as root.
Editing daemon.json Without Validation
Incorrect JSON syntax in /etc/docker/daemon.json can prevent Docker from starting.
After making changes, restart Docker and review the service logs if startup fails
Ignoring Disk Space Issues
A full disk can stop Docker from starting or creating the Docker socket.
Check available space:
df -h
Best Practices to Prevent Docker Daemon Errors
Following a few maintenance practices can reduce Docker-related downtime and improve system stability.
Enable Docker at Boot
Ensure Docker starts automatically after a system reboot.
sudo systemctl enable docker
Keep Docker Updated
Regularly update Docker Engine and Docker Desktop to receive bug fixes, performance improvements, and security patches.
Monitor Docker Logs
Review Docker logs periodically to detect storage, networking, or daemon issues before they impact production workloads.
Use the Docker Group Securely
Grant Docker access only to trusted users. Members of the docker group effectively have root-level control over the Docker daemon.
How Moon Technolabs Helps with Docker and DevOps Solutions
Moon Technolabs helps businesses design, deploy, and manage containerized applications using Docker, Kubernetes, CI/CD pipelines, and modern cloud platforms. Our DevOps specialists troubleshoot Docker daemon issues, optimize container workflows, automate deployments, implement secure infrastructure, and build scalable cloud-native architectures.
Whether you’re modernizing legacy applications, adopting microservices, or setting up enterprise DevOps pipelines, Moon Technolabs provides end-to-end Docker and infrastructure expertise to ensure reliable, secure, and high-performing deployments.
From Docker troubleshooting and container orchestration to CI/CD implementation, we help businesses improve reliability, security, and deployment efficiency.
Conclusion
The “Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” error indicates that the Docker CLI cannot communicate with the Docker Engine. In most cases, the problem is caused by a stopped Docker service, insufficient permissions, an incorrect Docker context, or a failed daemon startup.
A systematic troubleshooting approach—checking the Docker service, verifying socket permissions, adding your user to the docker group, reviewing logs, and validating Docker contexts—can resolve the majority of cases. By keeping Docker updated, enabling automatic startup, and following proper permission and configuration practices, you can minimize future daemon connectivity issues and maintain a stable container environment.
Learn about DevOps practices, CI/CD pipelines, infrastructure as code, automation, containerization, monitoring, and cloud-native development. Discover how DevOps improves collaboration, accelerates software delivery, and enhances operational efficiency. Keep pace with modern DevOps tools and methodologies driving continuous innovation.
Get in Touch With Us
Submitting the form below will ensure a prompt response from us.
