Closed LarryMai closed 3 years ago
worked in my case
PROBLEM
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 7F4D8E7C-BC87-433F-BCDB-D69991784B59).
This error message is usually because you're running Docker Desktop in a nested virtualization environment, such as: VMWare, VirtualBox, Azure, Xen, AWS EC2, Google Compute Engine
SOLUTION
VMWare vSphere "expose hardware assisted virtualization to the guest OS" under CPU settings
VMWare Fusion https://github.com/docker/for-win/issues/4470#issuecomment-585651502 Set option:
VMWare Workstation
Also some people have had luck doing this:
Windows Server in Hyper-V https://github.com/docker/for-win/issues/574#issuecomment-341621969
Azure windows 10 VM https://stackoverflow.com/a/50099965/1554346
So, I get this error when installing Docker for Windows in a Windows Server 2019 1809 guest OS running with Virtualbox 6.0.10. My host is a MacBook Pro running macOS 10.14.6.
Hyper-V paravirtualization is selected for the VM and both the Host Compute Service and Virtual Machine Management show as running in Windows. The DHCP tweak mentioned above doesn't have any impact.
There's no errors in the system event log when Docker Desktop throws the error, but there is a warning from Hyper-V-VmSwitch:
Failed to complete operation 'Policy Enum' on switch DD771604-3814-45D1-87DC-294E3E94C569 (Friendly Name: DockerNAT) Property Id {1550e863-4337-4917-a040-5a27dbc58b59} Instance Id {00000000-0000-0000-0000-000000000000}. Status = {Drive Not Ready}
The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed..
Hope this additional data may help a bit.
- Uninstall Docker 2. RESTART!!! (will not work if you don't)
- Install Docker
worked in my case
I don't know why but it worked in my case too.
It worked for me too... but after the latest update, it's back again.
I found that I needed to 'expose hardware assisted virtualization to the guest OS' in vSphere where I made the VM that Docker is running on.
I'm seeing the same error. Installed docker on my Windows 10 VM and the docker can't start "because one of the Hyper-V components is not running". The following two services are up running: Hyper-V Host Compute Service Hyper-V Virtual Machine Management
Please help!
I'm seeing the same error. Installed docker on my Windows 10 VM and the docker can't start "because one of the Hyper-V components is not running". The following two services are up running: Hyper-V Host Compute Service Hyper-V Virtual Machine Management
Please help! @lusiahli Yes, see my response above - this was exactly what was happening to me. I had to shut down the VM, goto the Windows 10 VM settings, under CPU you should be able to enable virtualization. That should fix the issue. Good luck
I'm seeing the same error. Installed docker on my Windows 10 VM and the docker can't start "because one of the Hyper-V components is not running". The following two services are up running: Hyper-V Host Compute Service Hyper-V Virtual Machine Management Please help! @lusiahli Yes, see my response above - this was exactly what was happening to me. I had to shut down the VM, goto the Windows 10 VM settings, under CPU you should be able to enable virtualization. That should fix the issue. Good luck
@mojiwa Thanks for the detailed info. My VM actually is a VDI managed by another group. I've sent a request with your suggestions. Will see.
Same error for me..
And for me.. Windows 10 started in VirtualBox 6.1 on Ubuntu 19.10 host. Docker Desktop 2.1.0.5 is started on this virtual Windows machine. Nested Intel virtualization is enabled in the VM settings. Just in case I also selected Hyper-V Paravirtualization Interface. Note, Intel nested virtualization is something new in this VBox version, so I won't wonder if it's buggy.
Stack trace is the same. I also tried to uninstall docker with reboot and reinstall again, but this didn't help. Both aforementioned Hyper-V services are started.
From logs I see
Ethernet switch port connected (switch name = '7427EF61-240B-421C-A59C-FE0FE5A43474', port name = '32D6DF5C-B0B3-4BCF-9716-159BFDB0DC8B', adapter GUID = '{F58FF8E9-DE1D-4ADB-9FC2-6A4D3AED6202}').
and The system successfully compacted 'c:\programdata\dockerdesktop\vm-data\dockerdesktop.vhdx'.
Port 81E97CA7-0D79-48C3-9597-C9EDF53D79BD (Friendly Name: ) successfully created on switch 7427EF61-240B-421C-A59C-FE0FE5A43474 (Friendly Name: DockerNAT).
Unfortunately ept instruction (for intel CPU for example) not passing into virtual cpu( https://www.virtualbox.org/manual/ch09.html#nested-virt
Therefore Hyper-V service not started in Windows, because it need support of ept instruction (see SLAT abbreviation)
Only Virtual-Box on Virtual-Box option available at this moment :((
So I guess Docker devs might also report this to MS which likely won't be fixed since the case is quite rare. And yet VBox can alter some paging settings via vboxmanage, not sure if it's possible to gain desire effect though. see https://www.virtualbox.org/manual/ch10.html 10.6
@mojiwa suggestion to "expose hardware assisted virtualization to the guest OS" under CPU settings worked for me. Running Windows Server 2019 on VMware 6.7.
- Uninstall Docker 2. RESTART!!! (will not work if you don't)
- Install Docker
worked in my case
I don't know why but it worked in my case too.
This solution worked for me as well. Thank you.
I have this issue still. My server is Win2019 VM server. What I found out is that since I run this server on Win2012 server host, this host OS does not support nested virtualization. For this I need Win10/Serv2019 host. and there is this command once you have all your OS software correct versions
Set-VMProcessor -VMName "your VM name" -ExposeVirtualizationExtensions $true
1. Uninstall Docker **2. RESTART!!!** (will not work if you don't) 2. Install Docker
worked in my case
After restart doesn't work, until reinstalling.
I am using VMware Fusion and installed Windows 10 and was getting the same error. I solved that issue by checking this option. Settings/Processors & Memory/Advanced/Enable hypervisor applications in this virtual machine. And It can be the reason for the lack of assigned Processors and RAM.
To add to this post as it really pertains to many other issues that folks have, is related to how the Docker Desktop for windows application installs. Specifically, when the installation is initiated, can we please have the installation include logic that looks for VMware Workstation? When a windows PC has VMware workstation installed, and the user installs Docker Desktop, it automatically installs Hyper-V components.
I would have seriously appreciated it if the installer had the logic to query my PC to look for an application called something like "VMware Workstation" and returned a warning before installation that would say, by continuing with this installation, VMware Workstation will no longer work.
This is because HyperV is a Type1 hypervisor and it will prevent VMware workstation from launching. The error that workstation gives isn't very helpful either and I spent half a day trying to figure out what happened, only to uninstall the HyperV components, which then broke Docker Desktop.
Just a thought.
- Uninstall Docker 2. RESTART!!! (will not work if you don't)
- Install Docker
worked in my case
I don't know why but it worked in my case too.
Lol, this worked for me too. I'm installing Docker Desktop on a Windows 10 VM using VirtualBox.
Version: 2.2.0.5 (43884)
Channel: stable
Sha1: 758e889f2c543b35d0bdfa51e811744f686d81b3
Started on: 2020/04/07 00:30:06.214
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows Server 2019 Standard
Edition: ServerStandard
Id: 1809
Build: 17763
BuildLabName: 17763.1.amd64fre.rs5_release.180914-1434
File: C:\Users\UserName\AppData\Local\Docker\log.txt
CommandLine: "C:\Program Files\Docker\Docker\Docker Desktop.exe"
You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[00:30:06.448][GUI ][Info ] Starting...
[00:30:06.495][ComponentVersions ][Info ] Edition community
[00:30:06.573][ComponentVersions ][Info ] Edition community
[00:30:07.308][AppMigrator ][Info ] Current version: 5. Latest version: 5
[00:30:07.527][TrackingSettings ][Info ] Crash report and usage statistics are enabled
[00:30:07.527][SegmentApi ][Info ] Usage statistic: Identify
[00:30:07.668][SegmentApi ][Info ] Usage statistic: appLaunched
[00:30:08.137][ApplicationTemplatesTracking][Info ] Cannot list templates
[00:30:08.137][SegmentApi ][Info ] Usage statistic: eventTemplatesInfo
[00:30:08.153][SegmentApi ][Info ] Usage statistic: heartbeat
[00:30:08.263][NpsStore ][Error ] Cannot read NPS ID: Could not find file 'C:\Users\UserName\AppData\Roaming\Docker.npsid'.
[00:30:08.279][NamedPipeClient ][Info ] Sending app/version()...
[00:30:08.295][NamedPipeClient ][Info ] Received response for app/version
[00:30:08.295][NamedPipeClient ][Info ] Sending app/migrate()...
[00:30:08.310][NamedPipeClient ][Info ] Received response for app/migrate
[00:30:08.295][NamedPipeServer ][Info ] app/version done in 00:00:00.
[00:30:08.310][NamedPipeServer ][Info ] app/migrate()
[00:30:08.310][NamedPipeServer ][Info ] app/migrate done in 00:00:00.
[00:30:08.342][NamedPipeClient ][Info ] Sending app/version()...
[00:30:08.342][NamedPipeClient ][Info ] Received response for app/version
[00:30:08.342][NamedPipeClient ][Info ] Sending version-packs/enable(community, Docker.Core.Settings)...
[00:30:08.342][NamedPipeServer ][Info ] app/version()
[00:30:08.357][NamedPipeClient ][Info ] Received response for version-packs/enable
[00:30:08.342][NamedPipeServer ][Info ] app/version done in 00:00:00.
[00:30:08.342][NamedPipeServer ][Info ] version-packs/enable(community, Docker.Core.Settings)
[00:30:08.357][NamedPipeServer ][Info ] version-packs/enable done in 00:00:00.0156240.
[00:30:08.357][NamedPipeClient ][Info ] Sending app/version()...
[00:30:08.357][NamedPipeClient ][Info ] Received response for app/version
[00:30:08.357][NamedPipeClient ][Info ] Sending engine/start(Linux, Docker.Core.Settings, Docker.Core.DaemonOptions, )...
[00:30:08.357][NamedPipeServer ][Info ] app/version()
[00:30:08.357][NamedPipeServer ][Info ] app/version done in 00:00:00.
[00:30:08.373][NamedPipeServer ][Info ] engine/start(Linux, Docker.Core.Settings, Docker.Core.DaemonOptions, )
[00:30:08.373][Linux ][Info ] Setting container engine status to Starting
[00:30:08.435][HyperV ][Info ] Stop
[00:30:08.435][PowerShell ][Info ] Run script with parameters: -Stop True -VmName DockerDesktopVM -SwitchName DockerNAT -Verbose True -ErrorAction Stop
[00:30:08.560][HyperV ][Info ] VM DockerDesktopVM is stopped
[00:30:08.576][HyperV ][Debug ] [stop] took 00:00:00.1406948 to run
[00:30:08.576][OptimizeDisk ][Info ] Optimize
[00:30:08.576][PowerShell ][Info ] Run script...
[00:30:10.303][VpnKit ][Info ] Killing existing vpnkit with PID 6908
[00:30:10.334][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 5456
[00:30:10.350][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 5456
[00:30:10.350][APIRequestLogger ][Info ] [90dca922]
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC). ---> Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected)
at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask)
at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_01.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
--- End of inner exception stack trace ---
at Start-MobyLinuxVM,
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC).
at Start-MobyLinuxVM,
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
Microsoft.HyperV.PowerShell.VirtualizationException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected)
at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask)
at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_01.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
[00:30:30.096][HyperV ][Error ] Unable to start Hyper-V VM: Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). ---> Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected)
at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask)
at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_01.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
--- End of inner exception stack trace ---
at Start-MobyLinuxVM,
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
Microsoft.HyperV.PowerShell.VirtualizationException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected)
at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask)
at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_01.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
[00:30:30.096][Linux ][Info ] Setting container engine status to FailedToStart [00:30:30.096][NamedPipeServer ][Error ] Unable to execute engine/start: Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
at Start-MobyLinuxVM,
Microsoft.HyperV.PowerShell.VirtualizationException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException:
'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected)
at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask)
at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_01.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
[00:30:30.143][GUI ][Info ] Sending Bugsnag report 3bf65d80-4494-42fb-98df-36b1ee0da7e2... [00:30:30.350][GUI ][Info ] Bugsnag report 3bf65d80-4494-42fb-98df-36b1ee0da7e2 sent [00:30:30.350][SegmentApi ][Info ] Usage statistic: eventCrash [00:30:30.381][Diagnostics ][Warning] Starting to gather diagnostics as User : 'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' gather. [00:30:45.685][GoBackendProcess ][Info ] time="2020-04-07T00:30:45-07:00" msg="external: GET /events 200 \"Go-http-client/1.1\" \"\"" [00:30:45.688][GoBackendProcess ][Info ] time="2020-04-07T00:30:45-07:00" msg="external: GET /forwards/list 200 \"Go-http-client/1.1\" \"\"" [00:32:44.516][GoBackendProcess ][Error ] time="2020-04-07T00:32:44-07:00" msg="unable to send a no-op event: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing open \\\\.\\pipe\\dockerFilesystemEvent: The system cannot find the file specified.\"" [00:45:09.291][Diagnostics ][Info ] Uploading diagnostics 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030 [00:45:14.905][Diagnostics ][Info ] Uploaded succesfully diagnostics 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030 [00:46:49.336][ErrorReportWindow ][Info ] Open logs
Diagnostic ID: 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030
Docker.Core.DockerException:
Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 470903BD-BECD-4578-98A4-0457823A58AF)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 470903BD-BECD-4578-98A4-0457823A58AF).
Version: 2.2.0.5 (43884) Channel: stable
Diagnostic ID: 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030
The Uninstall/RESTART/Install solution did NOT work for me
I use nested Virtualisation:
OS Name: Microsoft Windows Server 2019 Standard OS Version: 10.0.17763 N/A Build 17763 Version 1809 (OS Build 17763.1) Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Docker.Core.DockerException:
Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start. Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. 'DockerDesktopVM' failed to start. (Virtual machine ID 470903BD-BECD-4578-98A4-0457823A58AF) The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 470903BD-BECD-4578-98A4-0457823A58AF).
Version: 2.2.0.5 (43884) Channel: stable
Diagnostic ID: 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030
The Uninstall/RESTART/Install solution did NOT work for me
I use nested Virtualisation:
OS Name: Microsoft Windows Server 2019 Standard OS Version: 10.0.17763 N/A Build 17763 Version 1809 (OS Build 17763.1) Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Helped
Set-VMProcessor <VMName> -ExposeVirtualizationExtensions $true
in my case
Hello,
I am having a similar issue. My OS is Windows [10.0.16299.1747]. The Docker Desktop version is 19.03.8.
I cannot both switch into Linux Container or still cannot find a working image for windows. I even couldn`t run the hello-world image yet.
So far I tried the actions given below:
Most of the images for Windows Containers are not getting downloaded due to mismatch with my Windows version.
no matching manifest for windows/amd64 10.0.16299 in the manifest list entries
Here is the error log when trying to switch into Linux Container: (I don't get any error when switched back to windows container.)
Docker.Core.DockerException: Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start. at Start-MobyLinuxVM,
: line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.BackendNamedPipeServer. b8_2(Object[] args) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0. b 0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start. at Start-MobyLinuxVM,
: line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential) Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start. Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0`1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func`1 startTaskMethod, Func`2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet`1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)
at Docker.Core.Pipe.NamedPipeClient.
d5.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.<>cDisplayClass39_0. b0() at Docker.ApiServices.TaskQueuing.TaskQueue.<>cDisplayClass18_0.<.ctor>b__1()
It would be appreciated if you could provide feedback, I really wonder what I am doing wrong.
I'm having exactly the same issue too. Uninstall Docker > Reboot > Reinstall method does not work either.
The uninstall and reinstall method does not work for me
But the post Cannot enable hyper-v service works for me.
Just enable virtualization in BIOS.
I am using a Microsoft Surface (no option an always enabled). The DISM and Sfc options didn't fix my issue. https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker
The recovery clean start (without removing data) option was the only solution for me.
So I ran into this issue as well. I tried uninstalling, restarting and reinstalling with no success. So I tried starting the VM in Hyper-v just like @infraengineer-sre but that also failed to start. I found this article and after running bcdedit /set hypervisorlaunchtype Auto
everything worked like it should.
For me, according to the error, I just enabled SVM mode in BIOS, which is required for all Virtual Machine including Docker, and the issue was fixed.
I'm running in a Win10 VM on a Win10 host and had the same problem. I shut down the VM and ran this powershell command in an elevated session:
Set-VMProcessor -vmname docker2 -ExposeVirtualizationExtensions $true
Restarted the VM and it worked for me.
Hope this helps someone else
I am trying to install docker desktop(2.3.1.0) on a Windows 10 Pro, 1809 and its not starting.Its an Azure VM Its giving the below error:
Docker.Core.HttpBadResponseException: Unhandled exception: job failed with message: 'DockerDesktopVM' failed to start. (Virtual machine ID 9CC1AC9F-FA96-4A6E-BFFB-49B2C103750E)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 9CC1AC9F-FA96-4A6E-BFFB-49B2C103750E).
at Docker.Core.Logging.ClientExceptionInterceptor.1.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\HttpClientExtensions.cs:line 22 --- 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.Core.BackendAPI.BackendAPIClient.<StartHyperVVMAsync>d__11.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\BackendAPI\BackendAPIClient.cs:line 102 --- 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.LinuxHyperVEngine.<DoStartAsync>d__12.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\LinuxHyperVEngine.cs:line 60 --- 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.<WrapAsyncInCancellationException>d__0.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.<DoRunAsync>d__5.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.<DoRunAsync>d__5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 36 Original stacktrace: at Docker.Backend.HyperVInfrastructure.HandleUpdatedJob(CIMConcreteJob updatedJob) in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 800 at Docker.Backend.HyperVInfrastructure.<HandleMaybeAsyncJob>d__37.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 740 --- 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.Backend.HyperVInfrastructure.<StartVMAsync>d__29.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 588 --- 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.Backend.HyperV.<StartAsync>d__7.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperV.cs:line 102 --- 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.Backend.HttpAPI.HyperVAPIController.<StartAsync>d__8.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HttpAPI\HyperVAPIController.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 System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__1
1.MoveNext()
--- 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 System.Web.Http.Controllers.ApiControllerActionInvoker.
I have done all that is started above.Can someone please help?
Make sure your VM instance type supports nested virtualization.
@npab19 thanks for point me to the link.I re created a VM with supports nested virtualization and it works fine.
Version: 2.2.0.5 (43884) Channel: stable Sha1: 758e889f2c543b35d0bdfa51e811744f686d81b3 Started on: 2020/04/07 00:30:06.214 Resources: C:\Program Files\Docker\Docker\resources OS: Windows Server 2019 Standard Edition: ServerStandard Id: 1809 Build: 17763 BuildLabName: 17763.1.amd64fre.rs5_release.180914-1434 File: C:\Users\UserName\AppData\Local\Docker\log.txt CommandLine: "C:\Program Files\Docker\Docker\Docker Desktop.exe" You can send feedback, including this log file, at https://github.com/docker/for-win/issues [00:30:06.448][GUI ][Info ] Starting... [00:30:06.495][ComponentVersions ][Info ] Edition community [00:30:06.573][ComponentVersions ][Info ] Edition community [00:30:07.308][AppMigrator ][Info ] Current version: 5. Latest version: 5 [00:30:07.527][TrackingSettings ][Info ] Crash report and usage statistics are enabled [00:30:07.527][SegmentApi ][Info ] Usage statistic: Identify [00:30:07.668][SegmentApi ][Info ] Usage statistic: appLaunched [00:30:08.137][ApplicationTemplatesTracking][Info ] Cannot list templates [00:30:08.137][SegmentApi ][Info ] Usage statistic: eventTemplatesInfo [00:30:08.153][SegmentApi ][Info ] Usage statistic: heartbeat [00:30:08.263][NpsStore ][Error ] Cannot read NPS ID: Could not find file 'C:\Users\UserName\AppData\Roaming\Docker.npsid'. [00:30:08.279][NamedPipeClient ][Info ] Sending app/version()... [00:30:08.295][NamedPipeClient ][Info ] Received response for app/version [00:30:08.295][NamedPipeClient ][Info ] Sending app/migrate()... [00:30:08.310][NamedPipeClient ][Info ] Received response for app/migrate [00:30:08.295][NamedPipeServer ][Info ] app/version done in 00:00:00. [00:30:08.310][NamedPipeServer ][Info ] app/migrate() [00:30:08.310][NamedPipeServer ][Info ] app/migrate done in 00:00:00. [00:30:08.342][NamedPipeClient ][Info ] Sending app/version()... [00:30:08.342][NamedPipeClient ][Info ] Received response for app/version [00:30:08.342][NamedPipeClient ][Info ] Sending version-packs/enable(community, Docker.Core.Settings)... [00:30:08.342][NamedPipeServer ][Info ] app/version() [00:30:08.357][NamedPipeClient ][Info ] Received response for version-packs/enable [00:30:08.342][NamedPipeServer ][Info ] app/version done in 00:00:00. [00:30:08.342][NamedPipeServer ][Info ] version-packs/enable(community, Docker.Core.Settings) [00:30:08.357][NamedPipeServer ][Info ] version-packs/enable done in 00:00:00.0156240. [00:30:08.357][NamedPipeClient ][Info ] Sending app/version()... [00:30:08.357][NamedPipeClient ][Info ] Received response for app/version [00:30:08.357][NamedPipeClient ][Info ] Sending engine/start(Linux, Docker.Core.Settings, Docker.Core.DaemonOptions, )... [00:30:08.357][NamedPipeServer ][Info ] app/version() [00:30:08.357][NamedPipeServer ][Info ] app/version done in 00:00:00. [00:30:08.373][NamedPipeServer ][Info ] engine/start(Linux, Docker.Core.Settings, Docker.Core.DaemonOptions, ) [00:30:08.373][Linux ][Info ] Setting container engine status to Starting [00:30:08.435][HyperV ][Info ] Stop [00:30:08.435][PowerShell ][Info ] Run script with parameters: -Stop True -VmName DockerDesktopVM -SwitchName DockerNAT -Verbose True -ErrorAction Stop [00:30:08.560][HyperV ][Info ] VM DockerDesktopVM is stopped [00:30:08.576][HyperV ][Debug ] [stop] took 00:00:00.1406948 to run [00:30:08.576][OptimizeDisk ][Info ] Optimize [00:30:08.576][PowerShell ][Info ] Run script... [00:30:10.303][VpnKit ][Info ] Killing existing vpnkit with PID 6908 [00:30:10.334][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 5456 [00:30:10.350][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 5456 [00:30:10.350][APIRequestLogger ][Info ] [90dca922] GET http://localhost/features [00:30:10.360][GoBackendProcess ][Info ] time="2020-04-07T00:30:10-07:00" msg="external: GET /features 200 "" """ [00:30:10.370][APIRequestLogger ][Info ] [90dca922] GET http://localhost/features -> 200 OK (took 16ms) [00:30:10.371][VpnKitBridge ][Info ] Starting C:\Program Files\Docker\Docker\resources\vpnkit-bridge.exe --addr listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3 host [00:30:10.371][VpnKitBridge ][Info ] Started [00:30:10.371][HyperV ][Info ] Create [00:30:10.371][HyperVGuids ][Info ] Installing GUIDs... [00:30:10.371][Firewall ][Info ] Removing all existing rules... [00:30:10.371][HyperV ][Info ] filesharing does not need a Hyper-V NIC so omitting it [00:30:10.371][HyperVGuids ][Info ] GUIDs installed [00:30:10.371][PowerShell ][Info ] Run script with parameters: -Create True -VmName DockerDesktopVM -VhdPathOverride C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx -VhdSize 68719476736 -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 28 -PreferredIPAddress -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\resources\docker-desktop.iso -SwitchName -Verbose True -ErrorAction Stop [00:30:10.418][Firewall ][Info ] All existing rules are removed. [00:30:10.418][Firewall ][Info ] Opening ports for SMB... [00:30:10.449][Firewall ][Info ] Ports are opened [00:30:10.476][VpnKitBridge ][Info ] time="2020-04-07T00:30:10-07:00" msg="listening on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3..." [00:30:10.480][VpnKitBridge ][Info ] time="2020-04-07T00:30:10-07:00" msg="waiting for connection on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3..." [00:30:10.524][HyperV ][Info ] Setting CPUs to 2 and Memory to 2048 MB [00:30:10.727][HyperV ][Info ] Remove existing DVDs [00:30:12.185][HyperV ][Info ] Attach DVD C:\Program Files\Docker\Docker\resources\docker-desktop.iso [00:30:12.984][HyperV ][Info ] Disabled Guest Service Interface [00:30:13.000][HyperV ][Info ] Enabled Heartbeat [00:30:13.031][HyperV ][Info ] Disabled Key-Value Pair Exchange [00:30:13.046][HyperV ][Info ] Enabled Shutdown [00:30:13.078][HyperV ][Info ] Enabled Time Synchronization [00:30:13.109][HyperV ][Info ] Disabled VSS [00:30:13.296][HyperV ][Info ] VM created. [00:30:13.296][HyperV ][Debug ] [create] took 00:00:02.9256838 to run [00:30:13.296][PowerShell ][Info ] Run script '(Hyper-V\Get-VM DockerDesktopVM).Id.Guid'... [00:30:13.328][IsoConfig ][Info ] Generating CA Cert Bundle [00:30:13.343][IsoConfig ][Info ] CA Cert Bundle Generated [00:30:13.457][HyperV ][Info ] Start [00:30:13.473][PowerShell ][Info ] Run script with parameters: -Start True -VmName DockerDesktopVM -IsoFile C:\Program Files\Docker\Docker\resources\docker-desktop.iso -confIsoFile C:\ProgramData\DockerDesktop\tmp-d4w\config.iso -VhdPathOverride C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx -DockerIsoFile C:\Program Files\Docker\Docker\resources\docker.iso -Verbose True -ErrorAction Stop [00:30:13.551][HyperV ][Info ] Starting VM DockerDesktopVM... [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Setting handler to ignore all SIGPIPE signals [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Version is 218f01482560cba2fa863f9ad872ad51d1e717fc [00:30:13.566][VpnKit ][Info ] vpnkit.exe: System SOMAXCONN is 2147483647 [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Will use a listen backlog of 32 [00:30:13.566][VpnKit ][Info ] vpnkit.exe: No periodic Gc.compact enabled [00:30:13.566][VpnKit ][Error ] vpnkit.exe: Starting to watch : EINVAL [00:30:13.566][VpnKit ][Error ] vpnkit.exe: Failed to watch hosts file : invalid argument [00:30:13.566][VpnKit ][Warning] vpnkit.exe: There is no database: using hardcoded network configuration values [00:30:13.566][VpnKit ][Info ] vpnkit.exe: DNS server configured with no builtin DNS names; everything will be forwarded [00:30:13.566][VpnKit ][Info ] vpnkit.exe: 2 upstream DNS servers are configured [00:30:13.566][VpnKit ][Error ] vpnkit.exe: While watching /etc/resolv.conf: ENOENT [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Disabling transparent HTTP redirection [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Updating resolvers to use host resolver [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Secure random number generator is available [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Add(3): DNS configuration changed to: use host resolver [00:30:13.566][VpnKit ][Info ] vpnkit.exe: DNS server configured with builtin DNS names [ gateway.docker.internal -> 192.168.65.1, docker.for.win.gateway.internal -> 192.168.65.1, docker.for.win.http.internal -> 192.168.65.1, host.docker.internal -> 192.168.65.2, docker.for.win.host.internal -> 192.168.65.2, docker.for.win.localhost -> 192.168.65.2, vm.internal -> 192.168.65.3 ] [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Will use the host's DNS resolver [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Transparent HTTP redirection configuration file C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json has changed [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Reading transparent HTTP redirection from C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Watching transparent HTTP redirection configuration file C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json for changes [00:30:13.566][VpnKit ][Info ] vpnkit.exe: New Gateway forward configuration: [] [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Gateway forwards file C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json has changed [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Reading gateway forwards file from C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Watching gateway forwards file C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json for changes [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Configuration server_macaddr = f6:16:36:bc:f9:c6; max_connection = None; dns_path = None; dns = ; resolver = Host; domain = None; allowed_bind_addresses = 0.0.0.0; gateway_ip = 192.168.65.1; host_ip = 192.168.65.2; lowest_ip = 192.168.65.3; highest_ip = 192.168.65.14; dhcp_json_path = None; dhcp_configuration = None; mtu = 1500; http_intercept = None; http_intercept_path = C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json; port_max_idle_time = 300; host_names = host.docker.internal, docker.for.win.host.internal, docker.for.win.localhost; gateway_names = gateway.docker.internal, docker.for.win.gateway.internal, docker.for.win.http.internal; vm_names = vm.internal; udpv4_forwards = []; tcpv4_forwards = []; gateway_forwards_path = C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json; pcap_snaplen = 128 [00:30:13.566][VpnKit ][Error ] vpnkit.exe: While watching C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: ENOENT [00:30:13.566][VpnKit ][Error ] vpnkit.exe: Failed to read gateway forwards from C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: reading C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: No such file or directory. [00:30:13.566][VpnKit ][Info ] vpnkit.exe: New Gateway forward configuration: [] [00:30:13.566][VpnKit ][Info ] vpnkit.exe: Updating transparent HTTP redirection: { [00:30:13.566][VpnKit ][Info ] "exclude": "", [00:30:13.566][VpnKit ][Info ] "transparent_http_ports": [ [00:30:13.566][VpnKit ][Info ] 80 [00:30:13.566][VpnKit ][Info ] ], [00:30:13.566][VpnKit ][Info ] "transparent_https_ports": [ [00:30:13.566][VpnKit ][Info ] 443 [00:30:13.566][VpnKit ][Info ] ] [00:30:13.566][VpnKit ][Info ] } [00:30:13.707][HyperV ][Info ] Remove existing DVDs [00:30:14.188][HyperV ][Info ] Attach DVD C:\Program Files\Docker\Docker\resources\docker-desktop.iso [00:30:14.424][HyperV ][Info ] Attach Config ISO C:\ProgramData\DockerDesktop\tmp-d4w\config.iso [00:30:14.972][HyperV ][Info ] Attach Docker ISO C:\Program Files\Docker\Docker\resources\docker.iso [00:30:15.082][NPS ][Info ] NPS User id created [00:30:15.821][GUI ][Error ] Error getting credentials: [00:30:16.402][HyperV ][Error ] Unable to start Hyper-V VM: Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC). ---> Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0
1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher) --- End of inner exception stack trace --- at Start-MobyLinuxVM, : line 688 at , : line 811 [00:30:16.402][Linux ][Error ] Failed to start: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 0F8C5240-4ECE-4C89-B32C-9CD38B522BFC). at Start-MobyLinuxVM, : line 688 at , : line 811. Let's retry [00:30:16.402][Linux ][Info ] Setting container engine status to Starting [00:30:16.402][Installer ][Info ] Checking for features: Hyper-V [00:30:18.378][Installer ][Info ] Features installed [00:30:18.394][HyperV ][Info ] Hyper-V is running [00:30:18.394][HyperV ][Info ] Stop [00:30:18.394][PowerShell ][Info ] Run script with parameters: -Stop True -VmName DockerDesktopVM -SwitchName DockerNAT -Verbose True -ErrorAction Stop [00:30:18.488][HyperV ][Info ] VM DockerDesktopVM is stopped [00:30:18.488][HyperV ][Debug ] [stop] took 00:00:00.0937526 to run [00:30:18.488][OptimizeDisk ][Info ] Optimize [00:30:18.488][PowerShell ][Info ] Run script... [00:30:19.571][VpnKit ][Info ] Killing existing vpnkit with PID 6756 [00:30:19.602][VpnKitBridge ][Info ] Killing existing vpnkit-bridge with PID 6464 [00:30:19.602][HyperV ][Info ] Destroy [00:30:19.602][PowerShell ][Info ] Run script with parameters: -KeepVolume True -Destroy True -VmName DockerDesktopVM -SwitchName DockerNAT -Verbose True -ErrorAction Stop [00:30:19.711][HyperV ][Info ] VM DockerDesktopVM is stopped [00:30:19.711][HyperV ][Info ] Destroying Switch DockerNAT... [00:30:19.743][HyperV ][Info ] Removing VM DockerDesktopVM... [00:30:19.852][HyperV ][Debug ] [destroy] took 00:00:00.2499344 to run [00:30:19.852][Firewall ][Info ] Closing ports... [00:30:19.852][Firewall ][Info ] Removing all existing rules... [00:30:19.907][Firewall ][Info ] All existing rules are removed. [00:30:19.907][Firewall ][Info ] Ports are closed [00:30:19.907][HyperVGuids ][Info ] Removing GUIDs... [00:30:19.907][HyperVGuids ][Info ] GUIDs removed [00:30:19.907][HyperV ][Info ] Create [00:30:19.908][HyperV ][Info ] filesharing does not need a Hyper-V NIC so omitting it [00:30:19.908][PowerShell ][Info ] Run script with parameters: -Create True -VmName DockerDesktopVM -VhdPathOverride C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx -VhdSize 68719476736 -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 28 -PreferredIPAddress -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\resources\docker-desktop.iso -SwitchName -Verbose True -ErrorAction Stop [00:30:20.009][HyperV ][Info ] Creating VM DockerDesktopVM... [00:30:20.859][HyperV ][Info ] Setting CPUs to 2 and Memory to 2048 MB [00:30:21.126][HyperV ][Info ] Attach VHD C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx [00:30:22.004][HyperV ][Info ] Attach DVD C:\Program Files\Docker\Docker\resources\docker-desktop.iso [00:30:22.628][HyperV ][Info ] Disabled Guest Service Interface [00:30:22.644][HyperV ][Info ] Enabled Heartbeat [00:30:22.675][HyperV ][Info ] Disabled Key-Value Pair Exchange [00:30:22.691][HyperV ][Info ] Enabled Shutdown [00:30:22.707][HyperV ][Info ] Enabled Time Synchronization [00:30:22.722][HyperV ][Info ] Disabled VSS [00:30:23.066][HyperV ][Info ] VM created. [00:30:23.066][HyperV ][Debug ] [create] took 00:00:03.1574740 to run [00:30:23.113][HyperV ][Info ] Stop [00:30:23.113][PowerShell ][Info ] Run script with parameters: -Stop True -VmName DockerDesktopVM -SwitchName DockerNAT -Verbose True -ErrorAction Stop [00:30:23.224][HyperV ][Info ] VM DockerDesktopVM is stopped [00:30:23.224][HyperV ][Debug ] [stop] took 00:00:00.1106241 to run [00:30:23.224][OptimizeDisk ][Info ] Optimize [00:30:23.224][PowerShell ][Info ] Run script... [00:30:24.678][APIRequestLogger ][Info ] [ab6e1454] GET http://localhost/features [00:30:24.699][GoBackendProcess ][Info ] time="2020-04-07T00:30:24-07:00" msg="external: GET /features 200 "" """ [00:30:24.711][APIRequestLogger ][Info ] [ab6e1454] GET http://localhost/features -> 200 OK (took 25ms) [00:30:24.711][VpnKitBridge ][Info ] Starting C:\Program Files\Docker\Docker\resources\vpnkit-bridge.exe --addr listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3 host [00:30:24.711][VpnKitBridge ][Info ] Started [00:30:24.711][HyperVGuids ][Info ] Installing GUIDs... [00:30:24.711][HyperV ][Info ] Create [00:30:24.711][Firewall ][Info ] Removing all existing rules... [00:30:24.711][HyperV ][Info ] filesharing does not need a Hyper-V NIC so omitting it [00:30:24.711][HyperVGuids ][Info ] GUIDs installed [00:30:24.711][PowerShell ][Info ] Run script with parameters: -Create True -VmName DockerDesktopVM -VhdPathOverride C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx -VhdSize 68719476736 -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 28 -PreferredIPAddress -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\resources\docker-desktop.iso -SwitchName -Verbose True -ErrorAction Stop [00:30:24.727][Firewall ][Info ] All existing rules are removed. [00:30:24.727][Firewall ][Info ] Opening ports for SMB... [00:30:24.758][Firewall ][Info ] Ports are opened [00:30:24.812][VpnKitBridge ][Info ] time="2020-04-07T00:30:24-07:00" msg="listening on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3..." [00:30:24.816][VpnKitBridge ][Info ] time="2020-04-07T00:30:24-07:00" msg="waiting for connection on listen://00000000-0000-0000-0000-000000000000/000007CF-FACB-11E6-BD58-64006A7986D3..." [00:30:24.860][HyperV ][Info ] Setting CPUs to 2 and Memory to 2048 MB [00:30:25.017][HyperV ][Info ] Remove existing DVDs [00:30:25.377][HyperV ][Info ] Attach DVD C:\Program Files\Docker\Docker\resources\docker-desktop.iso [00:30:26.049][HyperV ][Info ] Disabled Guest Service Interface [00:30:26.065][HyperV ][Info ] Enabled Heartbeat [00:30:26.096][HyperV ][Info ] Disabled Key-Value Pair Exchange [00:30:26.112][HyperV ][Info ] Enabled Shutdown [00:30:26.144][HyperV ][Info ] Enabled Time Synchronization [00:30:26.160][HyperV ][Info ] Disabled VSS [00:30:26.303][HyperV ][Info ] VM created. [00:30:26.303][HyperV ][Debug ] [create] took 00:00:01.5926211 to run [00:30:26.303][PowerShell ][Info ] Run script '(Hyper-V\Get-VM DockerDesktopVM).Id.Guid'... [00:30:26.335][IsoConfig ][Info ] Generating CA Cert Bundle [00:30:26.350][IsoConfig ][Info ] CA Cert Bundle Generated [00:30:26.491][HyperV ][Info ] Start [00:30:26.491][PowerShell ][Info ] Run script with parameters: -Start True -VmName DockerDesktopVM -IsoFile C:\Program Files\Docker\Docker\resources\docker-desktop.iso -confIsoFile C:\ProgramData\DockerDesktop\tmp-d4w\config.iso -VhdPathOverride C:\ProgramData\DockerDesktop\vm-data\DockerDesktop.vhdx -DockerIsoFile C:\Program Files\Docker\Docker\resources\docker.iso -Verbose True -ErrorAction Stop [00:30:26.585][HyperV ][Info ] Starting VM DockerDesktopVM... [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Setting handler to ignore all SIGPIPE signals [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Version is 218f01482560cba2fa863f9ad872ad51d1e717fc [00:30:26.585][VpnKit ][Info ] vpnkit.exe: System SOMAXCONN is 2147483647 [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Will use a listen backlog of 32 [00:30:26.585][VpnKit ][Info ] vpnkit.exe: No periodic Gc.compact enabled [00:30:26.585][VpnKit ][Error ] vpnkit.exe: Starting to watch : EINVAL [00:30:26.585][VpnKit ][Error ] vpnkit.exe: Failed to watch hosts file : invalid argument [00:30:26.585][VpnKit ][Warning] vpnkit.exe: There is no database: using hardcoded network configuration values [00:30:26.585][VpnKit ][Info ] vpnkit.exe: DNS server configured with no builtin DNS names; everything will be forwarded [00:30:26.585][VpnKit ][Info ] vpnkit.exe: 2 upstream DNS servers are configured [00:30:26.585][VpnKit ][Error ] vpnkit.exe: While watching /etc/resolv.conf: ENOENT [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Disabling transparent HTTP redirection [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Updating resolvers to use host resolver [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Secure random number generator is available [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Add(3): DNS configuration changed to: use host resolver [00:30:26.585][VpnKit ][Info ] vpnkit.exe: DNS server configured with builtin DNS names [ gateway.docker.internal -> 192.168.65.1, docker.for.win.gateway.internal -> 192.168.65.1, docker.for.win.http.internal -> 192.168.65.1, host.docker.internal -> 192.168.65.2, docker.for.win.host.internal -> 192.168.65.2, docker.for.win.localhost -> 192.168.65.2, vm.internal -> 192.168.65.3 ] [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Will use the host's DNS resolver [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Transparent HTTP redirection configuration file C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json has changed [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Reading transparent HTTP redirection from C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Watching transparent HTTP redirection configuration file C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json for changes [00:30:26.585][VpnKit ][Info ] vpnkit.exe: New Gateway forward configuration: [] [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Gateway forwards file C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json has changed [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Reading gateway forwards file from C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Watching gateway forwards file C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json for changes [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Configuration server_macaddr = f6:16:36:bc:f9:c6; max_connection = None; dns_path = None; dns = ; resolver = Host; domain = None; allowed_bind_addresses = 0.0.0.0; gateway_ip = 192.168.65.1; host_ip = 192.168.65.2; lowest_ip = 192.168.65.3; highest_ip = 192.168.65.14; dhcp_json_path = None; dhcp_configuration = None; mtu = 1500; http_intercept = None; http_intercept_path = C:\Users\UserName\AppData\Roaming\Docker\http_proxy.json; port_max_idle_time = 300; host_names = host.docker.internal, docker.for.win.host.internal, docker.for.win.localhost; gateway_names = gateway.docker.internal, docker.for.win.gateway.internal, docker.for.win.http.internal; vm_names = vm.internal; udpv4_forwards = []; tcpv4_forwards = []; gateway_forwards_path = C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json; pcap_snaplen = 128 [00:30:26.585][VpnKit ][Error ] vpnkit.exe: While watching C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: ENOENT [00:30:26.585][VpnKit ][Error ] vpnkit.exe: Failed to read gateway forwards from C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: reading C:\Users\UserName\AppData\Roaming\Docker\gateway_forwards.json: No such file or directory. [00:30:26.585][VpnKit ][Info ] vpnkit.exe: New Gateway forward configuration: [] [00:30:26.585][VpnKit ][Info ] vpnkit.exe: Updating transparent HTTP redirection: { [00:30:26.585][VpnKit ][Info ] "exclude": "", [00:30:26.585][VpnKit ][Info ] "transparent_http_ports": [ [00:30:26.585][VpnKit ][Info ] 80 [00:30:26.585][VpnKit ][Info ] ], [00:30:26.585][VpnKit ][Info ] "transparent_https_ports": [ [00:30:26.585][VpnKit ][Info ] 443 [00:30:26.585][VpnKit ][Info ] ] [00:30:26.585][VpnKit ][Info ] } [00:30:26.663][HyperV ][Info ] Remove existing DVDs [00:30:27.022][HyperV ][Info ] Attach DVD C:\Program Files\Docker\Docker\resources\docker-desktop.iso [00:30:27.226][HyperV ][Info ] Attach Config ISO C:\ProgramData\DockerDesktop\tmp-d4w\config.iso [00:30:28.171][HyperV ][Info ] Attach Docker ISO C:\Program Files\Docker\Docker\resources\docker.iso [00:30:30.096][NamedPipeClient ][Error ] Unable to send engine/start: Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.BackendNamedPipeServer.b8_2(Object[] args) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential)
Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0
1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)[00:30:30.096][HyperV ][Error ] Unable to start Hyper-V VM: Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). ---> Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0
1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher) --- End of inner exception stack trace --- at Start-MobyLinuxVM, : line 688 at , : line 811 [00:30:30.096][Notifications ][Error ] Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.BackendNamedPipeServer.b8_2(Object[] args) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential)
Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0
1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)[00:30:30.096][Linux ][Info ] Setting container engine status to FailedToStart [00:30:30.096][NamedPipeServer ][Error ] Unable to execute engine/start: Docker.Core.Backend.BackendDestroyException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.BackendNamedPipeServer.b8_2(Object[] args) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
System.Management.Automation.RuntimeException: Unable to start Hyper-V VM: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7). at Start-MobyLinuxVM, : line 688 at , : line 811 at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions, Credential credential) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions, Credential credential)
Microsoft.HyperV.PowerShell.VirtualizationException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 03ADB2EC-E31D-4291-B206-D92E8743F0E7).
Microsoft.Virtualization.Client.Management.VirtualizationOperationFailedException: 'DockerDesktopVM' failed to start.
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running. at Microsoft.Virtualization.Client.Management.View.EndMethodReturnInternal(IVMTask task, VirtualizationOperation operation, Boolean affectedElementExpected) at Microsoft.Virtualization.Client.Management.VMComputerSystemBaseView.EndSetState(IVMTask setStateTask) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.<>c__DisplayClass4_0
1.<ConvertActionToFunction>b__0(T x) at Microsoft.HyperV.PowerShell.ExtensionMethods.OperationWatcherExtensions.PerformOperationWithReturn[T](IOperationWatcher watcher, Func
1 startTaskMethod, Func2 endTaskMethod, String taskDescription, VirtualizationObject targetObject) at Microsoft.HyperV.PowerShell.VirtualMachine.ChangeState(VirtualMachineAction action, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.StartVM.ProcessOneOperand(VirtualMachine vm, IOperationWatcher operationWatcher) at Microsoft.HyperV.PowerShell.Commands.VirtualizationCmdlet
1.ProcessOperands(IList`1 operands, IOperationWatcher operationWatcher)[00:30:30.143][GUI ][Info ] Sending Bugsnag report 3bf65d80-4494-42fb-98df-36b1ee0da7e2... [00:30:30.350][GUI ][Info ] Bugsnag report 3bf65d80-4494-42fb-98df-36b1ee0da7e2 sent [00:30:30.350][SegmentApi ][Info ] Usage statistic: eventCrash [00:30:30.381][Diagnostics ][Warning] Starting to gather diagnostics as User : 'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' gather. [00:30:45.685][GoBackendProcess ][Info ] time="2020-04-07T00:30:45-07:00" msg="external: GET /events 200 "Go-http-client/1.1" """ [00:30:45.688][GoBackendProcess ][Info ] time="2020-04-07T00:30:45-07:00" msg="external: GET /forwards/list 200 "Go-http-client/1.1" """ [00:32:44.516][GoBackendProcess ][Error ] time="2020-04-07T00:32:44-07:00" msg="unable to send a no-op event: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing open \\.\pipe\dockerFilesystemEvent: The system cannot find the file specified."" [00:45:09.291][Diagnostics ][Info ] Uploading diagnostics 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030 [00:45:14.905][Diagnostics ][Info ] Uploaded succesfully diagnostics 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030 [00:46:49.336][ErrorReportWindow ][Info ] Open logs
Diagnostic ID: 0B245A32-F8D5-4CFD-A756-FA5BE242876A/20200407073030
I was facing the similar issue, attached logs. Tried almost everything mentioned in this thread, none helped. Surprisingly, The issue was with the wireless driver, I didn't had proper wireless driver installed which was blocking the Hyper V to start the VM.
Resolution : Just disabled my wireless driver from Device Manager and everything seems to be working now.
I am trying to install docker desktop(2.3.1.0) on a Windows 10 Pro, 1809 and its not starting.Its an Azure VM Its giving the below error:
Docker.Core.HttpBadResponseException: Unhandled exception: job failed with message: 'DockerDesktopVM' failed to start. (Virtual machine ID 9CC1AC9F-FA96-4A6E-BFFB-49B2C103750E)
The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running (Virtual machine ID 9CC1AC9F-FA96-4A6E-BFFB-49B2C103750E). at Docker.Core.Logging.ClientExceptionInterceptor.d0.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\Logging\ClientExceptionInterceptor.cs:line 17 --- 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.Core.Logging.LoggingMessageHandler.d4.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\Logging\LoggingMessageHandler.cs:line 37 --- 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 System.Net.Http.HttpClient.d58.MoveNext() --- 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.Core.HttpClientExtensions.d1
1.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\HttpClientExtensions.cs:line 22 --- 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.Core.BackendAPI.BackendAPIClient.<StartHyperVVMAsync>d__11.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Core\BackendAPI\BackendAPIClient.cs:line 102 --- 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.LinuxHyperVEngine.<DoStartAsync>d__12.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\LinuxHyperVEngine.cs:line 60 --- 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.<WrapAsyncInCancellationException>d__0.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.<DoRunAsync>d__5.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.<DoRunAsync>d__5.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 36 Original stacktrace: at Docker.Backend.HyperVInfrastructure.HandleUpdatedJob(CIMConcreteJob updatedJob) in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 800 at Docker.Backend.HyperVInfrastructure.<HandleMaybeAsyncJob>d__37.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 740 --- 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.Backend.HyperVInfrastructure.<StartVMAsync>d__29.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperVInfrastructure.cs:line 588 --- 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.Backend.HyperV.<StartAsync>d__7.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV\HyperV.cs:line 102 --- 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.Backend.HttpAPI.HyperVAPIController.<StartAsync>d__8.MoveNext() in C:\workspaces\master\src\github.com\docker\pinata\win\src\Docker.Backend\HttpAPI\HyperVAPIController.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 System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__1
1.MoveNext() --- 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 System.Web.Http.Controllers.ApiControllerActionInvoker.d1.MoveNext() --- 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 System.Web.Http.Controllers.ActionFilterResult.d5.MoveNext() --- 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 System.Web.Http.Dispatcher.HttpControllerDispatcher.d__15.MoveNext()I have done all that is started above.Can someone please help?
Check if you have any driver that could be causing the issue, disable the problematic drivers, you could also try restarting the vmms and vmbus service on your windows machine.
I have this issue still. My server is Win2019 VM server. What I found out is that since I run this server on Win2012 server host, this host OS does not support nested virtualization. For this I need Win10/Serv2019 host. and there is this command once you have all your OS software correct versions
Set-VMProcessor -VMName "your VM name" -ExposeVirtualizationExtensions $true
This fixed my issue, thanks! (Hyper-V Guest, W10 Pro)
This tip fixed it for me. While leaving the error message dialog box open, click the system tray icon to open the context menu, and click 'switch to windows containers'. https://forums.docker.com/t/cannot-enable-hyper-v-service/94086/21 (My config: Windows 2019 Standard on VMware)
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
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
Expected behavior
Every thing is fine.
Actual behavior
Information
Steps to reproduce the behavior
environment: windows 10.018362.30
Step : no need run any docker file. just install the latest version of Docker Desktop and run