Introduction
You are working on a project, everything seems fine, and then it happens. You type a Docker command and your terminal throws back a brutal error message. It reads: cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? Your workflow stops completely. Your container will not start. And you have no idea where to begin.
This error is one of the most common issues Docker users face, regardless of their experience level. Beginners see it on their first day. Experienced engineers hit it after an unexpected system restart. The good news is that this error has clear, fixable causes. You just need to know where to look.
In this article, you will learn exactly what causes the error “cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running?”, how to diagnose the root problem, and how to fix it step by step on Linux, macOS, and Windows. You will also find a dedicated FAQ section answering the most common follow-up questions from developers just like you.
What Does This Error Actually Mean?
Before fixing anything, you need to understand what this message is telling you. The error “cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running?” appears when your Docker client cannot reach the Docker daemon.
Think of Docker as having two parts. The Docker client is the tool you interact with from the command line. The Docker daemon is the background service that actually manages containers, images, networks, and volumes. The two communicate through a Unix socket file located at /var/run/docker.sock.
When the daemon is not running, or when your user does not have permission to access that socket file, the client cannot establish a connection. The result is the error you see on screen. Understanding this distinction helps you narrow down the problem immediately.
The Unix Socket Explained Simply
A Unix socket is a special file that allows two programs on the same machine to talk to each other. It is faster than a network connection because no actual network traffic is involved. Docker uses this socket by default on Linux and macOS systems.
When you run docker ps or any Docker command, the client sends a request through /var/run/docker.sock to the daemon. If the daemon is offline or the socket is inaccessible, you hit the error: cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running?
The Most Common Causes of This Error
The error can have several root causes. Knowing which one applies to you saves a lot of time. Here are the most frequent triggers that developers encounter.
1. The Docker Daemon Is Simply Not Running
This is the most common cause by far. Your system restarted, you just installed Docker for the first time, or the daemon crashed silently in the background. The fix is straightforward: you start the daemon again.
On Linux, you run this command to start Docker:
sudo systemctl start docker
To check whether Docker is running, use:
sudo systemctl status docker
If you want Docker to start automatically every time your system boots, enable it with:
sudo systemctl enable docker
2. Permission Issues With the Socket File
Even when the daemon is running, you might still see the error cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? if your current user does not have permission to access the socket file.
By default, the Docker socket is owned by the docker group. If your user is not a member of this group, you have to use sudo for every Docker command, or add yourself to the group. To add your user to the docker group, run:
sudo usermod -aG docker $USER
After running this command, log out and log back in. The change only takes effect in a new session. You can verify your group membership with:
groups $USER
3. Docker Is Not Installed Correctly
If you recently installed Docker and immediately see this error, the installation might be incomplete. Some package managers install the Docker client without the daemon. Others install an older version that conflicts with your system configuration.
You can verify what is installed with:
docker –version
docker info
If docker info fails while docker –version works, the client is present but the daemon is missing or broken. In that case, reinstall Docker using the official documentation from docs.docker.com.
4. Docker Desktop Is Not Running on macOS or Windows
On macOS and Windows, Docker runs inside a lightweight virtual machine managed by Docker Desktop. The cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? error appears when Docker Desktop is not open or not fully started.
The fix here is simple. Open Docker Desktop from your Applications folder or Start menu. Wait for the whale icon in your menu bar or system tray to stop animating. That animation means Docker is still starting up. Once the icon is still, your daemon is ready.
5. The Docker Socket Path Is Wrong
Some advanced configurations or Docker Desktop versions on macOS use a different socket path than the default. The default is /var/run/docker.sock, but Docker Desktop for Mac sometimes uses a path inside your home directory.
You can point your client to the correct socket with the DOCKER_HOST environment variable:
export DOCKER_HOST=unix:///Users/yourname/.docker/run/docker.sock
Replace yourname with your actual macOS username. You can also check which socket Docker Desktop is using by inspecting the Docker Desktop settings under General or Advanced.
How to Diagnose the Error Step by Step
When you encounter cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running?, follow these diagnostic steps in order. Each step rules out a cause and gets you closer to the solution.
- Check if the Docker daemon is active with: sudo systemctl status docker
- Try running a Docker command with sudo to isolate permission issues: sudo docker ps
- Check the socket file exists and has correct permissions: ls -la /var/run/docker.sock
- Inspect Docker logs for crash messages: sudo journalctl -u docker –since today
- Verify your user is in the docker group: groups $USER
- On macOS or Windows, confirm Docker Desktop is open and fully loaded
- Check if a conflicting Docker context is set: docker context ls
Working through these steps in order solves the problem in the vast majority of cases. I have personally resolved dozens of instances of this error using exactly this checklist.
Fixing the Error on Linux
Linux users encounter this error most often after a fresh installation or after a reboot. Here is a complete fix sequence for Ubuntu, Debian, CentOS, and Fedora systems.
Start and Enable the Docker Service
sudo systemctl start docker
sudo systemctl enable docker
sudo systemctl status docker
You should see a green active (running) status. If you see a failed status, check the logs with:
sudo journalctl -u docker -n 50
The logs will show you the exact reason the daemon failed to start. Common reasons include port conflicts, missing kernel modules, and storage driver issues.
Fix Socket Permissions Permanently
If sudo docker ps works but docker ps without sudo fails, the issue is permissions. Add yourself to the docker group and refresh your session:
sudo usermod -aG docker $USER
newgrp docker
The newgrp command activates the new group membership without requiring a full logout. Test immediately after with docker ps.
Reinstall Docker on Linux
If the daemon refuses to start after all the above steps, a clean reinstall is your best option. Remove the existing installation first:
sudo apt remove docker docker-engine docker.io containerd runc
Then follow the official Docker installation guide for your Linux distribution at docs.docker.com. The official guide uses verified package repositories and installs all required components correctly.
Fixing the Error on macOS
macOS users most often see the cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? error when Docker Desktop is closed. The fix is usually straightforward.
Step 1: Launch Docker Desktop
Open Docker Desktop from your Applications folder. Look for the whale icon in your menu bar. Wait for it to stop animating before running any Docker commands. Attempting to use Docker while it is still loading always produces the daemon connection error.
Step 2: Set the Correct DOCKER_HOST
If Docker Desktop is running but the error persists, the socket path might differ from the default. Run this command to check:
docker context ls
Switch to the correct context if needed:
docker context use desktop-linux
Or manually set the socket path in your shell profile:
export DOCKER_HOST=unix://$HOME/.docker/run/docker.sock
Step 3: Reset Docker Desktop
If nothing else works, open Docker Desktop and navigate to Troubleshoot. Click Reset to Factory Defaults. This clears all custom configurations and restarts Docker fresh. You will lose locally cached images and containers, so use this as a last resort.
Fixing the Error on Windows
On Windows, this error typically appears when using Docker from WSL2 (Windows Subsystem for Linux) or when Docker Desktop is not running.
Ensure Docker Desktop Is Running
Open Docker Desktop from the Start menu. Check the system tray for the Docker whale icon. Wait for it to be fully loaded. Then return to your terminal and try your Docker command again.
Enable WSL2 Integration
If you run Docker commands from a WSL2 terminal and see the daemon error, integration might be disabled. Open Docker Desktop and go to Settings. Navigate to Resources and then WSL Integration. Enable integration for your active Linux distribution. Apply and restart Docker Desktop.
Run Docker Commands From PowerShell
If WSL2 integration is problematic, test your Docker commands directly from PowerShell or Command Prompt. If they work there but not in WSL2, the issue is isolated to the WSL2 integration layer.
Preventing This Error in the Future
Once you fix the issue, a few simple habits will prevent you from seeing cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? again.
- Enable autostart: Run sudo systemctl enable docker on Linux so the daemon starts automatically on every boot.
- Use the docker group: Always add your user to the docker group to avoid permission errors.
- Monitor Docker Desktop: On macOS and Windows, check that Docker Desktop is fully loaded before working.
- Keep Docker updated: Outdated versions sometimes introduce daemon stability issues. Update regularly.
- Check logs proactively: Run sudo journalctl -u docker periodically to catch errors before they disrupt your work.
Frequently Asked Questions
1. Why does this error appear after every system restart?
The Docker daemon is not configured to start automatically. On Linux, run sudo systemctl enable docker to fix this permanently. On macOS and Windows, open Docker Desktop settings and enable the option to launch it on login.
2. Does sudo docker ps fix the error?
Yes, in most cases. If docker ps fails but sudo docker ps works, your user lacks permission to access the Docker socket. Add yourself to the docker group with sudo usermod -aG docker $USER and log out and back in.
3. What if the Docker daemon starts but immediately crashes?
Check the logs with sudo journalctl -u docker -n 100. Look for error messages about storage drivers, port conflicts, or missing kernel modules. The logs almost always point directly to the cause.
4. Can this error occur inside a Docker container?
Yes. If you run a container that itself needs to communicate with Docker (for example, CI/CD agents), you must mount the Docker socket into the container. Use -v /var/run/docker.sock:/var/run/docker.sock in your docker run command. This approach carries security implications, so use it carefully.
5. How do I fix this error in a CI/CD pipeline?
In automated pipelines, ensure the Docker service is started before running your Docker commands. In GitHub Actions, use the setup-docker action or check that the runner has Docker pre-installed. In GitLab CI, use a Docker-in-Docker service or mount the host socket into your job container.
6. What does /var/run/docker.sock mean exactly?
It is the path to the Unix socket file that the Docker daemon listens on. The Docker client sends commands through this file to the daemon. If the file does not exist, the daemon is not running. If the file exists but you cannot access it, your user lacks the necessary permissions.
7. Will reinstalling Docker fix the error?
Sometimes. Reinstalling is the right move when the daemon fails to start even after checking permissions and logs, or when the original installation was incomplete. Always remove the old installation cleanly before reinstalling to avoid configuration conflicts.
8. Can a firewall cause this error?
Not directly. The Unix socket is a local file, not a network connection, so firewalls do not affect it. However, if you configure Docker to use a TCP socket instead of the Unix socket, firewalls can block it. The default Unix socket path is not affected by firewall rules.
9. Why does this happen on a fresh Docker installation?
Fresh installations often need one manual step: starting the daemon for the first time. Run sudo systemctl start docker and then sudo systemctl enable docker. Also ensure you have added your user to the docker group before running commands without sudo.
10. Is the DOCKER_HOST environment variable relevant to this error?
Yes. If DOCKER_HOST is set to an incorrect value, the client tries to connect to a non-existent socket or remote host. Run echo $DOCKER_HOST to check. If it shows a wrong path, unset it with unset DOCKER_HOST and try again with the default socket.
Conclusion
The error cannot connect to the docker daemon at unix:///var/run/docker.sock. is the docker daemon running? sounds intimidating at first, but it always has a concrete cause. In most cases, the daemon is simply not running, or your user lacks the right permissions to access the socket. Both issues have quick, clear fixes.
You now have a complete diagnostic checklist, platform-specific solutions for Linux, macOS, and Windows, and preventive measures to keep the error from coming back. The next time your terminal throws this error at you, you will know exactly where to start.
Did this guide solve your problem? If you found a fix that is not listed here, share it in the comments. Your experience might save another developer hours of frustration. And if you work with Docker regularly, bookmark this page so you have the solutions ready the next time this error appears.
Also Read In qtsdatacenter.co.uk
Email: johanharewn314@gmail.com
Author Name: Johan Harwen
