How to fix error during connect: This error may indicate that the docker daemon is not running. in Docker

DockerBEGINNERMEDIUMUpdated Dec 1, 2025· 360 views

This error appears on Windows when the Docker Desktop application is not running or failed to start. The Docker CLI cannot connect to the daemon service that manages containers.

Quick fix

Fixes error during connect: This error may indicate that the docker daemon is not running.

Start-Process "C:\Program Files\Docker\Docker\Docker Desktop.exe"
  1. Start Docker Desktop
  2. Verify Docker is running
  3. Run as Administrator
  4. Restart Docker Desktop service
docker — error
Start-Process "C:\Program Files\Docker\Docker\Docker Desktop.exe"
error during connect: This error may indicate that the docker daemon is not running.

What this error means

When you run any Docker command on Windows (like `docker ps`, `docker run`, or `docker build`), the Docker CLI needs to communicate with the Docker daemon. On Windows, this communication happens through a named pipe at `//./pipe/docker_engine`. The "docker daemon is not running" error indicates that the Docker CLI cannot establish this connection. This typically means Docker Desktop is either not started, failed during startup, or has crashed. Without a running daemon, no container operations are possible. The full error message often includes additional context: "In the default daemon configuration on Windows, the docker client must be run elevated to connect." This hints that permissions or elevation might also be factors, though the primary cause is usually that Docker Desktop simply needs to be launched.

Typical symptoms

  • All Docker commands fail with 'error during connect' message
  • PowerShell or Command Prompt shows 'docker daemon is not running'
  • Docker Desktop whale icon is not visible in the system tray
  • Docker Desktop shows 'Docker Desktop is starting...' but never completes
  • Running 'docker version' shows Client info but errors on Server section
  • Running 'docker info' returns connection refused or pipe errors

Common causes

  1. Docker Desktop application is not running (most common)
  2. Docker Desktop failed to start due to WSL2 issues
  3. Virtualization (Hyper-V or WSL2) is not enabled in Windows features
  4. Hardware virtualization is disabled in BIOS/UEFI
  5. Docker Desktop service crashed or stopped unexpectedly
  6. Antivirus or security software blocking Docker
  7. Conflict with VirtualBox, VMware, or other virtualization software
  8. Corrupted Docker Desktop installation or configuration
  9. User not in the docker-users group (permission issue)
  10. Windows Update broke Hyper-V or WSL2 integration

How to fix "error during connect: This error may indicate that the docker daemon is not running."

1Start Docker Desktop

The most common solution is simply launching Docker Desktop:

1. Click the Windows Start menu
2. Type "Docker Desktop" and click the application
3. Wait for the whale icon to appear in the system tray
4. The icon animates while starting - wait until it becomes solid

Using PowerShell:

powershell
Start-Process "C:\Program Files\Docker\Docker\Docker Desktop.exe"

Tip: Enable "Start Docker Desktop when you sign in to Windows" in Docker Desktop Settings to avoid this issue in the future.

2Verify Docker is running

Once Docker Desktop shows as running, verify the daemon is accessible:

powershell
docker version

You should see both Client and Server sections. If only Client appears, the daemon is still not running.

Check detailed status:

powershell
docker info

This should display information about containers, images, storage driver, and more.

3Run as Administrator

Docker may require elevated privileges to connect:

1. Close your current terminal
2. Right-click on PowerShell or Command Prompt
3. Select "Run as administrator"
4. Try your Docker command again

Alternative - Add yourself to docker-users group:

powershell
# Run in elevated PowerShell
net localgroup docker-users "$env:USERNAME" /ADD

Log out and log back in for the group change to take effect.

4Restart Docker Desktop service

If Docker Desktop appears running but commands fail, restart the service:

Using Windows Services:
1. Press Win+R, type services.msc, press Enter
2. Find "Docker Desktop Service"
3. Right-click and select "Restart"

Using PowerShell (Administrator):

powershell
Restart-Service -Name "com.docker.service"

Using the System Tray:
1. Right-click the Docker whale icon
2. Click "Restart"

5Switch Docker daemon mode

If you've previously used Windows containers, Docker might be in the wrong mode:

powershell
& "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon

Or right-click the Docker whale icon and select "Switch to Linux containers" (or vice versa).

Note: Most users should use Linux containers (the default).

6Update and restart WSL2

If using the WSL2 backend (default on Windows 10/11 Home):

powershell
# Update WSL
wsl --update

# Shut down all WSL instances
wsl --shutdown

Then restart Docker Desktop.

Check WSL distributions:

powershell
wsl -l -v

You should see "docker-desktop" and "docker-desktop-data" in the list.

7Enable virtualization features

Docker requires virtualization support. Verify it's enabled:

Check virtualization status:
1. Open Task Manager (Ctrl+Shift+Esc)
2. Go to the Performance tab
3. Look for "Virtualization: Enabled"

Enable Windows features:
1. Open "Turn Windows features on or off"
2. Enable these features:
 - Hyper-V (for Windows Pro/Enterprise)
 - Virtual Machine Platform
 - Windows Subsystem for Linux
 - Windows Hypervisor Platform
3. Click OK and restart Windows

If virtualization shows as Disabled, you need to enable it in BIOS/UEFI:
1. Restart your computer
2. Enter BIOS setup (usually F2, F12, Del, or Esc during boot)
3. Find "Intel VT-x", "AMD-V", or "Virtualization Technology"
4. Enable it and save/exit

8Reset Docker Desktop

If other solutions don't work, try resetting Docker:

1. Open Docker Desktop
2. Click the gear icon (Settings)
3. Go to "Troubleshoot" section
4. Click "Reset to factory defaults"

Warning: This removes all containers, images, volumes, and settings. Export important images first:

powershell
docker save my-image:tag -o my-image-backup.tar
9Clean reinstall Docker Desktop

As a last resort, perform a complete reinstall:

1. Uninstall Docker Desktop:
 - Open Windows Settings > Apps
 - Find Docker Desktop and uninstall

2. Remove leftover data:

powershell
Remove-Item -Recurse -Force "$env:APPDATA\Docker" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Docker" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:PROGRAMDATA\Docker" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:PROGRAMDATA\DockerDesktop" -ErrorAction SilentlyContinue

3. Unregister WSL distributions:

powershell
wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

4. Restart Windows

5. Download and install the latest Docker Desktop from https://www.docker.com/products/docker-desktop/

Advanced notes

Diagnosing startup failures:
Docker Desktop creates diagnostic logs that can help identify why the daemon fails to start:

powershell
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload

This generates a diagnostic ID you can share with Docker support.

Antivirus interference:
Some security software blocks Docker's network or file operations. Common culprits include:
- Trend Micro
- Symantec Endpoint Protection
- McAfee
- Windows Defender (rarely)

Try temporarily disabling your antivirus or adding Docker to its exclusions:
- C:\Program Files\Docker\*
- C:\ProgramData\Docker\*
- C:\Users\*\AppData\Local\Docker\*

Conflicts with other virtualization:
- VirtualBox versions before 6.0 conflict with Hyper-V
- VMware Workstation versions before 15.5.5 have similar issues
- Some gaming anti-cheat software disables Hyper-V

Re-enable Hyper-V if disabled:

cmd
bcdedit /set hypervisorlaunchtype auto

Then restart Windows.

WSL2 vs Hyper-V backend:
- Windows Home: Only WSL2 backend available
- Windows Pro/Enterprise: Both available; WSL2 recommended for performance
- If WSL2 checkbox is greyed out, ensure WSL is installed: wsl --install

Corporate environments:
Group policies may prevent Docker from starting. Contact your IT department to ensure:
- Hyper-V/virtualization is allowed
- Your user is in the docker-users group
- No software restriction policies block Docker

Frequently asked questions

What does "error during connect: This error may indicate that the docker daemon i" mean?
When you run any Docker command on Windows (like docker ps, docker run, or docker build), the Docker CLI needs to communicate with the Docker daemon. /pipe/docker_engine. The "docker daemon is not running" error indicates that the Docker CLI cannot establish this connection.
How do I fix "error during connect: This error may indicate that the docker daemon i"?
This error appears on Windows when the Docker Desktop application is not running or failed to start. The Docker CLI cannot connect to the daemon service that manages containers.
What causes "error during connect: This error may indicate that the docker daemon i"?
Docker Desktop application is not running (most common) Docker Desktop failed to start due to WSL2 issues Virtualization (Hyper-V or WSL2) is not enabled in Windows features
Is the "error during connect: This error may indicate that the docker daemon i" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading