‘MobyLinuxVM’ failed to start. (Virtual machine ID 8F62E181-9572-4E0F-AD43-747647FFE916)

[Thenilko]

Unable to start: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: ‘MobyLinuxVM’ failed to start.

‘MobyLinuxVM’ could not initialize.

‘MobyLinuxVM’ failed to start. (Virtual machine ID 8F62E181-9572-4E0F-AD43-747647FFE916)

‘MobyLinuxVM’ could not initialize. (Virtual machine ID 8F62E181-9572-4E0F-AD43-747647FFE916)
at Start-MobyLinuxVM, : line 291
at , : line 386
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 246
at Docker.Backend.ContainerEngine.Linux.Restart(Settings settings, String daemonOptions) in C:\gopath\src\github\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 182
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github\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\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

I`ve tried to reinstall it.
Install edge version of Docker
Disable and Enable - Hyper-V

But the problem still exist. Please for help

[mchalep]

I have this problem too. Clean install of Docker CE for Windows and reinstall of HyperV on Windows 10 - Fails every time I try to start the product. Can't believe Docker would release such buggy software that simply does not work.

[Thenilko]

Please help me. Its urgent! No one knows ?

[Athius]

I have exactly the same problem. The weird thing is when I try to reinstall Docker CE for Windows, the installer doesn't ask me any questions like the path to install or other stuff. I suspect the uninstall of docker is not well done (for example, I still had Kinematic installed...)

[motoronin]

I have exactly the same problem. Confirmed Hyper-V can be used to create VM's. Created and Delete MobyLinux VM using Hyper-V Manager and path to mobylinux.iso found at end of C:\Program Files\Docker\Docker\resources. After deleting MobyLinux.VM using Hyper-V manager. Rebooted to refresh for next step.

Using same path C:\Program Files\Docker\Docker\resources\mobylinux.iso. Tried creating MobyLinux VM using following command in Powershell as Administrator. PS C:\WINDOWS\system32> powershell -ExecutionPolicy Bypass -file "C:\Program Files\Docker\Docker\resources\MobyLinux.ps1" -create . Results are similar as describe in this thread.

ISO file at .\mobylinux.iso does not exist
At C:\Program Files\Docker\Docker\resources\MobyLinux.ps1:376 char:5

• throw "$args"
  

• ~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (ISO file at .\m... does not exist:String) [], RuntimeException
  • FullyQualifiedErrorId : ISO file at .\mobylinux.iso does not exist

Question: Is it possible to edit/correct/update the MobyLinux.ps1 with missing information at the line numbers described in the errors? Would appreciate any advice how remedy?

Running Windows 10 Pro | Version 1703 | Build 15063.674

Thanks!

[michaeldhealy]

Same issue:
The Virtual Machine Management Service failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running (Virtual machine ID 2DEC1BD6-A0F2-4935-BE5D-59F364158C22).

at Start-MobyLinuxVM, : line 315

at , : line 410

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 256

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 130

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

[renkaf]

I had the same issue.

After updating windows (1709) the issue was solved and docker started normally

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

[afisayo]

/remove-lifecycle stale

[rn]

please provide diagnostics IDs. Without there is no way we can help

[pthopa]

Getting the error below with Version: 18.03.1-ce-win65 (17513) on Windows 10 Enterprise.
Diagnostic id: 18D1AF83-F929-4439-958A-53314D83087B/2018-06-06_16-06-30
I tried using the latest edge version 18.05 and also reverting to an earlier version but nothing helped.
Using windows containers works fine. Problem is only when running Linux containers. So problem seems to be with starting the Linux vm.

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 9B63B6DB-0392-46ED-A356-79FF2B044372)
at Start-MobyLinuxVM, : line 300
at , : line 395
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 67
at Docker.Actions.<>c__DisplayClass14_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 51
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

[yesosuresh]

Encountered similar error while trying to switch from Windows container to Linux container. Kindly help.
Windows 10 Pro

Diagnostic id: B88C32B3-FEA2-4862-BE75-9FC13C9F5507/2018-06-19_10-43-50

PS C:\WINDOWS\system32> docker version
Client:
Version: 18.03.1-ce
API version: 1.37
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:12:48 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm

Server:
Engine:
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.24)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:21:42 2018
OS/Arch: windows/amd64
Experimental: false

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

Microsoft VmBus (Instance ID D41A1872-3740-41CE-A1EE-4522AB82F991): Failed to Power on with Error 'The system cannot find the path specified.'.

'MobyLinuxVM' failed to start. (Virtual machine ID 36D32D7F-D650-434F-83E9-8D6E8568012E)

'MobyLinuxVM' Microsoft VmBus (Instance ID D41A1872-3740-41CE-A1EE-4522AB82F991): Failed to Power on with Error 'The system cannot find the path specified.' (0x80070003). (Virtual machine ID 36D32D7F-D650-434F-83E9-8D6E8568012E)
at Start-MobyLinuxVM, : line 300
at , : line 395
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.<>c__DisplayClass23_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 264
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

[yesosuresh]

I've managed to fix it. For my case 'Microsoft Hyper-V Virtual Machine Bus Provider' was disabled under System devices. After enabled it, problem resolved.

[deckerbl]

Same issue. I have been working on this for quite a while but cannot figure it out. I have updated diagnostics. Please take a look. Cannot start MobyLinuxVM
Diag ID:
8DF2F5FD-457E-494D-B677-96F32A8DEC0B/20180720073806

[davehutton]

Did you ever figure out this issue? Running into the same

[deckerbl]

We do have it working but I am afraid I can only tell you what the problem was. Our problem ended up being that I could not launch a bootable ISO from Hyper-V on startup. So the mobylinux initial start up was failing. I actually couldn't get any ISO to boot in a Hyper-V virtual. We believe the issue was related to antivirus / firewall software, ESET. The security guys made some changes and it eventually started working.

[shankar1011]

i,m also facing almost similar type of issue.
Here i'm unable to see any "MobyLinuxVM".
Even my windows is updated and "Microsoft Hyper-V virtual machine bus provider" is also eanbled.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

[buddingPop]

Running into the same issue here.
Diagnostic id:
3AFEEFE6-EDA0-4671-B563-2DCEDCB2D049/20181128152436

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 E00991BB-BA4E-4295-B155-36DE4DAD29A7)

'MobyLinuxVM' failed to start worker process: %%3228369022 (0xC06D007E). (Virtual machine ID E00991BB-BA4E-4295-B155-36DE4DAD29A7)
at Start-MobyLinuxVM, : line 296
at , : line 412
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 92
at Docker.Actions.<>c__DisplayClass19_0.b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 74
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

[ebriney]

Hi @buddingPop. Can you try to uninstall VirtualBox it is not compatible with hyperV

[motoronin]

Greetings. Cannot Docker for Windows 10 coexist with any other VM environment installed? Is a scratch install only solution? Windows Dockers VM works. MobyLinux VM does not.

Running VMware Workstation. Hyper-V works when configured not to auto-start during boot.

[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