This error may indicate that the docker daemon is not running windows

04.11.202321.08.2022 admin 0 Comments

This error may indicate that the docker daemon is not running windows

«Docker Desktop Starting. » forever on Windows

I have tried so many ways but didn’t solve:

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I’ve found out another symptom leading to the solution is also related to WSL.

On one side, Docker service won’t start throwing this error:

error during connect: This error may indicate that the docker daemon is not running.: Get «http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version»: open //./pipe/docker_engine: The system cannot find the file specified.

And on the other, WSL is unresponsive. Attempting to run a WSL Distro or WSL command directly on CMD, won’t return any output at all. It will just hang in there.

So the solution is common to WSL and Docker. I’ve found in a question regarding the WSL issue, that the LxssManager Windows service is staled (it may show under services.msc as Stopping and all the buttons are greyed out, or I’ve even seen it Running apparently, but with the Docker and WSL issues above, so something is wrong with it still.)

First, we have to get LxssManager PID in order to kill it. Using an elevated shell, we can get it this way:

Having the PID, we can kill the process but beware I wasn’t able to kill it using kill or taskkill commands. I was getting the following error:

To effectively kill the process, do as following:

Replace XXXXX with PID, of course. Having done so, start the LxssManager service:

A word of warning: I’ve noted in some cases this is not enough for unknown (to me) technical reasons even if LxssManager service is shown as Running. Just repeat the above steps! Sometimes it works doing this once, sometimes doing it twice for some reason.

TL;DR

Docker unable to start on Windows 10 #2210

Comments

Getitdan commented Jul 15, 2018 •

Expected behavior

Docker should run on windows 10.

Actual behavior

Docker does not start.

Information

Also, the log.txt file includes the following errors:

What have I tried
This happens all over again (even after a full uninstalling & installing).
The docker icon in tray is red. I tried the following command (as suggested by: #587):
netsh interface ipv4 set address name=»vEthernet (DockerNAT)» static 10.0.75.1 255.255.255.0
This made docker tray icon to go white («Docker is running» status), instead of red, pretending to work. But. now, running «docker ps» results in the following error:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/containers/json: 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.

I have also tried to disable hyper-v, and let docker to start it. Still didn’t work.

This is really frustrating, as I cannot use Docker at all.
I made an upgrade to my Windows, from 7 to 10, only to get Docker running.
But all I’m getting are problems. Why isn’t the normal installation simply work?
Thanks!

Steps to reproduce the behavior

The text was updated successfully, but these errors were encountered:

bogere commented Jul 16, 2018

Getitdan commented Jul 16, 2018 •

@bogere Thanks for your input. My Windows is already fully updated:

I did nothing wrong, and docker won’t work. Please help me.

rn commented Jul 16, 2018

@Getitdan do you run any AV software by any chance? Have you tried a factory reset?

Getitdan commented Jul 16, 2018 •

@rn I have just disabled my Nod32 Antivirus, and reinstalled docker. But sadly, the same problem occurs.

I upgraded my Windows 7 to Windows 10. Do you have any other suggestion, or should I format my whole pc? (if this what you mean by factory reset). Thanks a lot for your response! It’s really important for me.

Update: usually docker is not running. But sometimes, after a «Restart» option inside docker, it is suddenly shown as running. Then, I try to run simple commands and get errors.

And:
docker ps
shows:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.37/containers/json: 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.

Getitdan commented Jul 17, 2018 •

Update:
I’ve tried this command:
docker-machine create default
and got:

Now, I disabled hyper-v, reinstalled docker, made a reset, and run:
docker-machine create default

Running pre-create checks.
Creating machine.
(default) Copying C:\Users\user.docker\machine\cache\boot2docker.iso to C:\Users\user.docker\machine\machines\default\boot2docker.iso.
(default) Creating VirtualBox VM.
(default) Creating SSH key.
(default) Starting the VM.
(default) Check network to re-create if needed.
(default) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
(default) 0%.
(default) Progress state: E_INVALIDARG
(default) VBoxManage.exe: error: Failed to create the host-only adapter
(default) VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at ‘F:\tinderbox\win-5.2\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp’ (76) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0038).
(default) VBoxManage.exe: error: Please contact the product vendor!
(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(default) VBoxManage.exe: error: Context: «enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)» at line 94 of file VBoxManageHostonly.cpp
(default)
(default) This is a known VirtualBox bug. Let’s try to recover anyway.
(default) Found a new host-only adapter: «VirtualBox Host-Only Ethernet Adapter #11»
(default) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP.
(default) The host-only adapter is corrupted. Let’s stop the VM, fix the host-only adapter and restart the VM
(default) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP.
Waiting for machine to be running, this may take a few minutes.
Detecting operating system of created instance.
Waiting for SSH to be available.
Detecting the provisioner.
Provisioning with boot2docker.
Copying certs to the local machine directory.
Copying certs to the remote machine.
Setting Docker configuration on the remote daemon.
Checking connection to Docker.
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env default

But docker is red.

Bottom line: nothing works. I’ve tried everything. Hope someone can help.

Docker forever in «Docker is starting..» at Windows task

I have installed a Docker stable version, and it took forever to start. Until now I have not seen the notification showing Docker is running. I can only see the Docker icon at the taskbar, showing Docker is starting.

I am running on Windows 10 Pro, Intel Core 2 Duo E8500, supporting virtualization.

18 Answers 18

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Thanks to https://github.com/docker/for-win/issues/7050, you should just simply run these two lines of commands inside powerShell: First Exit docker hub desktop, then run these commands in PowerShell:

Important Note: As @ Nachtalb said «I think it should be noted that this removes all docker containers and data. (WLS: Unregisters the distribution and deletes the root filesystem.)»

Personally, the most non-destructive method for myself has been to use:

Docker then indicates its starting the wsl services during it’s start process and my issues are resolved.

Other methods (like register/unregister) tend to be much more destructive and I lose configuration/data/volumes.

The Diagnose and Feedback menu should allow you to access the logs which are in:

It will generate a zip file with said logs and other information.

The default recommendation is:

But sometimes, all the options in the «Reset» pane are grayed out.

For testing, desactivating the AV (AntiVirus) is an option (again, just to be tested).

Check also the state of your Network adapater in the device manager.

If you have a third-party network product like a VPN (for instance https://www.zerotier.com/), try and uninstall it before restarting docker.

Resetting Hyper-V could help:

Go to «Turn Windows features on or off», disable all Hyper-V related features, reboot, then Docker should ask if it can enable and reboot for you.
Let it do that and see if it’s fixed. If not I’d probably try manually re-enabling Hyper-V.

I had a problem with most recent version. I uninstalled it, removed all docker folders and server and virtual switch from hyper-v and then reinstalled and it worked.

Cannot start Docker for Windows: Fails to Initialize #601

Comments