Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Modifying the properties of the device 'Memory' failed.

[jecot]

Expected behavior

Docker starts normally

Actual behavior

Docker throws an error and can't start

Information

468650FA-BB4D-4F09-B388-D9D0D6DDC67C/2017-10-12_08-48-19

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Modifying the properties of the device 'Memory' failed.

The operation cannot be performed while the object is in its current state.
at New-MobyLinuxVM, : line 216
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

Windows version: Windows 10 Pro 1703 build 15063.608
Docker version: Docker CE 17.09.0-ce-win33 (13620) Channel: stable 8c56a3b

[jecot]

I did try a few vain solutions mentionned in
#27
#390

[jasonbivins]

Hi @jecot
It looks like the MobyLinuxVM is stuck. According to the logs, it is still in use, but has the number zero for assigned memory and for minimum memory. Do you see anything strange in Hyper-V manager for assigned memory? Can you try deleting it ?

You can also try this in Powershell to remove it.
powershell -ExecutionPolicy ByPass -File "C:\Program Files\Docker\Docker\resources\MobyLinux.ps1" -destroy

[jecot]

Thanks @jasonbivins for helping out.

I've already tried that, with no positive results. The same error is thrown back.
I ended up installing Docker tools instead of running Docker natively on my windows machine (and it worked right off the bat) but this issue still needs to be addressed.

[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

[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