How To Resolve “Cannot Connect To The Docker Daemon”

Seeing the error "Cannot connect to the Docker daemon" is one of the most common (and annoying) issues Docker users face. In this guide, we’ll explain what it means, why it happens, and How To Resolve “Cannot Connect To The Docker Daemon” — with practical examples.

The Error Message

When you run a Docker command like this:

docker ps

You might get this error:

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

Or on Windows:

error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopEngine/json": open //./pipe/dockerDesktopEngine: The system cannot find the file specified.

Why This Happens

This error usually means that:

• The Docker daemon is not running, or
• Your user doesn’t have permission to talk to the Docker service

Solution on Linux

Step 1: Check if Docker is Running

sudo systemctl status docker

If it’s inactive or failed:

sudo systemctl start docker

To auto-start Docker on boot:

sudo systemctl enable docker

Step 2: Add Your User to the Docker Group

By default, Docker requires sudo. If you want to run Docker as a non-root user:

sudo usermod -aG docker $USER

Then log out and log back in, or run:

newgrp docker

Now this should work without sudo:

docker ps

Solution on Windows (Docker Desktop)

Step 1: Make Sure Docker Desktop Is Running

• Check the system tray for the Docker whale icon.
• If not running, open Docker Desktop from the Start Menu.

Step 2: Reset the Docker Daemon

If Docker Desktop is stuck:

• Open Docker Desktop
• Go to Settings > Troubleshoot
• Click “Restart Docker”

Step 3: WSL2-Specific Fix (for Windows 10/11)

If you’re using WSL2 and Docker, check if the Docker daemon is exposed to WSL:

wsl
docker ps

If it fails, try:

wsl --shutdown

Then restart Docker Desktop and reopen WSL.

You may also need to enable integration in:

Docker Desktop → Settings → Resources → WSL Integration

Quick Test Command

Once fixed, this command should work:

docker run --rm hello-world

Expected output:

Hello from Docker!
...

Summary

The “Cannot connect to the Docker daemon” error is usually simple to fix once you know where to look—service status, permissions, or environment setup. Whether you’re on Linux or Windows, these steps should get your Docker CLI back in action.

This is the end of the How To Resolve “Cannot Connect To The Docker Daemon”.

You can read more useful articles like How To Run Docker Containers As Non-Root Users Securely.

Follow us for the more helpful posts!

We hope this is a useful post for you.