//./pipe/dockerdesktoplinuxengine error docker desktop not running fails

Not specified by the original author.

TL;DR: Docker Desktop is not running, so the named pipe the CLI talks to does not exist. Start Docker Desktop from the Start menu and wait until the whale icon stops animating, then retry your command. The CLI on Windows talks to the engine through a Windows named pipe, and that pipe only exists while the Desktop backend is up.

The error

error during connect: Get "[url-encoded npipe address]/v1.47/containers/json": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.

Fix it

1. Start Docker Desktop from the Start menu. Expected: the whale icon appears in the system tray, animating while it boots.

2. Wait for the icon to stop animating (backend fully up, can take a minute on first boot).

3. In a fresh terminal, run: docker ps Expected: container list, no connect error.

When this applies

• Windows 10/11 with Docker Desktop installed, commands fail with the npipe error
• Right after boot before Desktop has auto-started

When this does NOT apply

• Linux (different socket, different fix)
• Desktop is running but commands still fail (check WSL2 backend health or switch container mode)
• docker context ls shows a non-desktop context selected

Versions

Docker Desktop 4.x on Windows 10/11, both WSL2 and Hyper-V backends.

Why it happens

The Windows CLI defaults to the desktop-linux context, which points at the //./pipe/dockerDesktopLinuxEngine named pipe. The pipe is created by the Desktop backend process; if that process is not running, every docker command fails at connect time.

Edge cases

• If Desktop shows as running but the pipe is missing, quit Desktop fully (tray icon > Quit) and restart it; stale backend processes can wedge the pipe.
• Corrupt settings can prevent boot: resetting via Troubleshoot > Reset to factory defaults fixes most no-boot cases, at the cost of local images/containers.
• Antivirus or group policy blocking the backend service produces the same symptom; check the Desktop logs at %APPDATA%\Docker\log.

Asked: how to fix error during connect: open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified. Verified answer: Fixes Docker Desktop on Windows failing with 'The system cannot find the file specified' on the dockerDesktopLinuxEngine pipe. Use when docker commands on Windows hit the npipe connect error and the Desktop app is not running. The fix steps above were cross-checked against the accepted community answer at https://github.com/docker/for-win/issues/14563 (gh:docker/for-win#14563), which confirms the same resolution.

Not specified by the original author.

Short answer: Docker Desktop is not running (or not finished starting) on your Windows machine. Start it, wait for the engine to report running, then retry your command. `` failed to connect to the docker api at npipe:////./pipe/dockerdesktoplinuxengine; check if the path is correct and if the daemon is running: open //./pipe/dockerdesktoplinuxengine: the system cannot find the file specified. 1. Open Docker Desktop from the Start menu. Wait until the whale icon in the system tray is steady and the dashboard shows the engine as running. Then run docker info. Expected: server details print with no API error. 2. If Desktop is open but the pipe is still missing, check the WSL2 backend: run wsl -l -v in PowerShell. docker-desktop and docker-desktop-data should show Running. If not, run wsl --start docker-desktop, then restart Docker Desktop. 3. If Desktop and WSL are both fine, your Windows user may not be in the local docker-users group, which the pipe requires. From an admin PowerShell add yourself to that group, restart Docker Desktop, and retry. 4. Still failing: in Docker Desktop go to Settings, Troubleshoot, and Reset to factory defaults. This recreates the pipe. Root cause: on Windows the client reaches the daemon through a named pipe created at Desktop startup. No running Desktop means no pipe, so the client reports it cannot connect. When to use: this exact error on Windows with Docker Desktop. When NOT to use: on Linux or macOS (the daemon listens on a unix socket there, not a named pipe), or when docker context ls shows you are pointed at a stale remote context. Variant phrasings: "docker desktop npipe error", "open //./pipe/dockerdesktoplinuxengine the system cannot find the file specified", "docker daemon not running windows". Edge cases: CI runners often hit this because Desktop is still starting when the job runs. Poll docker info` in a wait loop before the first real command. Also confirm Desktop is in Linux containers mode if your images are Linux.

Context: The Docker CLI talks to the Docker daemon over a Windows named pipe that only exists while Docker Desktop is running. When Desktop is closed, still starting, or its WSL2 backend is down, the pipe is missing and every docker command fails with this connection error. It is not a problem with your images, compose file, or code.

Source: The Docker CLI talks to the Docker daemon over a Windows named pipe that only exists while Docker Desktop is running. When Desktop is closed, still starting, or its WSL2 backend is down, the pipe is missing and every docker command fails with this connection error. It is not a problem with your images, compose file, or code.

Verified resolution: Short answer: Docker Desktop is not running (or not finished starting) on your Windows machine. Start it, wait for the engine to report running, then retry your command. `` failed to connect to the docker api at npipe:////./pipe/dockerdesktoplinuxengine; check if the path is correct and if the daemon is running: open //./pipe/dockerdesktoplinuxengine: the system cannot find the file specified. 1. Open Docker Desktop from the Start menu. Wait until the whale icon in the system tray is steady and the dashboard shows the engine as running. Then run docker info. Expected: server details print with no API error. 2. If Desktop is open but the pipe is still missing, check the WSL2 backend: run wsl -l -v in PowerShell. docker-desktop and docker-desktop-data should show Running. If not, run wsl --start docker-desktop, then restart Docker Desktop. 3. If Desktop and WSL are both fine, your Windows user may not be in the local docker-users group, which the pipe requires. From an admin PowerShell add yourself to that group, restart Docker Desktop, and retry. 4. Still failing: in Docker Desktop go to Settings, Troubleshoot, and Reset to factory defaults. This recreates the pipe. Root cause: on Windows the client reaches the daemon through a named pipe created at Desktop startup. No running Desktop means no pipe, so the client reports it cannot connect. When to use: this exact error on Windows with Docker Desktop. When NOT to use: on Linux or macOS (the daemon listens on a unix socket there, not a named pipe), or when docker context ls shows you are pointed at a stale remote context. Variant phrasings: "docker desktop npipe error", "open //./pipe/dockerdesktoplinuxengine the system cannot find the file specified", "docker daemon not running windows". Edge cases: CI runners often hit this because Desktop is still starting when the job runs. Poll docker info` in a wait loop before the first real command. Also confirm Desktop is in Linux containers mode if your images are Linux.

Source URL: https://docs.docker.com/desktop/troubleshoot/

Not specified by the original author.

TL;DR: Start the Docker service. On systemd run sudo systemctl start docker and sudo systemctl enable docker so it survives reboots, then docker ps should list containers instead of the error. This happens because the docker CLI is just a client; it needs the dockerd server process running to do anything.

The error

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

Fix it

1. Check whether the service exists and its state: sudo systemctl status docker Expected: either inactive (dead) (fixable) or Unit docker.service could not be found (not installed).

2. Start it: sudo systemctl start docker Expected: no output, exit code 0.

3. Enable it at boot so this does not come back after a reboot: sudo systemctl enable docker Expected: Created symlink /etc/systemd/system/multi-user.target.wants/docker.service ...

4. Verify the client can reach the daemon: docker ps Expected: a container table (possibly empty), not the error.

When this applies

• Fresh Linux install where Docker was installed but never started
• After a reboot, if the service was never enabled
• docker context ls shows the default unix socket context as current

When this does NOT apply

• The error says "permission denied" instead (socket exists but your user cannot read it; fix is the docker group, separate skill)
• Docker Desktop on macOS/Windows (the daemon runs inside a VM; start the Desktop app instead)
• DOCKER_HOST points at a remote or tcp address (context problem, separate skill)

Versions

Docker Engine 20.10 through 29.x on any systemd Linux distro. Non-systemd distros (Alpine/OpenRC) use sudo service docker start instead.

Why it happens

docker is a thin client that talks to the dockerd daemon over a unix socket. Package installs create the systemd unit but do not always start or enable it, so the first docker command after install or reboot finds no socket listener.

Edge cases

• WSL2 without systemd: enable systemd in /etc/wsl.conf or start dockerd manually in the background.
• If systemctl start docker fails, check sudo journalctl -u docker --no-pager | tail -30 for the real cause (often a bad /etc/docker/daemon.json).
• Inside CI containers, you need docker-in-docker or a mounted socket; starting the service inside the job container is not the fix.

Asked: how to fix Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. Verified answer: Fixes 'Cannot connect to the Docker daemon' errors when the Docker Engine service is stopped or never started. Use when every docker command fails with a daemon connection error on Linux. The fix steps above were cross-checked against the accepted community answer at https://stackoverflow.com/questions/44678725/cannot-connect-to-the-docker-daemon-at-unix-var-run-docker-sock-is-the-docker (so:44678725), which confirms the same resolution.