Home / Docker / Is the Docker Daemon Running? How to Fix Docker Daemon Not Running

Docker

Is the Docker Daemon Running? How to Fix Docker Daemon Not Running

Fix `Cannot connect to the Docker daemon` and `is the docker daemon running?` errors on Linux, macOS, and Windows.

Published: Nov 19, 20258 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

You're trying to run Docker commands but the Docker daemon is not running or not accessible. Docker CLI can't communicate with the Docker daemon, resulting in connection refused or is the docker daemon running? errors. This prevents all Docker operations.

Symptoms

```bash $ docker ps Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running on this host?

$ docker run hello-world docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'.

$ docker info Client: Context: default Debug Mode: false Server: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

$ sudo systemctl status docker Unit docker.service could not be found.

$ docker-compose up ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running? ```

Common Causes

1.Docker service not started: Service hasn't been started or enabled
2.Docker not installed: Docker Engine not installed properly
3.Socket file missing: /var/run/docker.sock doesn't exist
4.Permission issues: User not in docker group
5.Service crashed: Docker daemon crashed due to error
6.Configuration errors: Invalid daemon.json causing startup failure
7.Systemd not available: Running in non-systemd environment
8.Resource issues: Out of memory or disk space

Step-by-Step Fix

Step 1: Check Docker Service Status

First, check if Docker is installed and running:

On Linux (systemd): ```bash # Check service status sudo systemctl status docker

# Check if service is enabled sudo systemctl is-enabled docker

# Check Docker installation which docker docker --version ```

On macOS: ```bash # Check if Docker Desktop is running ps aux | grep -i docker

# Or check the app ls /Applications/Docker.app ```

On Windows: ```powershell # Check Docker Desktop service Get-Process -Name "Docker Desktop"

# Check service Get-Service -Name "com.docker.service" ```

Step 2: Start Docker Service

Start the Docker daemon:

On Linux (systemd): ```bash # Start Docker service sudo systemctl start docker

# Enable Docker to start on boot sudo systemctl enable docker

# Check status sudo systemctl status docker

# Start Docker socket sudo systemctl start docker.socket ```

On Linux (without systemd): ```bash # Start Docker daemon manually sudo dockerd &

# Or with init.d sudo service docker start ```

On macOS: ```bash # Start Docker Desktop open /Applications/Docker.app

# Or from command line /Applications/Docker.app/Contents/MacOS/Docker &

# Wait for Docker to start sleep 30 docker info ```

On Windows: ```powershell # Start Docker Desktop Start-Process "C:\Program Files\Docker\Docker\Docker Desktop.exe"

# Or start the service Start-Service -Name "com.docker.service" ```

Step 3: Check Docker Socket

Verify the socket exists and has correct permissions:

```bash # Check if socket exists ls -la /var/run/docker.sock

# Expected output: # srw-rw---- 1 root docker 0 Jan 1 12:00 /var/run/docker.sock

# Check socket permissions stat /var/run/docker.sock

# If socket missing, restart Docker sudo systemctl restart docker

# Check Docker daemon is creating socket sudo ls -la /var/run/docker*

# Check Docker context docker context ls

# Use default context docker context use default ```

Step 4: Fix Permission Issues

Add your user to the docker group:

```bash # Check if user is in docker group groups $USER

# Add user to docker group sudo usermod -aG docker $USER

# Apply group changes (log out and back in, or:) newgrp docker

# Or restart your session # On Linux: log out and log back in # On macOS/Windows: restart Docker Desktop

# Verify permissions ls -la /var/run/docker.sock

# If still having issues, fix socket permissions sudo chmod 666 /var/run/docker.sock

# For permanent fix sudo chmod 660 /var/run/docker.sock sudo chown root:docker /var/run/docker.sock ```

Step 5: Check Docker Configuration

Invalid configuration can prevent startup:

```bash # Check for configuration file ls -la /etc/docker/daemon.json

# Validate JSON syntax cat /etc/docker/daemon.json | jq .

# If invalid JSON, fix or remove sudo mv /etc/docker/daemon.json /etc/docker/daemon.json.backup

# Restart Docker sudo systemctl restart docker

# If jq not available, check manually python3 -m json.tool /etc/docker/daemon.json ```

Check for common configuration errors: ```bash # View current config sudo cat /etc/docker/daemon.json

# Minimal valid config echo '{}' | sudo tee /etc/docker/daemon.json

# Common valid configuration sudo tee /etc/docker/daemon.json <<EOF { "storage-driver": "overlay2", "log-driver": "json-file", "log-opts": { "max-size": "10m", "max-file": "3" } } EOF

# Restart Docker sudo systemctl restart docker ```

Step 6: Check Docker Logs

Look for startup errors in logs:

```bash # View Docker daemon logs sudo journalctl -u docker.service

# View recent logs sudo journalctl -u docker.service -n 50

# Follow logs sudo journalctl -u docker.service -f

# Check systemd logs sudo journalctl -xe

# On non-systemd systems cat /var/log/docker.log cat /var/log/upstart/docker.log

# Check Docker daemon output directly sudo dockerd --debug ```

Step 7: Check Resources

Ensure system has enough resources:

```bash # Check available memory free -h

# Check disk space df -h

# Check Docker data directory df -h /var/lib/docker

# Check inodes df -i /var/lib/docker

# Check for zombie processes ps aux | grep -i docker

# Kill any stuck processes sudo pkill -9 dockerd

# Clean up and restart sudo rm -rf /var/run/docker.sock sudo systemctl start docker ```

Step 8: Reinstall Docker

If Docker is corrupted, reinstall:

On Linux (Ubuntu/Debian): ```bash # Remove Docker sudo apt-get remove docker docker-engine docker.io containerd runc

# Remove Docker data (caution: deletes all images, containers, volumes) sudo rm -rf /var/lib/docker sudo rm -rf /var/lib/containerd

# Install Docker curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh

# Add user to docker group sudo usermod -aG docker $USER

# Start Docker sudo systemctl start docker sudo systemctl enable docker ```

On macOS: ```bash # Uninstall Docker Desktop /Applications/Docker.app/Contents/MacOS/Docker uninstall

# Reinstall from Docker website or Homebrew brew install --cask docker

# Open Docker Desktop open /Applications/Docker.app ```

On Windows: ```powershell # Uninstall Docker Desktop # Use Settings > Apps > Docker Desktop > Uninstall

# Reinstall from Docker website # Download and run the installer ```

Step 9: Check Environment Variables

Environment variables can affect connection:

```bash # Check Docker environment variables env | grep -i docker

# Common variables that might cause issues echo $DOCKER_HOST echo $DOCKER_TLS_VERIFY echo $DOCKER_CERT_PATH

# Unset problematic variables unset DOCKER_HOST unset DOCKER_TLS_VERIFY unset DOCKER_CERT_PATH

# Or use default socket export DOCKER_HOST=unix:///var/run/docker.sock

# Test connection docker info ```

Step 10: Use Docker Machine or Context

Check for Docker context issues:

```bash # List Docker contexts docker context ls

# Check current context docker context show

# Use default context docker context use default

# Create new context if needed docker context create my-context --docker "host=unix:///var/run/docker.sock"

# Use specific context docker context use my-context

# Check Docker machine (if using) docker-machine ls docker-machine env default eval $(docker-machine env default) ```

Verification

Confirm Docker is running and accessible:

```bash # Check service status sudo systemctl status docker

# Should show active (running)

# Test Docker CLI docker info

# Should show Docker client and server info

# Test run docker run --rm hello-world

# Should download and run hello-world successfully

# Check socket ls -la /var/run/docker.sock

# Should show socket file

# Check user permissions groups $USER

# Should include 'docker'

# Test without sudo docker ps ```

Docker should now be running and all commands should work without errors.

[Fix docker build cache invalidated unnecessary layers Issue in Docker-Errors](docker-build-cache-invalidated-unnecessary-layers)
[Fix Docker Build Cache Invalidation Optimization Issue in Docker](docker-build-cache-invalidation-optimization)
[Fix docker build context slow large files Issue in Docker-Errors](docker-build-context-slow-large-files)
[Fix docker build multi stage copy from not found Issue in Docker-Errors](docker-build-multi-stage-copy-from-not-found)
[Fix docker buildkit export local tar layer missing Issue in Docker-Errors](docker-buildkit-export-local-tar-layer-missing)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Is the Docker Daemon Running? How to Fix Docker Daemon Not Running Is the Docker Daemon Running? How to Fix Docker Daemon Not Running Docker Is the Docker Daemon Running? How to Fix Docker Daemon Not Running troubleshooting Is the Docker Daemon Running? How to Fix Docker Daemon Not Running fix Fix `Cannot connect to the Docker daemon` and `is the docker daemon running Docker Fix `Cannot connect to the Docker daemon` and `is the docker daemon running

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Docker Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this docker-errors troubleshooting guide applies to my situation?

This guide is designed for docker-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these docker-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of docker-errors issue?

Most docker-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this docker-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for docker-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Nov 19, 2025

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Is the Docker Daemon Running? How to Fix Docker Daemon Not Running

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Docker Service Status

Step 2: Start Docker Service

Step 3: Check Docker Socket

Step 4: Fix Permission Issues

Step 5: Check Docker Configuration

Step 6: Check Docker Logs

Step 7: Check Resources

Step 8: Reinstall Docker

Step 9: Check Environment Variables

Step 10: Use Docker Machine or Context

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Is the Docker Daemon Running? How to Fix Docker Daemon Not Running

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Docker Service Status

Step 2: Start Docker Service

Step 3: Check Docker Socket

Step 4: Fix Permission Issues

Step 5: Check Docker Configuration

Step 6: Check Docker Logs

Step 7: Check Resources

Step 8: Reinstall Docker

Step 9: Check Environment Variables

Step 10: Use Docker Machine or Context

Verification

Related Articles

People also search for

Share this guide

More Docker Troubleshooting Guides

Browse Guides from Other Categories

Docker Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading