Symptoms & Diagnosis
The “Docker daemon not running” error is a common hurdle for Windows users. It typically occurs when the Docker background process fails to initialize or loses connection with the Windows Subsystem for Linux (WSL).
Common symptoms include the Docker Desktop icon remaining “stuck” in the starting phase or receiving the “error during connect: This error may indicate that the docker daemon is not running” message in your terminal.
To diagnose the root cause, you should first check the status of the Docker service. Open PowerShell as an Administrator and run the following command to see if the engine is responsive:
docker versionIf the client section displays info but the server section shows an error, the daemon is definitely unresponsive. You can also check the Windows Services panel (services.msc) to look for the “Docker Desktop Service” status.
| Symptom | Potential Cause | Severity |
|---|---|---|
| “Docker Desktop is unable to start” | WSL 2 Kernel outdated | Medium |
| Connection refused on localhost:2375 | Expose daemon setting disabled | Low |
| Docker hangs on “Starting” | Resource starvation or corrupted VHDX | High |
Troubleshooting Guide
Step 1: Restart Docker Desktop Service
Often, the service simply fails to trigger during system boot. You can manually force a restart of the Docker backend using PowerShell:
net stop com.docker.service
net start com.docker.serviceStep 2: Update WSL 2 Kernel
Docker Desktop for Windows relies heavily on WSL 2. If your Linux kernel is outdated, the daemon will fail to mount the necessary containers. Run this command to ensure you are on the latest version:
wsl --update
wsl --shutdownStep 3: Reset Docker to Factory Defaults
If configuration files are corrupted, a reset is necessary. Right-click the Docker icon in the system tray, select “Troubleshoot,” and choose “Reset to factory defaults.” Note that this will remove your local images and containers.
Step 4: Switch to Windows Containers (and back)
Sometimes the daemon toggle gets stuck. Right-click the Docker icon and select “Switch to Windows containers.” After it successfully switches, toggle it back to “Linux containers.” This forces the daemon to rebuild its runtime environment.
Prevention
To prevent the Docker daemon from failing in the future, ensure that “Start Docker Desktop when you log in” is enabled in the settings. This allows the background services to warm up before you attempt to run commands.
Keep your Windows OS updated. Many Docker issues are linked to outdated virtualization features in Windows 10 and 11. Regularly running wsl --update is also highly recommended.
Finally, avoid hard-shutting down your PC while Docker containers are active. Properly stop your containers using docker stop $(docker ps -q) before turning off your machine to prevent VHDX file corruption.