The docker client must be run elevated to connect

Question

When I am trying to built docker app, I am getting below error. Command I am running is docker build -t node_curd_exe .

error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=h3q9gxeprezyco28agiqe9jp2&shmsize=0&t=node_curd_exe&target=&ulimits=null&version=1: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Anything else I can do ?

Go to the directory where the Docker is installed on your Windows installation drive and find a file named "Docker for Windows.exe", right click it and run it as administrator. See if it solves the problem. — 7_R3X, Aug 12 '19 at 11:38

score 73 · Accepted Answer · answered May 21 '20 at 13:32

73

I have encountered this problem myself. My problem was that I had configured Docker Desktop to not run at startup. As long as Docker Desktop is not running, you will not have the Docker daemon running, hence the error.

Quickly check whether you have a white whale in your taskbar before trying any more exotic solutions.

answered May 21 '20 at 13:32

RDavey

1,530
10
27

2

Good place to start. Mine docker wasn't starting at all, had to reinstall it. – user9999 Nov 03 '21 at 05:48
3

But my docker is running :/ – kame Nov 10 '21 at 10:41

score 6 · Answer 2 · edited Oct 27 '20 at 08:36

Try this:

"Hardware assisted virtualization and data execution protection must be enabled in the BIOS" Typically, this problem is due to a disabled Hyper-V or because the hypervisor agent is not running. Open a Windows shell as administrator and enable Hyper-V with:

dism /Online /Enable-Feature:Microsoft-Hyper-V /All

Reboot your machine and see if Docker for Windows starts. If the above doesn't work, open a Windows shell as administrator and enable the hypervisor with:

bcdedit /set hypervisorlaunchtype auto

If Docker for Windows is still not working properly, try the following additional solutions, which are based on instructions extracted from this Docker for Windows issue thread.

Reboot your machine and see if Docker for Windows starts. Copy this path: Control Panel\Programs\Programs and Features into a File Explorer address bar.

Click Turn Windows feature on or off on the left side of the Control Panel. Clear the Hyper-V check box in the list of Windows features.

Reboot your machine and start Docker for Windows (or reinstall if necessary). If the above doesn't work, then Virtualization Based Security (VBS) might be interfering and needs to be disabled. Try the following to disable VBS: Open the Local Group Policy Editor (gpedit.msc)

Go to Computer Configuration\Administrative Templates\System\Device Guard Disable VBS.

Worked for me ! only had to execute the first command and reboot, thanks a lot — saadoune, Nov 27 '21 at 16:29

score 3 · Answer 3 · answered Dec 02 '20 at 07:27

I had a similar issue : Docker Desktop was configured to run Linux containers but my Visual Studio project targeted Windows containers.

So after launching Docker, I right-clicked the whale (was red) in the taskbar's tray and selected the 'Switch to Windows containers' menu item.

An error message showed up talking about 'Deny write access for fixed drives not protected by Bitlocker' which was fixed by launching a regedit and putting a 0 for the following key : Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FVE\FDVDenyWriteAccess

Then repeating the tray action finally worked and the whale turned to white.

score 3 · Answer 4 · edited Jun 07 '22 at 21:14

3

Open PowerShell as Administrator and run:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

edited Jun 07 '22 at 21:14

Ryan M

18,333
31
67
74

answered May 30 '21 at 19:39

Eduardo Herrera

93
9

score 1 · Answer 5 · answered Aug 12 '19 at 11:41

1

try this on your CMD:

docker-machine create box
docker-machine env box

this issue still open

answered Aug 12 '19 at 11:41

LinPy

16,987
4
43
57

score 0 · Answer 6 · edited Jun 07 '22 at 21:13

0

What solved in my case, on Windows 11, was to turn off Hypervisor and Windows Subsystem for Linux, reboot and turn on again.

edited Jun 07 '22 at 21:13

Ryan M

18,333
31
67
74

answered Jun 07 '22 at 20:55

Claudio Shigueo Watanabe

878
15
24

score 0 · Answer 7 · edited May 31 '23 at 02:40

0

Start the Docker service
In the command line do the following:
```
net stop com.docker.service
```
Then:
```
net start com.docker.service
```

edited May 31 '23 at 02:40

user16217248

3,119
19
19
37

answered Apr 13 '23 at 11:40

Abeer Mousa

1
1

Consider `Ctrl + k` to highlight your code – Harsh Apr 18 '23 at 06:28

The docker client must be run elevated to connect

7 Answers7

Linked