Docker not starting in windows 10. "Unable to stop: Killed VM MobyLinuxVM did not stop"

[prem5192]

Expected behavior

Docker to start.

Actual behavior

Not able to start and getting the error message : "Unable to stop: Killed VM MobyLinuxVM did not stop"

Information

Logs for the issue is provided below :
Unable to stop: Killed VM MobyLinuxVM did not stop
at Fatal, : line 372
at Stop-VM-Force, : line 360
at Stop-MobyLinuxVM, : line 298
at , : line 379
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
at Docker.Backend.ContainerEngine.Linux.DoStop()
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Using docker stable version. Version 17.03.1-ce-win5 (10743) Channel: stable b18e2a5

Steps to reproduce the behavior

1. Started my windows 10 machine.
2. Waited for docker to start automatically on windows start up.
3. Docker is not starting and throws the above log.

Note : Docker was working fine for past few days. Facing this issue suddenly. Provide a quick response ASAP.

[simonferquel]

Could you provide a diagnostic ID please ?

[afurculita]

I have one with the same problem: "7A9EC775-E969-4FE8-B7B1-71338B6F73FF/2017-04-22_22-56-36"

[cavamagie]

same problem

[nxhoang]

same issue:
Diagnostic ID : 4EDE3868-4668-4AC8-9725-59B20FA5CF49/2017-05-27_18-36-02

[itpcc]

same :

Unable to stop: Killed VM MobyLinuxVM did not stop
at Fatal, <No file>: line 372
at Stop-VM-Force, <No file>: line 360
at Stop-MobyLinuxVM, <No file>: line 298
at <ScriptBlock>, <No file>: line 379
   at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   at Docker.Backend.ContainerEngine.Linux.DoStop()
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Diag ID: F1A76EF4-52A9-4D96-9DFB-90EE5A4CB9C8/2017-06-07_15-32-14

[dariusstrasel]

Same:

Unable to stop: Killed VM MobyLinuxVM did not stop
at Fatal, <No file>: line 376
at Stop-VM-Force, <No file>: line 364
at Stop-MobyLinuxVM, <No file>: line 302
at <ScriptBlock>, <No file>: line 383
   at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   at Docker.Backend.ContainerEngine.Linux.DoStop()
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
   at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters)
   at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Diagnostic ID:
16C2ABCA-E0D7-4815-8547-D27330119F5C/2017-07-14_16-18-07

[Premier]

Same on Win10 Enterprise

Unable to stop: Killed VM MobyLinuxVM did not stop
at Fatal, <No file>: line 376
at Stop-VM-Force, <No file>: line 364
at Stop-MobyLinuxVM, <No file>: line 302
at <ScriptBlock>, <No file>: line 383
   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 280
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) 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.<Register>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

[ssh24]

Facing the same issue. Any updates?

[sherryhw]

Is there any update? I always get this issue after I restart.

[gastongamietea]

Any updates? Same issue 47763231-CFD0-43C5-BACB-6525AE0F5955/2017-08-17_09-39-06

[combrinckd]

Is anyone going to look into this issue?

[Kirkaiya]

I just now installed Docker for Windows on my Windows 10 Enterprise (Creators Update, build 1703) laptop. Got the same error, same line numbers as posted by user "Premier" above. I installed, when I ran it the first time, it asked me to enable Hyper-V (nice that it does that), which it restarted to enable. On first subsequent login, got the "An error occurred" dialog window with this same error.

I sent the crash report, diagnostic id = E6AFFE95-E592-4623-B3F3-D9484DFB7AC5/2017-08-29_16-19-42

[ssh24]

Fixed the issue for me when I ran the Docker for Windows application as an Administrator.

[Kurdym]

I restored my windows disk today from an acronis backup.
Then I tried to start Docker. Failed with the error as described.
In Hyper-V manager I saw the state of the MobyLinuxVM was *critical.

So I deleted the MobyLinuxVM from within Hyper-V manager and restarted Docker.
MobyLinuxVM was recreated and now Docker runs fine.

[AbdulSayyed]

Restarted again as an adminstrator and it is working fine thanks to @ssh24

[pimp89]

Any other solution then running as an administrator ?
Same problem during the first start of docker.

DiagnosticID = 75B15248-C24F-4525-98E9-FC22F1DA3D0D/2018-01-25_15-54-20

[snegas]

@pimp89 you could try @Kurdym solution. Delete the MobyLinuxVM from withing Hyper-V manager and then restart your Docker.

[juanxjk]

Same issue. DiagnosticID = 48203ACF-9A65-46C7-97A6-243A77C54BA8/2018-02-20_10-33-40

[mattsgreen]

Please take a look at this issue: #1656
The suggested powershell cleanup of HyperV worked for me

[pimp89]

It can be closed 2018-03-06 22:47 GMT+01:00 shivakumarjava1 <notifications@github.com>:

…

Is this issue still open? Unable to stop: Killed VM MobyLinuxVM did not stop at Fatal, : line 400 at Stop-VM-Force, : line 388 at Stop-MobyLinuxVM, : line 326 at , : line 407 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 181 at Docker.Backend.ContainerEngine.Linux.DoStop() in C:\gopath\src\ github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 306 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 129 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 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#651 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD1_yESpRvVwbpodCv8wNYNm4JnuPNY3ks5tbwPYgaJpZM4M-45X> .

[Pampati-Rahul]

facing the same issue.
Not able to see the VM in hyper -v but still facing the same issue.
Unable to destroy: Killed VM MobyLinuxVM did not stop
at Fatal, : line 400
at Stop-VM-Force, : line 388
at Stop-MobyLinuxVM, : line 326
at , : line 408
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 181
at Docker.Backend.ContainerEngine.Linux.DoDestroy(Boolean keepVolume) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 319
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
ID:962F3DCB-FAB1-4C6F-9382-256CAA542174/2018-03-23_14-39-56
Any help here ?

[enderandpeter]

In my case, I have a strong feeling that ending the Docker Service in Task Manager and then starting Docker for Windows again allowed it to finally start everything back up normally.

[rahmanya]

I know this issue is closed, but just to add , I had similar problem, I restarted my machine and while docker was starting , it reported same problem so I restore docker to factory default and it's working.
Docker Version: 18.06.0-ce-win72 (19098)
OS: Windows 10 Pro

[enderandpeter]

I really wish someone would fix this. I've installed Docker for Windows on three different Windows machines in the past year and all of them experience the exact same problem.

[hamidh2]

i quited the running docker and then run the docker for windows as adminstrator after these step the docker run correctly for me!!!

[billavasunny]

Faced the exact same issue. Killed the process from Task Manager and ran as Administrator. Thanks to SSH24 above

[pbbhopp]

The same situation here( Win10( Version 10.0.17134) with Docker 2.0.0.3), after switch to Windows containers it was unable to return to Linux containers - an error occurred with the VM.
So, I stopped the Hyper-V process vmcompute.exe in the Task Manager. Then run it again as Admin, then switch Docker to Linux containers, it switched and runs well. Try this and return feedback.

[animesharma]

Same issue - Docker 2.0.0.3 on Windows 10 Enterprise.
Diagnostic ID: C38902AC-A545-4684-B35C-5B4660A844A4/20190624121609

[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