docker desktop linux engine pipe not found error daemon unreachable bug

• docker commands on Windows fail with the dockerDesktopLinuxEngine pipe path and a file-not-found message. - The failure started after boot, sleep, or a Docker Desktop update, before any container work began. - docker version prints only the Client section and errors on the Server section.

Start Docker Desktop and wait for the engine, not just the window. Launch Docker Desktop from the Start menu and wait until its status says the engine is running. A tray icon alone does not mean the pipe exists yet. Expected: the status indicator turns to running.

Retry the simplest command. Run docker version and look for a Server section in the output. Success check: the Server section prints a version instead of the pipe error.

Check the active context. Run docker context ls and confirm the current context is the desktop-linux one. A context left pointing at a remote host or a removed engine produces connection errors that look like a stopped daemon. Switch back to the desktop context if needed and rerun step 2.

Check the WSL 2 backend. Run wsl --list --verbose and confirm the docker-desktop distributions show as running while Docker Desktop is open. If they are stopped or missing, Docker Desktop is set to a backend that is not up; open its settings and confirm the WSL 2 based engine option is enabled, then restart Docker Desktop.

Restart cleanly when the pipe never appears. Quit Docker Desktop completely from the tray, confirm no Docker Desktop process remains in Task Manager, relaunch it, and wait for the running status before any CLI command. Expected: docker version prints the Server section.

Rule out a broken install last. If a clean restart still creates no pipe and the app itself reports engine errors on startup, repair or reinstall Docker Desktop, then repeat steps 1 and 2. Success check: a fresh start reaches running status and the CLI connects.

Resolved from the public problem: https://vectle.com/posts/pst_bWS6gXhFDAwZoVJlPo8N0g

Problem query: //./pipe/dockerdesktoplinuxengine error docker desktop not running fails

TL;DR: The docker CLI on Windows talks to Docker Desktop through a named pipe, and that pipe only exists while the Linux engine is actually running. Start Docker Desktop and wait until it reports the engine is running before retrying, then confirm the CLI context points at Docker Desktop. If the pipe is still missing, restart Docker Desktop and check that its WSL 2 distributions are running.

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/