“Cannot connect to the Docker daemon.” If you’ve seen this error, your containers aren’t going anywhere until you fix it.
Learning how to start Docker daemon is one of the first skills every developer needs when working with containerization.
The daemon (dockerd) is the background service that powers everything. Container management, image pulls, network isolation, storage drivers. None of it works without the daemon running.
This guide covers startup methods for Linux, Windows, and macOS. You’ll get exact commands, troubleshooting steps, and configuration options.
Time required: 2-5 minutes. Let’s get your Docker Engine running.
How to Start Docker Daemon
Starting Docker daemon is the process of activating the background service that manages containers, images, networks, and volumes on your host machine.
The daemon (dockerd) handles all communication between the Docker CLI and container runtime.
Users need this when Docker commands return “Cannot connect to the Docker daemon” errors, after system reboot, or when the service crashes unexpectedly.
This guide covers 5 methods for Linux, Windows, and macOS. Time required: 2-5 minutes. Skill level: basic terminal knowledge.
Prerequisites
Before you start Docker daemon, verify these requirements:
- Docker Engine 20.10+ or Docker Desktop 4.0+ must be installed on your system
- Operating system: Ubuntu 20.04+, CentOS 7+, Fedora, Debian, Windows 10/11, or macOS 10.15+
- Administrative privileges (sudo access on Linux, Administrator on Windows)
- Terminal, PowerShell, or command line interface access
Most Linux distributions use systemd as the service manager. Older systems like Ubuntu 14.10 use upstart instead.
Windows and macOS users typically run Docker Desktop, which bundles the daemon with a graphical interface.
Step 1: How Do You Start Docker Daemon on Linux with Systemd?
Run sudo systemctl start docker in your terminal to activate the Docker service through the Linux service manager. The daemon starts as a background process, listening on the unix socket at /var/run/docker.sock.
Action
1. Open terminal and execute:
“ sudo systemctl start docker `
2. Verify the service status:
` sudo systemctl status docker `
3. Expected output: “Active: active (running)” with green indicator.
Purpose
The systemctl command interfaces with systemd to manage system services. This method ensures proper configuration management and logging through the Linux init system.
Docker daemon requires root privileges to access system resources, network interfaces, and storage drivers.
Step 2: How Do You Start Docker Daemon Manually Using dockerd?
Execute sudo dockerd to run the daemon directly in your terminal foreground. This method bypasses the service manager and sends logs straight to your terminal window for real-time debugging.
Action
1. Run the daemon command:
` sudo dockerd `
2. With debug flags enabled:
` sudo dockerd --debug `
3. Expected result: Terminal displays “API listen on /var/run/docker.sock” message.
Purpose
Manual startup helps troubleshoot daemon configuration errors. The process runs in foreground, blocking the terminal until stopped with Ctrl+C.
Use this for testing custom daemon.json settings or diagnosing startup failures that systemctl logs don’t reveal clearly.
Step 3: How Do You Start Docker Daemon on Windows?
Launch Docker Desktop from the Start menu or run Start-Service docker in PowerShell with Administrator privileges. The system tray icon turns green when the Docker Engine activates successfully.
Action
Method A – Docker Desktop:
- Click Start Menu > Docker Desktop
- Wait for whale icon in system tray to stop animating
- Green status indicates daemon is ready
Method B – PowerShell (Admin):
` Start-Service docker `
Check status:
` Get-Service docker `
Purpose
Windows runs Docker through either Hyper-V or WSL2 backend. Docker Desktop manages both the daemon and the virtual machine layer automatically.
The PowerShell method works when Docker Desktop is installed but not running, activating the Windows service directly.
Step 4: How Do You Start Docker Daemon on macOS?
Open Docker Desktop from the Applications folder or run open /Applications/Docker.app in Terminal. The whale icon appears in the menu bar, animating while the daemon initializes.
Action
Method A – Finder:
- Navigate to Applications > Docker
- Double-click Docker.app
- Wait for menu bar icon to show “Docker Desktop is running”
Method B – Terminal:
` open /Applications/Docker.app `
Verify status:
` docker info `
Purpose
macOS requires Docker Desktop because the daemon needs a Linux kernel to run Docker containers. The app creates a lightweight VM using Apple’s Hypervisor framework.
Step 5: How Do You Configure Docker Daemon to Start Automatically on Boot?
Run sudo systemctl enable docker on Linux to register the service for automatic startup. Windows and macOS users configure this through Docker Desktop settings under "Start Docker Desktop when you log in."
Action
Linux (systemd):
` sudo systemctl enable docker `
Windows/macOS:
- Open Docker Desktop > Settings > General
- Check “Start Docker Desktop when you sign in”
- Click Apply & Restart
Purpose
Auto-start ensures the daemon activates during boot sequence without manual intervention. Critical for servers running containerized applications in production environments.
Step 6: How Do You Verify Docker Daemon is Running?
Execute docker info to display detailed daemon status including server version, storage driver, and container runtime information. A successful response confirms the daemon accepts API requests.
Action
Primary check:
` docker info `
Quick verification:
` docker ps `
Service status (Linux):
` sudo systemctl status docker `
Purpose
The docker info command queries the daemon API directly. If the daemon isn't running, you'll see "Cannot connect to the Docker daemon" error instead of system information.
Learn more about checking if Docker is running for additional verification methods.
Troubleshooting
Cannot Connect to Docker Daemon Error
Cause: Docker service not running or socket file missing at /var/run/docker.sock.
Solution:
` sudo systemctl start docker sudo systemctl status docker `
If status shows failed, check daemon logs with journalctl -u docker.service.
Permission Denied Error on Linux
Cause: Current user lacks membership in the docker group.
Solution:
` sudo usermod -aG docker $USER `
Log out completely and log back in. The group change requires a new session to take effect.
Docker Daemon Fails to Start Due to Port Conflict
Cause: Another process occupies ports required by Docker networking or the daemon socket.
Solution:
` sudo lsof -i :2375 sudo lsof -i :2376 `
Kill conflicting processes or change Docker’s listening port in daemon.json.
Insufficient Resources Error
Cause: Host machine lacks CPU, memory, or disk space for daemon operations.
Solution:
` df -h # Check disk space
free -m # Check memory
docker system prune # Remove unused data
`
Consider removing unused Docker images to free storage.
Docker Daemon Configuration
The daemon.json file controls daemon configuration options including network settings, storage drivers, and logging behavior.
File locations by OS:
- Linux: /etc/docker/daemon.json
- Windows: C:ProgramDatadockerconfigdaemon.json
- macOS: ~/.docker/daemon.json
Sample configuration:
` { "debug": true, "storage-driver": "overlay2", "log-driver": "json-file", "log-opts": { "max-size": "10m", "max-file": "3" } } `
Restart the daemon after editing: sudo systemctl restart docker
Docker stores container data in /var/lib/docker on Linux, C:ProgramDatadocker on Windows. Check where Docker images are stored for detailed path information.
Related Processes
After starting the daemon, you may need these related operations:
- Stop daemon: sudo systemctl stop docker
- Restart daemon: sudo systemctl restart docker
- View logs: journalctl -u docker.service -f
- Configure TLS: Add certificate paths to daemon.json
For container management after daemon startup, learn how to use Docker effectively.
Understanding what Docker is and its core components helps troubleshoot daemon issues faster.
Teams using DevOps workflows integrate daemon management into their build pipelines for continuous integration.
FAQ on How To Start Docker Daemon
What is Docker daemon and why do I need to start it?
The Docker daemon (dockerd) is a background service that manages containers, images, networks, and volumes. Without it running, the Docker CLI cannot execute commands. The daemon handles all container lifecycle operations on your host machine.
How do I know if Docker daemon is already running?
Run docker info in your terminal. If the daemon is active, you'll see system information including server version and storage driver. An error message "Cannot connect to the Docker daemon" means the service isn't running.
What command starts Docker daemon on Linux?
Use sudo systemctl start docker on distributions with systemd like Ubuntu, CentOS, and Fedora. For older systems using upstart, run sudo service docker start instead. Both commands require root privileges.
How do I start Docker daemon on Windows?
Launch Docker Desktop from the Start menu or run Start-Service docker in PowerShell as Administrator. The system tray whale icon indicates daemon status. Green means running, animating means starting up.
How do I start Docker daemon on macOS?
Open Docker Desktop from Applications or run open /Applications/Docker.app in Terminal. macOS requires Docker Desktop because the daemon needs a Linux kernel provided through a lightweight virtualization layer.
Can I run Docker daemon manually without systemd?
Yes. Execute sudo dockerd to start the daemon in foreground mode. This sends logs directly to your terminal, useful for debugging configuration issues. Press Ctrl+C to stop the daemon when finished.
How do I make Docker daemon start automatically on boot?
Run sudo systemctl enable docker on Linux to register the service for automatic startup. Windows and macOS users enable "Start Docker Desktop when you sign in" under Settings > General.
Why does Docker daemon fail to start?
Common causes include insufficient disk space, port conflicts, corrupted daemon.json configuration, or missing permissions. Check logs with journalctl -u docker.service on Linux. Verify your user belongs to the docker group.
What is the difference between Docker daemon and Docker Desktop?
Docker Desktop is a GUI application bundling the daemon, CLI, and Docker Compose. The daemon is just the background service. Linux can run the daemon standalone; Windows and macOS typically need Docker Desktop.
How do I restart Docker daemon after configuration changes?
Run sudo systemctl restart docker on Linux after editing daemon.json. Docker Desktop users click "Apply & Restart" in settings. Learn how to restart containers affected by daemon restarts.
Conclusion
Knowing how to start Docker daemon removes the biggest barrier between you and running containers. The process takes under five minutes on any operating system.
Linux users rely on systemctl commands. Windows and macOS users launch Docker Desktop.
The daemon.json file gives you control over logging, storage drivers, and network settings. Configure auto-start on boot for production servers.
When errors appear, check service status first. Most issues trace back to permissions, port conflicts, or resource constraints.
Your Docker CLI, containerd, and container orchestration tools all depend on the daemon running properly. Master this foundation, and container deployment becomes routine.
Keep the troubleshooting commands handy. You’ll need them eventually.
Many of his resources are available on various design marketplaces and for free on Codepen.
Over the years, he's worked with a range of clients and contributed to design publications like Design Your Way, Designmodo, WebDesignerDepot, WPDean, Speckyboy, and Slider Revolution among others.
