Docker error during connect docker_engine on a Windows named pipe means the CLI never reached a daemon at all: it tried to open the pipe the engine listens on and found nothing there. On a Windows runner the reasons are short: the engine is not running yet, the client is pointed somewhere else, or the job wanted Linux containers and is on the wrong runner.
The client picks a transport from the context or the environment. On Windows that is a named pipe, and the pipe exists only while the engine is running.
What this error means
Every Docker command in the job fails the same way and fails instantly, including docker version and docker info , because nothing ever reached the engine. The URL in the message is the pipe path percent-encoded, which is what makes it look exotic: %2F%2F.%2Fpipe%2Fdocker_engine is just //./pipe/docker_engine . The Windows CLI talks to the engine over the npipe transport, written npipe:////./pipe/docker_engine , where Linux and macOS use unix:///var/run/docker.sock .…