Docker fails to start on Windows 10

[sdevane]

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

[dsperling]

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

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
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version: open //./pipe/docker_engine: The system cannot find the file specified.

[Morgy93]

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

Output of 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: The requested address is not valid in its context.

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):

Failed to start VM "MobyLinuxVM": Fehler beim Starten von "MobyLinuxVM".

Fehler beim Starten von "MobyLinuxVM" (ID des virtuellen Computers 5534CC75-8A5C-4BA7-82BC-EB315C4DAA77).

"MobyLinuxVM": Fehler beim Starten des Arbeitsprozesses: Der Prozess wurde unerwartet beendet. (0x8007042B) (ID des virtuellen Computers 5534CC75-8A5C-4BA7-82BC-EB315C4DAA77).
   bei Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
   bei Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
   bei Docker.Core.Backend.BackendClient.Start(Settings settings)
   bei Docker.Actions.DoStart(Settings settings, Boolean showWelcomeWindow)
   bei Docker.Core.TaskQueue.<.ctor>b__16_0()

[eino-makitalo]

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]

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]

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]

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]

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

[dsperling]

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

Notes:

• 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]

@rneugeba Yeah, that what @friism said. 😁

[PetaPetaPeta]

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

[dsperling]

@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]

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]

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]

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.

So I'm creating a new thread over here: https://social.technet.microsoft.com/Forums/windows/en-US/home?forum=win10itprovirt

EDIT: https://social.technet.microsoft.com/Forums/windows/en-US/2df51b2d-18d3-463e-8fe5-3517bfb2950f/vm-failed-to-start-worker-process-the-process-terminated-unexpectedly?forum=win10itprovirt

[PetaPetaPeta]

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

[burgoyn1]

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

---

10 0 10586 0

[anusornc]

id = 5A0795B3-B950-4CC3-B296-F392FD31D7B2/2016-08-16_21-19-47

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.<.ctor>b__16_0()

[rn]

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]

I have a similar issue.

PS C:\Users\Tom> docker version

Client:
 Version:      1.12.1-rc1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   7889dc7
 Built:        Fri Aug 12 18:35:53 2016
 OS/Arch:      windows/amd64
 Experimental: true
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version: open //./pipe/docker_engin
e: The system cannot find the file specified.

Logs for a restart:

[01:29:36.934][Notifications  ][Info   ] Docker is restarting...
[01:29:36.968][NamedPipeClient][Info   ] Sending Stop()...
[01:29:36.997][NamedPipeServer][Info   ] Stop()
[01:29:37.024][HyperV         ][Info   ] Stop
[01:29:37.049][PowerShell     ][Info   ] Run script with parameters: -Stop True...
[01:29:38.149][HyperV         ][Info   ] VM MobyLinuxVM is stopped
[01:29:38.176][VpnKit         ][Info   ] Killing existing com.docker.slirp with PID 8444
[01:29:38.205][DataKit        ][Info   ] Killing existing com.docker.db with PID 3640
[01:29:38.237][NamedPipeServer][Info   ] Stop done.
[01:29:38.262][NamedPipeClient][Info   ] Received response for Stop
[01:29:38.313][NamedPipeClient][Info   ] Sending Start(Docker.Core.Settings)...
[01:29:38.350][NamedPipeServer][Info   ] Start(Docker.Core.Settings)
[01:29:38.379][HyperVGuids    ][Info   ] Installing GUIDs...
[01:29:38.406][HyperVGuids    ][Info   ] GUIDs installed
[01:29:38.433][Firewall       ][Info   ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[01:29:40.742][Firewall       ][Info   ] Ports are opened
[01:29:40.768][HyperV         ][Info   ] Create
[01:29:40.794][PowerShell     ][Info   ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[01:29:41.526][HyperV         ][Info   ] Using existing Switch: DockerNAT
[01:29:43.456][HyperV         ][Info   ] Using existing Switch IP address
[01:29:43.492][HyperV         ][Info   ] Using existing: MobyLinuxVM (state = Off)
[01:29:43.955][HyperV         ][Info   ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[01:29:43.986][DataKit        ][Info   ] Starting...
[01:29:44.021][PowerShell     ][Info   ] Run script...
[01:29:44.109][DataKit        ][Info   ] Started
[01:29:44.159][VpnKit         ][Info   ] Starting...
[01:29:44.225][PowerShell     ][Info   ] Run script...
[01:29:44.312][VpnKit         ][Info   ] Started
[01:29:44.384][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/config=static
[01:29:44.445][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[01:29:44.482][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[01:29:44.517][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[01:29:44.575][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/resolv.conf=nameserver 10.0.75.1
[01:29:44.610][Database       ][Info   ] Writing com.docker.driver.amd64-linux/network=hybrid
[01:29:44.656][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={"registry-mirrors":[],"insecure-registries":[],"debug":false}
[01:29:44.711][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[01:29:44.746][Database       ][Info   ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[01:29:44.828][DataKit        ][Info   ] 
[01:29:44.843][DataKit        ][Info   ] +7036us    Datakit  Starting com.docker.db.exe 09081b4 ...
[01:29:45.032][VpnKit         ][Info   ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[01:29:45.046][VpnKit         ][Info   ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[01:29:45.052][VpnKit         ][Info   ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[01:29:45.059][VpnKit         ][Info   ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19 max_connections:None vsock_path:
[01:29:45.066][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to e63516d7-4e39-4a2c-880e-f9bfb390ef19:0B95756A-9985-48AD-9470-78E060895BE7
[01:29:45.075][VpnKit         ][Debug  ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19
[01:29:45.081][VpnKit         ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[01:29:45.090][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to e63516d7-4e39-4a2c-880e-f9bfb390ef19:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[01:29:45.096][VpnKit         ][Debug  ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19
[01:29:46.342][DataKit        ][Info   ] 
[01:29:46.353][DataKit        ][Info   ] +1521241us       fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[01:29:46.343][Database       ][Info   ] Successfully wrote 9 value(s)
[01:29:46.367][HyperV         ][Info   ] Start
[01:29:46.377][PowerShell     ][Info   ] Run script with parameters: -Start True...
[01:29:46.431][HyperV         ][Info   ] Starting VM MobyLinuxVM...
[01:29:49.996][HyperV         ][Info   ] Hyper-V is running
[01:29:50.001][HyperV         ][Info   ] Create
[01:29:50.005][PowerShell     ][Info   ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[01:29:50.564][HyperV         ][Info   ] Using existing Switch: DockerNAT
[01:29:50.656][HyperV         ][Info   ] Using existing Switch IP address
[01:29:50.777][HyperV         ][Info   ] Using existing: MobyLinuxVM (state = Off)
[01:29:51.205][HyperV         ][Info   ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[01:29:51.217][HyperV         ][Info   ] Stop
[01:29:51.224][PowerShell     ][Info   ] Run script with parameters: -Stop True...
[01:29:51.382][HyperV         ][Info   ] VM MobyLinuxVM is stopped
[01:29:51.392][VpnKit         ][Info   ] Killing existing com.docker.slirp with PID 10728
[01:29:51.409][DataKit        ][Info   ] Killing existing com.docker.db with PID 3916
[01:29:51.446][HyperVGuids    ][Info   ] Installing GUIDs...
[01:29:51.451][HyperVGuids    ][Info   ] GUIDs installed
[01:29:51.457][Firewall       ][Info   ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[01:29:54.295][Firewall       ][Info   ] Ports are opened
[01:29:54.307][HyperV         ][Info   ] Create
[01:29:54.316][PowerShell     ][Info   ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[01:29:54.523][HyperV         ][Info   ] Using existing Switch: DockerNAT
[01:29:54.673][HyperV         ][Info   ] Using existing Switch IP address
[01:29:54.737][HyperV         ][Info   ] Using existing: MobyLinuxVM (state = Off)
[01:29:54.804][HyperV         ][Info   ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[01:29:54.818][DataKit        ][Info   ] Starting...
[01:29:54.826][PowerShell     ][Info   ] Run script...
[01:29:54.880][DataKit        ][Info   ] Started
[01:29:54.902][VpnKit         ][Info   ] Starting...
[01:29:54.915][PowerShell     ][Info   ] Run script...
[01:29:55.011][VpnKit         ][Info   ] Started
[01:29:55.022][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/config=static
[01:29:55.041][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[01:29:55.072][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[01:29:55.089][Database       ][Info   ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[01:29:55.098][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/resolv.conf=nameserver 10.0.75.1
[01:29:55.107][Database       ][Info   ] Writing com.docker.driver.amd64-linux/network=hybrid
[01:29:55.113][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={"registry-mirrors":[],"insecure-registries":[],"debug":false}
[01:29:55.123][Database       ][Info   ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[01:29:55.132][Database       ][Info   ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[01:29:55.504][DataKit        ][Info   ] 
[01:29:55.516][DataKit        ][Info   ] +14689us    Datakit  Starting com.docker.db.exe 09081b4 ...
[01:29:55.577][VpnKit         ][Info   ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[01:29:55.584][VpnKit         ][Info   ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[01:29:55.594][VpnKit         ][Info   ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[01:29:55.600][VpnKit         ][Info   ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19 max_connections:None vsock_path:
[01:29:55.607][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to e63516d7-4e39-4a2c-880e-f9bfb390ef19:0B95756A-9985-48AD-9470-78E060895BE7
[01:29:55.613][VpnKit         ][Debug  ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19
[01:29:55.618][VpnKit         ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[01:29:55.624][VpnKit         ][Info   ] com.docker.slirp.exe: connecting to e63516d7-4e39-4a2c-880e-f9bfb390ef19:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[01:29:55.630][VpnKit         ][Debug  ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://e63516d7-4e39-4a2c-880e-f9bfb390ef19
[01:29:56.864][Database       ][Info   ] Successfully wrote 9 value(s)
[01:29:56.869][HyperV         ][Info   ] Start
[01:29:56.875][PowerShell     ][Info   ] Run script with parameters: -Start True...
[01:29:56.873][DataKit        ][Info   ] 
[01:29:56.889][DataKit        ][Info   ] +1384240us       fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[01:29:56.923][HyperV         ][Info   ] Starting VM MobyLinuxVM...
[01:29:57.581][NamedPipeServer][Error  ] Unable to execute Start: 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 E63516D7-4E39-4A2C-880E-F9BFB390EF19)

'MobyLinuxVM' failed to start worker process: The process terminated unexpectedly. (0x8007042B). (Virtual machine ID E63516D7-4E39-4A2C-880E-F9BFB390EF19)
at Start-MobyLinuxVM, <No file>: line 228
at <ScriptBlock>, <No file>: line 322    at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   at Docker.Backend.LinuxContainersEngine.DoStart(Settings settings)
   at Docker.Backend.LinuxContainersEngine.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
[01:29:57.747][NamedPipeClient][Error  ] Unable to send Start: 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 E63516D7-4E39-4A2C-880E-F9BFB390EF19)

'MobyLinuxVM' failed to start worker process: The process terminated unexpectedly. (0x8007042B). (Virtual machine ID E63516D7-4E39-4A2C-880E-F9BFB390EF19)
at Start-MobyLinuxVM, <No file>: line 228
at <ScriptBlock>, <No file>: line 322
[01:29:57.885][Notifications  ][Error  ] 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 E63516D7-4E39-4A2C-880E-F9BFB390EF19)

'MobyLinuxVM' failed to start worker process: The process terminated unexpectedly. (0x8007042B). (Virtual machine ID E63516D7-4E39-4A2C-880E-F9BFB390EF19)

And trying to start it in hyper-v manager:

[rn]

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

[tomgeorge]

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

8e3a687d-9c88-4adc-8572-2630686aad6b

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]

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

Unable to start: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 'MobyLinuxVM' failed to start.

'MobyLinuxVM' failed to initialize.

'MobyLinuxVM' failed to start. (Virtual machine ID A15CBE3A-E9CA-4A19-84AA-DD833A837518)

'MobyLinuxVM' failed to initialize. (Virtual machine ID A15CBE3A-E9CA-4A19-84AA-DD833A837518)
at Start-MobyLinuxVM, <No file>: line 228
at <ScriptBlock>, <No file>: line 322
   at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   at Docker.Backend.LinuxContainersEngine.DoStart(Settings settings)
   at Docker.Backend.LinuxContainersEngine.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

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

[Morgy93]

@rneugeba
This whole issue is not related to docker.
There are several other people around who are facing the exact same issue while not beeing related to docker at all.
Have a look at: https://social.technet.microsoft.com/Forums/windows/en-US/2df51b2d-18d3-463e-8fe5-3517bfb2950f/vm-failed-to-start-worker-process-the-process-terminated-unexpectedly?forum=win10itprovirt

We obviously need to wait for a solution from Microsoft.

[Morgy93]

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]

Fun thing .. it's already reported on the official COMODO forums and they're aware of it: https://forums.comodo.com/bug-reports-cis/comodo-firewall-began-conflict-with-hyperv-t116351.0.html

[gabrielbarceloscn]

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]

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]

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

[Maliek]

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]

@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]

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]

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

[cascarr]

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]

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]

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]

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:

Windows 10
Version 1709 (OS Build 16299.125)

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]

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]

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.

Cheers!

[horros]

Just thought I'd chip in, I have problems with Docker starting on Windows 10 in bootcamp on a MacBook Pro maybe once a week or two weeks. Turns out the Mac does something strange and at some point starts telling Windows that it does not in fact support any form of virtualisation, which naturally causes Hyper-V to barf. A quick visit to MacOS and a reboot, and it works again.

I spent a fair few hours trying to figure this out before 2+2=5 and I connected the dots.

[sandeepamilineni]

#5010 Docker startup issue. Didnt have this issue previously.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked