Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Servers, nginx and Docker

Docker on Windows cannot open the docker_engine pipe: access is denied

Erroropen //./pipe/docker_engine: Access is denied

Short 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.

  • Applies to Docker Desktop 4.x, Windows 11, PowerShell 7
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check which account you are, and whether Windows lists the docker-users group among its groups.

    whoami
    whoami /groups
  2. 2Match what you see, then jump to its fix

    1. 1Docker Desktop shows 'Docker Desktop - Access Denied', or whoami /groups has no docker-users line.Your account is not in the docker-users groupFix
    2. 2docker 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

What does the error look like?

  • open //./pipe/docker_engine: Access is denied
  • Docker 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 /groups

2Fix

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 in

3Verify

After signing in again, the group is listed and docker answers.

whoami /groups
docker version

Confirmed by docs.docker.com

Did this fix it?

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.

whoami

2Fix

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 docker

3Verify

The same account now gets a version for both Client and Server.

docker version

Confirmed by docs.docker.com

Did this fix it?

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

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.