Closed ph3ll3r closed 4 years ago
@ph3ll3r Thank you for bringing this to our attention. Can you detail the specific document or tutorial you were following for this? It will help get the issue the appropriate attention.
I created a Hyper V VM WIN10 pro, version 1909 on a physical server using Windows Server 2019 enterprise data center. I downloaded Docker for windows 10 desktop. It installed properly or so I thought. I started docker in windows as the default. I tried to switch to Linux containers. A soon as I started Powershell and it crashed. DockerDesktopVM never started in the VM.
Below is the crash log:
Version: 2.2.0.0 (42247)
Channel: stable
Sha1: 2e3b4c91994e99da6458fe2291f2efbb3d5d80fe
Started on: 2020/01/29 15:33:49.516
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1909
Build: 18363
BuildLabName: 18362.1.amd64fre.19h1_release.190318-1202
File: C:\Users\pheller\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
[15:33:49.650][GUI ][Info ] Starting...
[15:33:49.670][ComponentVersions ][Info ] Edition community
[15:33:49.740][ComponentVersions ][Info ] Edition community
[15:33:50.002][AppMigrator ][Info ] Current version: 5. Latest version: 5
[15:33:50.002][GUI ][Error ] An instance is already running. Exiting.
[15:34:19.098][WindowsDaemon ][Info ] The description for Event ID '0' in Source 'gupdate' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Service stopped'
[15:34:21.107][WindowsDaemon ][Info ] The Software Protection service is starting.
Parameters:
Failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running.
'DockerDesktopVM' failed to start. (Virtual machine ID 3D70EE6E-DAC1-4DFE-934A-76DB06AB6C52)
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 3D70EE6E-DAC1-4DFE-934A-76DB06AB6C52). ---> 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 3D70EE6E-DAC1-4DFE-934A-76DB06AB6C52)
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 3D70EE6E-DAC1-4DFE-934A-76DB06AB6C52).
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E)
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E).
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E)
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E). ---> 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 6F8AF338-276F-447B-95F8-B43DFCFFA60E)
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E).
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E)
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 6F8AF338-276F-447B-95F8-B43DFCFFA60E).
at Start-MobyLinuxVM,
Trying to do a docker windows container and it generated the errors below:
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> docker version Client: Docker Engine - Community Version: 19.03.5 API version: 1.40 Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:22:37 2019 OS/Arch: windows/amd64 Experimental: false
Server: Docker Engine - Community Engine: Version: 19.03.5 API version: 1.40 (minimum version 1.24) Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:36:50 2019 OS/Arch: windows/amd64 Experimental: false PS C:\WINDOWS\system32> docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 960f02a6490f microsoft/mssql-server-windows-developer "powershell -Command…" 8 hours ago Created 0.0.0.0:11000->1433/tcp win-sql PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> docker version Client: Docker Engine - Community Version: 19.03.5 API version: 1.40 Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:22:37 2019 OS/Arch: windows/amd64 Experimental: false
Server: Docker Engine - Community Engine: Version: 19.03.5 API version: 1.40 (minimum version 1.24) Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:36:50 2019 OS/Arch: windows/amd64 Experimental: false PS C:\WINDOWS\system32> docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 60973b6f5d96 microsoft/mssql-server-windows-developer "powershell -Command…" About a minute ago Created 0.0.0.0:11002->1433/tcp win-sql2 960f02a6490f microsoft/mssql-server-windows-developer "powershell -Command…" 8 hours ago Created 0.0.0.0:11000->1433/tcp win-sql PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 960f02a6490f microsoft/mssql-server-windows-developer "powershell -Command…" 8 hours ago Created 0.0.0.0:11000->1433/tcp win-sql PS C:\WINDOWS\system32> docker run -d --name win-sql2 -p 11002:1433 -e ACCEPT_EULA=Y -e SA_PASSWORD=PH@123456789 microsoft/mssql-server-windows-developer 60973b6f5d96299634db007cf9b31b0917cff69e1581cee3b2212716a7564d64 C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem 60973b6f5d96299634db007cf9b31b0917cff69e1581cee3b2212716a7564d64: The virtual machine could not be started because a required feature is not installed. (extra info: {"SystemType":"Container","Name":"60973b6f5d96299634db007cf9b31b0917cff69e1581cee3b2212716a7564d64","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\ProgramData\Docker\windowsfilter\60973b6f5d96299634db007cf9b31b0917cff69e1581cee3b2212716a7564d64","Layers":[{"ID":"40f98a5b-d45d-57ff-bdf4-6b2b81a02aaf","Path":"C:\ProgramData\Docker\windowsfilter\ce42f057963e5ec0d8148c5652744a92ac536f322645771857a71b6005d5bc78"},{"ID":"23564109-3bf9-5f78-97c4-366f3b6bd689","Path":"C:\ProgramData\Docker\windowsfilter\bc3e649f1e81570f8d8c8e8f305a44e3a17e93742cb785e04040c0ec5da8d88f"},{"ID":"73d2cdcb-4a16-587a-b68d-a92898d7d470","Path":"C:\ProgramData\Docker\windowsfilter\5d2ab7ade640c854a0b121facf08110abca3979140338ff4d26bf0728e2f9ee7"},{"ID":"bbda8dbc-c6c5-500c-aa64-0f02ef0e033f","Path":"C:\ProgramData\Docker\windowsfilter\f8beaa613b9e022c7babfbc6ce24d781e57022e66bcb73e3300e0ed5f816de37"},{"ID":"6769618d-3718-5c58-8f78-b6b31c191d4b","Path":"C:\ProgramData\Docker\windowsfilter\60c1051cda5ed1e1b824d9e4cad564e479e1480ba07b1821dee8770de0918136"},{"ID":"27bede48-49f7-572a-9e3d-3fcf0c8cadd6","Path":"C:\ProgramData\Docker\windowsfilter\f49179deb75714f34e472676bc31483caca4efdf35c6ef0d5d50feb75664c487"},{"ID":"57c9de4b-e4c2-5ab1-8486-0d02be6b074c","Path":"C:\ProgramData\Docker\windowsfilter\f5344a51b16c7a4e49c43e13ea528194e3dcc2c85760f4439bc4d5726281bfe5"},{"ID":"c48ca4b1-3453-5324-9a5a-53ff8dabecd8","Path":"C:\ProgramData\Docker\windowsfilter\3001651abf08794b1ebde0aa43209ed7121a8371689c43b734a38cf19785a989"},{"ID":"009baae0-a872-5cc9-8697-849ab7f1036f","Path":"C:\ProgramData\Docker\windowsfilter\6eab7008d81198f3e131408c7e5850f8ab1b03d4d1cd4766c2e2352ea49a31f3"},{"ID":"6bcbc05d-0f69-5f5b-b7bb-44fe7928ee7a","Path":"C:\ProgramData\Docker\windowsfilter\440fb4a3c670f4e5d0d3a644b5646d266321c8ae7c4e6a412b455ebcc2768c28"},{"ID":"0a2a3599-0a0a-5f48-8b1e-c64e978b86bd","Path":"C:\ProgramData\Docker\windowsfilter\b0b161cf21f437a7f8be1c2e1fecf176aa8c130d7d6224911ea96e96f0c3f755"},{"ID":"152021c0-9328-571e-8bf4-83ba5ca9c50e","Path":"C:\ProgramData\Docker\windowsfilter\d9f20c61559909c0b62de4ee4c3741f0b1a8cec795b5738dc5506d0158939e1b"}],"HostName":"60973b6f5d96","HvPartition":true,"EndpointList":["304E5ECD-729B-4CFB-81B0-88F2F6D154D6"],"HvRuntime":{"ImagePath":"C:\ProgramData\Docker\windowsfilter\b0b161cf21f437a7f8be1c2e1fecf176aa8c130d7d6224911ea96e96f0c3f755\UtilityVM"},"AllowUnqualifiedDNSQuery":true}). PS C:\WINDOWS\system32>
@ph3ll3r Is there something in any specific Azure doc you are looking to have updated or are having issues with? If yes, please share the link to the documentation you are following.The scope for these doc issues is to help identify gaps and issues with the documentation.
Else, if you are looking for help with debugging issues I would suggest opening a post on MSDN and Stack Overflow communities. Our engineers will help you there with the troubleshooting.
@ph3ll3r Is there any update?
My question is what am I doing incorrectly?
On a physical server with Windows server 2019 enterprise, I created Hyper V multiple vms both Servers and win10 pro client. I installed docker Windows Desktop on one of the win10 pro VM client. The client virtual machine name is the Hyper-V Manager. I get an error when I try to start DockerDestopVM and the state remains off. Any Docker command crashes Docker.
Is there a conflict when nesting Hyper-V managers and VMs on the physical box ?
We will now close this issue as this is an old issue. If you are still seeing this issue, please tag me in a comment. I will reopen it and we will gladly continue the discussion.
Windows server 2019 enterprise Hyperv vm has docker installed and gets a error hcsshim::CreateComputeSystem: The virtual machine could not be started because a required feature is not installed. Probably since it is nested within the physical machine?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.