Docker failed to start on windows 10 enterprise LTSC #7576

Comments

rcm0rris commented Jul 7, 2020 •

[V] I have tried with the latest version of my channel (Stable or Edge) [V] I have uploaded Diagnostics Diagnostics ID:5084D55D-8DC1-4800-968B-84944AF7DCF6/20200707074440

Expected behavior

docker normal start up.

Actual behavior

docker failed to start.

Information

• Is it reproducible? Yes
• Is the problem new? Not sure
• Did the problem appear with an update? Not sure
• Windows Version: Windows 10 Enterprise LTSC
• Docker Desktop Version: 2.3.0.3 (45519)
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No, run on notebook install with windows 10 OS.

Steps to reproduce the behavior

1. Install docker (Docker Desktop Installer.exe)
2. After installation, follow exception shows, docker failed to start.

Docker.Core.HttpBadResponseException:
Unhandled exception: 序列未包含項目
於 Docker.Core.Logging.ClientExceptionInterceptor.d__0.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\ClientExceptionInterceptor.cs: 行 17
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 Docker.Core.Logging.LoggingMessageHandler.d__4.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\Logging\LoggingMessageHandler.cs: 行 37
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 System.Net.Http.HttpClient.d__58.MoveNext()
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.Core.BackendAPI.BackendAPIClient.d__10.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Core\BackendAPI\BackendAPIClient.cs: 行 93
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.Engines.LinuxHyperVEngine.d__12.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\LinuxHyperVEngine.cs: 行 57
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.ApiServices.StateMachines.TaskExtensions.d__0.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs: 行 29
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.ApiServices.StateMachines.StartTransition.d__5.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs: 行 67
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 Docker.ApiServices.StateMachines.StartTransition.d__5.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs: 行 92
Original stacktrace:
於 System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
於 Docker.Backend.HyperVInfrastructure.d__12.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs: 行 117
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.Backend.HyperVInfrastructure.d__10.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs: 行 97
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.Backend.HyperV.d__8.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperV.cs: 行 131
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 Docker.Backend.HttpAPI.HyperVAPIController.d__7.MoveNext() 於 C:\workspaces\stable-2.3.x\src\github.com\docker\pinata\win\src\Docker.Backend\HttpAPI\HyperVAPIController.cs: 行 35
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 System.Threading.Tasks.TaskHelpersExtensions.d__0.MoveNext()
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 System.Web.Http.Controllers.ApiControllerActionInvoker.d__1.MoveNext()
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 System.Web.Http.Controllers.ActionFilterResult.d__5.MoveNext()
— 先前擲回例外狀況之位置中的堆疊追蹤結尾 —
於 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
於 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
於 System.Web.Http.Dispatcher.HttpControllerDispatcher.d__15.MoveNext()

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

[SOLVED] : Docker Desktop — Failed to start DockerDesktopVM windows 10 #7353

Comments

anupwarke commented Jun 21, 2020

I have tried with the latest version of my channel (Stable or Edge) I have uploaded Diagnostics Diagnostics ID:

Expected behavior

Actual behavior

Information

• Windows Version: Window 10 Pro 1909
• Docker Desktop Version: 2.3.0.3
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

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

anupwarke commented Jun 21, 2020

ggoyal23 commented Jun 22, 2020

I am also getting the same behavior. Installed docker latest stable version (2.3.0.3) and it is giving an error on Windows 10 and failed to start.
«Docker.Core.HttpBadResponseException:
Unhandled exception: job failed with message: ‘DockerDesktopVM’ failed to restore. (Virtual machine ID F297D6A9-607A-4FCC-AD41-82B898CA5111)»

anupwarke commented Jul 12, 2020

@ggoyal23 Do you get any way out of this issue?
Thanks

anupwarke commented Jul 14, 2020

SOLVED

With lot of google and analysis of the issue, finally i resolved this issue. With more analysis to the issue i identified that the issue is not with Docker Desktop. When we run the Docker Desktop with Linux container, docker generally creates a VM named «DockerDesktopVM» over Hyper-V which actually provide the linux backend for docker.

The issue was with this VM only. the windows was not able to start this VM even with elevated user access. So i went around the Microsoft logs (Event Viewer) and analyzed the Hyper-V logs for failure. I observed «Virtual Machine Worker Process initialization has timed out, and will terminate.»
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin Source: Microsoft-Windows-Hyper-V-Worker Date: 6/22/2020 11:04:30 PM Event ID: 3062 Task Category: None Level: Error Keywords: User: NT VIRTUAL MACHINE\B090AFBE-5461-4896-8930-599E1D3DD0B8 Computer: XXXXXX-XXXXXXX Description: Virtual Machine Worker Process initialization has timed out, and will terminate. Event Xml:

3062 0 2 0 0 0x8000000000000000 147 Microsoft-Windows-Hyper-V-Worker-Admin

This pointed that windows is getting timed out while starting the VM. So i decided to check the VM starting manually using command line. Microsoft has documented well about the power-shell commands for all features. you can find the commands for starting VM. Reference Doc here

With command line analysis with Start-VM command, i got to know that there is AccessDenied error received for the command. Even you create any random VM, windows fails to start. I further googled it and tried lot of ways like VHDX & VMCX files may not have correct permission, add the permission to these files with ICacls for GUID blahblahblah. However failed.

Then i identified the comments in one of the blog for locagroup setting. Reference here — Comment «Nick Holness
Apr 7, 2015 at 3:49 PM«.

THANKS A LOT to Nick Holness, you rescued me from this problem

Working solution & Details:

1. Start the Docker Desktop with linux container enabled. You will be prompt with error. DO NOT CLICK ON QUIT AS IT WILL CLEAR THE VM & OTHER DETAILS
2. Open the PowerShell with administrator right
3. type command «Get-VM» and you list of VMs. this will list your docker VM as well «DockerDesktopVM»
4. type command «Start-VM -Name DockerDesktopVM» and enter. This will fail with error «AccessDenied:Microsoft.HyperV.PowerShell.Commands.StartVMCommand»
   THIS IS THE MAIN REASON FOR DOCKER FAILURE
5. type command «net localgroup administrators» and enter
   if you see «Everyone» as a part of the list administrators group then follow below steps else there is some other issue
6. type command «net localgroup administrators Everyone /delete» and enter
   NOTE: You might see SERVICE as a part of list the please delete SERVICE rather Everyone.
7. Reboot the system and try the docker start with administrator rights.

Not Sure, how the Everyone/SERVICE is added as a part of administrators group. but that was the main issue in my case Closing the issue.

Docker fails to start on Windows 10 #27

Comments

sdevane commented Aug 5, 2016 •

Expected behavior

Docker should start

Actual behavior

Docker fails to start and an Error reported in a window

Information

• Diagnostic ID from «Diagnose & Feedback» in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

Windows 10 pre and post Windows 10 anniverssary editions latest builds

1. installer Docker (also tried Beta version)
2. After installation completes the Docker is supposed to auto launch, but it fails to start

A diagnostic was uploaded with id: 5829B164-D591-4EF5-9283-A838DDE27F7D/2016-08-05_19-06-39

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

dsperling commented Aug 5, 2016

I am see a similar issue with the Anniversary update (version 1607). Here is my docker version output.

Morgy93 commented Aug 6, 2016

Same problem here.
I already posted mine here: moby/moby#25443
I’ll just copy it over here:

Output of docker version :

Additional environment details (AWS, VirtualBox, physical, etc.):

• Docker for Windows latest (08/05/16 MM/TT/JJ) (there’s no version info on the website, nor for the InstallDocker.msi)
• Windows 10 Pro
• version 1607
• build 14393.10

Steps to reproduce the issue:
I don’t know how to «reproduce», but all I did was to upgrade to the anniversary update and activated the Windows Subsystem for Linux (WSL) for Bash on Ubuntu on Windows
My docker worked just nice before

Describe the results you received:
The VM doesn’t start.

Describe the results you expected:
The VM does start / boot

Additional information you deem important (e.g. issue happens only occasionally):

eino-makitalo commented Aug 8, 2016

I fixed my problem with hyper-v console and choosing MobyLinuxVM and right mouse click to update settings to newest. Then it gave warning that it is not running with older version of Hyper-V but after that. I managed to start Docker again. Situation before: I updated my Windows 10 to newest version and docker for windows hangs in situation . «Starting «. Before update I killed all docker and Hyper-V processes ( I do not know if its realy needed)

Morgy93 commented Aug 8, 2016

I also upgraded the configuration from 7.0 to 8.0 (whatever that means), but no change.
After I removed the VM manually, it gets the 8.0 automatically, but still the same error occurs.
I cannot start the VM within the Hyper-V either:

It basically just states that it failed to start and that the process exited unexpectedly.

shairez commented Aug 8, 2016

I reverted back from the windows 10 anniversary update and now it works again.

So it might be a temporary solution for you too, until they’ll sort it out.

rn commented Aug 8, 2016

In general, several of us run the anniversary update (including WSL) and we do test releases on it as well and we haven’t seen any issues. So we are curious to get to the bottom of this.

@Morgy93 when you say «Upgraded configuration from 7.0 to 8.0» what do you mean?

friism commented Aug 8, 2016

@rneugeba I suspect it’s the Hyper-V VM configuration version

dsperling commented Aug 8, 2016 •

I was finally able to get the ‘stable’ release running on 1607 on a PC that had previous failures. Here are the steps I used.

1. Download the Docker for Windows ‘stable’ installer
2. Disconnect the PC from local networking
3. Uninstall any previous Docker version and ensure no VM’s are listed in the Hyper-V Manager
4. Install Docker for Windows ‘stable’
5. The last step allows you to launch Docker. Keep the box checked.
   • Docker tray app fails to display its icon, no notifications occur
   • Open Hyper-V Manager and I did not see any VM’s listed
   • Docker for Windows.exe is running and displayed in Task Manager
6. Reboot
7. Now I see the Docker notification and the tray icon.
8. Docker welcome window appears and everything is functional.
9. Reconnect to your local network

• No notices to reboot were displayed by the Installer.
• Installing ‘stable’ on previous Windows versions never required a reboot on this PC.
• Having the PC connected to my local network/Internet during install always results in a non-functioning Docker. Basically the system is in the same state as after step 5 above.

Update:

I have seen an install succeed with the PC connected to the network, although this is not reproducible.

1. Install Docker ‘stable’
2. Reboot
3. Wait 18 minutes
4. Docker welcome screen appears

Morgy93 commented Aug 9, 2016

PetaPetaPeta commented Aug 9, 2016

I seem to have some of the same issues. Should #28 and this be merged into one?

dsperling commented Aug 9, 2016 •

@PetaPetaPeta I agree that the issue I am seeing matches #28. However the original issue that @sdevane reported is a different issue in MobyLinuxVM:

‘MobyLinuxVM’ failed to start worker process: The process terminated unexpectedly.

So I suggest we keep #28 for the issue we are seeing and #27 reflects @sdevane original issue.

Morgy93 commented Aug 9, 2016

I guess I tried almost everything possible related to network stuff.
But I can even remove the network switch and network adapter within the VM and it fails to start with the same error as before.
So I’d assume that it’s not directly an issue with the network stuff for the VM to fail booting.

Even though I reported thousands of crash reports already, here’s the latest one: EF5CEE54-6553-4655-A810-98A1549E5A7D/2016-08-09_19-30-33

Morgy93 commented Aug 9, 2016

There seem to be other people out there who are having the same issue, probably using some whole different VM: https://social.technet.microsoft.com/Forums/en-US/a539273e-d80e-4dcb-993a-5b1dd0935728/vm-not-starting?forum=virtualserver
So maybe this has nothing to do with docker at all?!

Morgy93 commented Aug 9, 2016 •

I’m sure now. I tried the HoloLens emulator and Windows Phone emulator from Visual Studio 2015 (I used the Windows Phone emulator before and it always worked fine) and both VM fail to start with the same error as the docker VM.

PetaPetaPeta commented Aug 9, 2016 •

Temporary fix proposed here(#28 (comment)) is a working workaround for me.

burgoyn1 commented Aug 10, 2016 •

I am having the same issue with a fresh install of docker and I am completely lost. I keep getting the following error. I have tried to re-install docker, remove everything, but nothing works.

Failed to start VM «MobyLinuxVM»: ‘MobyLinuxVM’ failed to start.

‘MobyLinuxVM’ failed to initialize.

‘MobyLinuxVM’ failed to start. (Virtual machine ID 817661C8-62FA-4E75-9C79-79F4AF06CA50)

‘MobyLinuxVM’ failed to initialize. (Virtual machine ID 817661C8-62FA-4E75-9C79-79F4AF06CA50)
at Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Core.Backend.BackendClient.Start(Settings settings)
at Docker.Actions.<>c__DisplayClass26_0.b__0()
at Docker.Core.TaskQueue. b__16_0()

Attached are the log files. Anyone have any idea because I am lost. Below are the versions I am running:

PS C:\Users\Steven> docker —version
Docker version 1.12.0, build 8eab29e
PS C:\Users\Steven> docker-compose —version
docker-compose version 1.8.0, build d988a55
PS C:\Users\Steven> docker-machine —version
docker-machine.exe version 0.8.0, build b85aac1
PS C:\Users\Steven> docker version
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:15:28 2016
OS/Arch: windows/amd64
Error response from daemon: An invalid argument was supplied
PS C:\Users\Steven> [System.Environment]::OSVersion.Version

Major Minor Build Revision

anusornc commented Aug 16, 2016 •

The running command stopped because the preference variable «ErrorActionPreference» or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer ‘AJ’ because the object was not found. The object might have been deleted, or you might not have permission to perform the task. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.
at Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Core.Backend.BackendClient.Start(Settings settings)
at Docker.Actions.DoStart(Settings settings, Boolean showWelcomeWindow)
at Docker.Core.TaskQueue. b__16_0()

rn commented Aug 18, 2016

For those who still experience this issue, could you try un-installing and then install the latest Beta (Beta23) from here: https://download.docker.com/win/beta/InstallDocker.msi

We made some significant changes to the way the VM is created/started but also improved the diagnostics so it would be useful for us to know if this issue is resolved.
Thanks
Rolf

tomgeorge commented Aug 19, 2016 •

I have a similar issue.

Logs for a restart:

And trying to start it in hyper-v manager:

rn commented Aug 19, 2016

@tomgeorge thanks for the report. Could you provide the diagnostics id? Thanks

tomgeorge commented Aug 19, 2016 •

@rneugeba do you mean the crash report id? if so, one you can reference is:

Also, I have a few more pieces of info for you. Here’s my current docker version (I have tried stable and beta):

And looking through the event viewer in windows, I see a couple of things that might be of interest:

One Critical Error from source Hyper-V-VMMS, Event ID 15350, with the description «The virtualization infrastructure driver (VID) is not running.»

One Critical Error from source Hyper-V-VMMS, Event ID 14096, with the description «Virtual Machine Management service failed to start.»

And for each attempt to start docker, the following events:

Event ID 15130, ‘MobyLinuxVM’ failed to start. (Virtual machine ID )

Event ID 15500 ‘MobyLinuxVM’ failed to start worker process: The process terminated unexpectedly. (0x8007042B). (Virtual machine ID )’

VirtualBox and an OLD version of docker toolbox was installed on my computer when I enabled Hyper-V and installed docker for windows.

burgoyn1 commented Aug 20, 2016

Mine also still does not start running the new beta. I also reset docker to default settings and still nothing.

Diagnostic ID — 29B832CD-87FF-4E78-9985-50BAB90BABD7/2016-08-20_08-44-06

Morgy93 commented Aug 21, 2016

We obviously need to wait for a solution from Microsoft.

Morgy93 commented Aug 21, 2016

I can’t believe it — I found a solution to this.

I was using «COMODO Internet Security Pro» as my 3rd party firewall, anti virus, sandbox and whatsoever program — after I removed it completely and rebooted my pc, all of my Hyper-V VM are working again — including docker of course.
I also reported this here so we’ll see if this is the case for other users as well using third party firewall, av, sandbox, etc. software.

Finally I can benefit from the new «Bash on Ubuntu on Windows» terminal in addition to Docker for Windows. («Full» Linux experience on Windows, yay :D)

Morgy93 commented Aug 21, 2016

gabrielbarceloscn commented Apr 23, 2017

I was running on Windows 10 (inside a Parallels VM . MacOs)
Then reading this link:
https://docs.docker.com/docker-for-windows/troubleshoot/#hyper-v

I realized that virtualization wasn’t enabled on windows vm.
Changing some Parallels options and bingo. It’s working again. Nice.

chrismark commented Apr 23, 2017

Experienced something similar, Docker won’t start. Luckily I only had to restart Docker thru Settings > Reset > Restart Docker.. and that made it work.

londoncalling commented Apr 24, 2017

@gabrielrb thanks, it’s really nice to hear that the docs helped 🙂

Maliek commented Sep 12, 2017

These steps got me further, it is similar to some steps previously mentioned.

1. Download docker (stable)
2. Uninstall docker
3. disable hyper-v via the steps mentioned by @slpixe
4. restart PC
5. install docker, will notify you to enable hyper-v via a restart
6. Restart happens automatically
7. After reboot, it works fine 👌

londoncalling commented Sep 12, 2017

@gabrielrb @Maliek I’ll have another look at the docs and see if I can use your experience here to clarify some of this. Thanks for following up on this thread.

pori commented Nov 8, 2017

Had this is issue too. A really simple fix was disabling Docker for Windows on startup. Starting it manually seems to give Hyper-V enough time to do it’s thing and sync with Docker. Hope this helps any vagrants from Google!

CaCTuCaTu4ECKuu commented Nov 11, 2017

Windows 10 Pro 1703 b15063.674 File is missing error
Fix by creating VHD and Virtual Machines folders written in Hyper-V Settings

cascarr commented Nov 15, 2017

Please how do I solve this?

Unable to stop: The running command stopped because the preference variable «ErrorActionPreference» or common parameter is set to Stop: The specified module ‘Hyper-V’ was not loaded because no valid module file was found in any module directory.
at , : line 79
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV.cs:line 177
at Docker.Backend.ContainerEngine.Linux.DoStop() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 279
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 122
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

ximura commented Nov 15, 2017

Docker for Windows: Version 17.09.0-ce-win33 (13620)

Unable to create: The running command stopped because the preference variable «ErrorActionPreference» or common parameter is set to Stop: Creating the virtual machine failed.
at New-MobyLinuxVM, : line 201
at , : line 385
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV.cs:line 177
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 123
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

djadeja commented Nov 21, 2017

I had similar issue when I installed Docker CE for Windows Version 17.11.0-ce-rc4-win39 (14244) Channel: edge e557194 on Windows 10.

In Command/cmd windows, when I tried to run commands docker ps, docker version, docker info, the I got error like “error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.34/version” every time.

To resolved this issue,

1. I made “Hyper-V” off (Unchecked) from “Turn Windows feature on or off”, which required the OS to be restarted.
2. And after first restart, I made “Hyper-V” On (Checked), which again required the OS to be restarted.

After second restart, above docker commands started working and giving proper output.

So, turning Hyper-V off and then on resolved this issue for me.

mobiius commented Dec 22, 2017

Just thought I’d add my own crash log. (Since I keep having this issue.)

Unable to start: The running command stopped because the preference variable «ErrorActionPreference» or common parameter is set to Stop: ‘MobyLinuxVM’ failed to start. (Virtual machine ID 195AC639-88F1-4379-87D1-332FF73A1A21)

‘MobyLinuxVM’ failed to start worker process: %%3228369022 (0xC06D007E). (Virtual machine ID 195AC639-88F1-4379-87D1-332FF73A1A21)
at Start-MobyLinuxVM, : line 291
at , : line 386
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 245
at Docker.Backend.ContainerEngine.Linux.Restart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 181
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Windows version is:

It’s my work machine so I cant mess about with turning off AV solutions and what not. It was working fine up until Wednesday. (I did upgrade windows on Tuesday.)

mikethomas-ftdi commented Jan 16, 2018 •

Hey all, this frustrating error plagued me for three days. I attempted everything that I read above and nothing worked. For me it finally came to windows updates. I needed to have my windows FULLY updated. When you open the «Check for Updates» control panel, make sure you click «Check online for updates from Microsoft Update». My local policies are set in such a way that this is not done normally, and so the «Your device is up to date.» message was misleading for me as I needed to install a major Windows update. For the record, I am fully up to date with Window 10 Enterprise, Version 1709, OS Build 16299.192.

After I updated everything. I reset Hyper V via the steps mentioned by @slpixe. Then did a fresh install of the latest stable build of Docker for Windows and all was well. Be sure to restart manually after installing Docker, so the the commands show up in your shell windows.

Hopefully, this helps someone.

gavinmclelland commented Feb 3, 2018

The process cannot access the file ‘C:\Program Files\Docker\Docker\resources\mobylinux.iso’ because it is being used by another process.

Installed Docker for Windows via Lando on a fresh installation of Windows 10 Pro, Version 1709, OS build 16299.192.

Initial installation seemed successful. Dockers auto upgrade to latest version gave me the error above. I was able to fix the issue by Launching Hyper-V Manager to Shut down the MobyLinuxVM. I relaunched the Docker installer and the issue was resolved.