Docker on Windows cannot open the docker_engine pipe: access is denied
open //./pipe/docker_engine: Access is deniedShort answer
On Windows the docker CLI talks to the engine through a named pipe, and Docker Desktop restricts that pipe. If your account is not in the docker-users group, or you run the CLI as a different user than the one who started Docker Desktop, the pipe is refused. Add the account to docker-users and sign out and in again.
Fix it fast
1Find out which cause you have
Check which account you are, and whether Windows lists the docker-users group among its groups.
whoami whoami /groups2Match what you see, then jump to its fix
- 1
Docker Desktop shows 'Docker Desktop - Access Denied', or whoami /groups has no docker-users line.Your account is not in the docker-users groupFix - 2
docker works in one terminal and fails in another, for example an elevated shell of another account or a service.The CLI runs as a different user than the one who launched Docker DesktopFix
- 1
What does the error look like?
open //./pipe/docker_engine: Access is deniedDocker Desktop - Access Denied
Cause 1 of 2
Your account is not in the docker-users group
1Check
Docker Desktop needs docker-users membership for some privileged features. The installer adds only the person who ran the all-users install. Everyone else has to be added by hand.
whoami /groups2Fix
As an administrator, open Computer Management, go to Local Users and Groups, then Groups, then docker-users, and add the account. Sign out of Windows and sign in again so the new group applies.
# Computer Management
# Local Users and Groups > Groups > docker-users > Add
# then sign out and back in3Verify
After signing in again, the group is listed and docker answers.
whoami /groups
docker versionConfirmed by docs.docker.com
Cause 2 of 2
The CLI runs as a different user than the one who launched Docker Desktop
1Check
When Docker Desktop launches, the non-privileged pipes are restricted to the user who launched it, members of the local Administrators group, and LOCALSYSTEM. Any other account is refused.
whoami2Fix
Run the docker command as the user who started Docker Desktop, or start Docker Desktop from the account that needs to use it.
# Quit Docker Desktop, then start it again
# from the same Windows account that runs docker3Verify
The same account now gets a version for both Client and Server.
docker versionConfirmed by docs.docker.com
How do I stop it coming back?
- Add every developer account that uses Docker Desktop to docker-users when you roll out a machine.
- Run docker from the same Windows account that launched Docker Desktop, not from a second account's shell.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Servers
Docker Desktop on Windows stays on starting or shows a WSL error
HCS_E_HYPERV_NOT_INSTALLED
On Windows, a failed start is nearly always virtualization.
3 causes, each with a fixServers
apk cannot find py-pip in an Alpine Docker image
py-pip (no such package):
On current Alpine releases there is no package called py-pip.
2 causes, each with a fixServers
ng serve runs in the container but localhost:4200 does not open
The browser cannot open localhost:4200 although ng serve is running in the container
ng serve listens on localhost by default, which inside a container is the container itself.
3 causes, each with a fixServers
Angular routes return 404 from nginx when you refresh or open a link
The home page loads, but refreshing /some/route shows an nginx 404
Angular routes like /users/42 are not files, so nginx looks for them on disk and returns 404.
3 causes, each with a fixServers
AH00558: Apache in Docker cannot reliably determine its fully qualified domain name
Set the 'ServerName' directive globally to suppress this message
AH00558 is a warning, not a crash.
2 causes, each with a fixServers
Apache in a Docker container logs AH01114 when it proxies to a backend
AH01114: HTTP: failed to make connection to backend: api
Apache's proxy worker could not open a connection to the address in ProxyPass.
5 causes, each with a fix