Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Desktop Cannot Switch to Linux Containers #5834

Closed
2 tasks done
luqq opened this issue Feb 21, 2020 · 7 comments
Closed
2 tasks done

Docker Desktop Cannot Switch to Linux Containers #5834

luqq opened this issue Feb 21, 2020 · 7 comments

Comments

@luqq
Copy link

luqq commented Feb 21, 2020

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 2F161CBA-600B-4CC7-AA62-460DC9AE4C96/20200221071822

Expected behavior

Docker should switch to using Linux Containers.
Bios and Windows have Hyper-V enabled with all related features installed

Actual behavior

Receive error message:

Docker.Core.Backend.BackendDestroyException:
Unable to stop Hyper-V VM: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.
at <ScriptBlock>, <No file>: line 90
   at Docker.Core.Pipe.NamedPipeClient.<TrySendAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
   at Docker.Actions.<>c__DisplayClass39_0.<SwitchDaemon>b__0()
   at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass18_0.<.ctor>b__1()

  System.Management.Automation.RuntimeException:
  Unable to stop Hyper-V VM: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.
  at <ScriptBlock>, <No file>: line 90
     at Docker.Backend.HyperV.HandleException(String action, Exception ex)
     at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters, PowerShellConfiguration config)
     at Docker.Backend.ContainerEngine.Linux.DoStop()
     at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential)
  
     System.IO.FileNotFoundException:
     The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.

Information

  • Windows Version: Windows 10 Pro 1909 Build 18363
  • Docker Desktop Version: 2.2.1.0 (42746) edge
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

  1. Enable Hyper-V as per guidelines
  2. Install latest Docker Desktop
  3. Verify installation by running a Windows container
  4. Select "Switch to Linux Containers..." in the Docker Desktop tray icon
@anjali-aglawe
Copy link

Same here

Diagnostic Id: 4FD7ED37-B662-4C73-91C0-1AE75A655F88/20200224165003

Windows 10 Enterprise build 18362
Docker desktop 2.2.0.3 (42716)

@aranoe
Copy link

aranoe commented Feb 25, 2020

I fixed this by doing a factory reset, but this isn't certainly an option for everyone...

@erikbye
Copy link

erikbye commented Feb 26, 2020

See my comment on this other issue, might be related.

#5875 (comment)

@NiklausMaurer
Copy link

NiklausMaurer commented Mar 5, 2020

Same here

Diagnostic Id: B7BBF344-C734-4AC3-90A0-9632902AEC70/20200305122139

@luqq
Copy link
Author

luqq commented Mar 6, 2020

This bug has been fixed in:
Docker Desktop Version: 2.2.2.0 (43066) edge

@rreis27
Copy link

rreis27 commented May 14, 2020

Version: 2.3.0.2 (45183)
Channel: stable
Sha1: e9b671cd3cb844cb63ad6fd7c79a4d15424233c4
Started on: 2020/05/14 17:27:25.460
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1909
Build: 18363

17:30:30.966][EngineStateNotificationRecorder][Debug ] Registered state {"State":"failed to start","Mode":"linux","date":1589495430}
[17:30:30.966][LoggingMessageHandler][Info ] [2e0c4362] POST http://localhost/engine/state
[17:30:30.966][SystrayNotifications][Error ] Unhandled exception: job failed with message: 'DockerDesktopVM' failed to start. (Virtual machine ID BF046A6B-8CBF-4BD3-A002-9F41012A0994)

The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running

Diagnostic id: 1F851996-6F0E-430F-9F25-97AAFD5DFD29/20200515141301

@docker-robott
Copy link
Collaborator

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 docker locked and limited conversation to collaborators Jul 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants