DockerDesktopVM' failed to start

mjn28 commented 4 years ago

[x ] I have tried with the latest version of my channel (Stable or Edge)
[ x] I have uploaded Diagnostics
Diagnostics ID: 5B79901F-53AD-4A6E-AD1F-7475C6CF997E/20200606174608

Expected behavior

Docker opens and runs after install

Actual behavior

Docker installs but will not run

An error occurred Docker.Core.HttpBadResponseException: Unhandled exception: job failed with message: 'DockerDesktopVM' failed to start. (Virtual machine ID 57E5E042-7680-41EE-8EDA-6917CAF996F1)

Information

Windows Version: Windows 10 Enterprise Version 1909
Docker Desktop Version:
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: no

Steps to reproduce the behavior

Download Docker Desktop
Run Docker Desktop
Error Occurs

mat007 commented 4 years ago

If you open the Hyper-V Manager and manually start the DockerDesktopVM, does it start? If yes, does Docker Desktop run correctly afterwards?

mjn28 commented 4 years ago

I actually got it working on a another computer (Windows 10 Pro) so I am able to use it now.

When I tried to start Docker on my Windows 10 Enterprise computer the DockerDesktopVM would be off and when I would try to start it I would get an error message and it would be unable to start

Albatross-Cyber commented 4 years ago

Hi,

I'm also getting the same error while starting the Docker as stated above. All the configurations are same for me also as mentioned by @mjn28 . I tried to start the VM as well but it is not getting started and giving me an error. Please help me with this.

Let me know if you want more details on this error.

Thanks in advance!

anupwarke commented 4 years ago

i am facing the same issue with windows 10 pro and Docker Desktop 2.3.0.3 with linux container enabled. Tried staring the VM separately from Hyper-V however failed. Does anyone have identified the solution for this? Please help. I am struggling for this issue last few weeks. Appreciate help

I opened a new issue https://github.com/docker/for-win/issues/7353

cybernetics commented 4 years ago

same here. not able to start docker for desktop. using win 10 Pro (v 2004) with WSL2. during the installation I did not select the checkbox to enable WSL2 backend, still, it seems like it's trying to use WSL2 backend.

also submitted docker diagnostic with id: 96DD888D-3B30-4F40-A5F5-BC139A7300EB/20200629051046

getting the following error during startup:

System.InvalidOperationException: Failed to deploy distro docker-desktop to %localappdata%\Docker\wsl\distro: exit code: -1 stdout: Error: 0xffffffff

stderr: at Docker.Core.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\WslCommand.cs:line 119 at Docker.Engines.WSL2.WSL2Provisioning.d16.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:line 142 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Engines.WSL2.WSL2Provisioning.d6.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\WSL2Provisioning.cs:line 44 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.Engines.WSL2.LinuxWSL2Engine.d23.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:line 91 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.TaskExtensions.d0.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Docker.ApiServices.StateMachines.StartTransition.d5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Docker.ApiServices.StateMachines.StartTransition.d5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92

docker-robott commented 3 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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 commented 3 years ago

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

docker / for-win