Error response from daemon: hcsshim::CreateComputeSystem: The virtual machine could not be started because a required feature is not installed

Question

I have downloaded Docker Desktop onto a Windows 10 Pro machine (1809). I am trying to do a docker run hello-world command, but I receive this error:

docker: Error response from daemon: hcsshim::CreateComputeSystem 0e3c581b7316f66fd396f6007f3260ded7d934c5e6d53c9fedba279b9c0044c2:
        The virtual machine could not be started because a required feature is not installed.
(extra info: {"SystemType":"Container","Name":"0e3c581b7316f66fd396f6007f3260ded7d934c5e6d53c9fedba279b9c0044c2","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\Docker\\windowsfilter\\0e3c581b7316f66fd396f6007f3260ded7d934c5e6d53c9fedba279b9c0044c2","Layers":[{"ID":"08298683-92e6-5d81-8efa-07df462bc835","Path":"C:\\ProgramData\\Docker\\windowsfilter\\da67c59750c9d72f917f4169d58fff3285b27d01c30c159f437b8ec8bace3fd3"},{"ID":"8ffbf2ed-0796-5433-969d-24c7c60eed76","Path":"C:\\ProgramData\\Docker\\windowsfilter\\20785c70b0b36964948ecf0180bbe644306ed1f70686864f3cf476229f3ae054"},{"ID":"d0522a69-fb9e-53ff-8eec-0492669a13de","Path":"C:\\ProgramData\\Docker\\windowsfilter\\2c662c56ef3ffafe3f5cb6180ac24154c081866bb0a6c0e3c27fa5a3bcc957a7"}],"HostName":"0e3c581b7316","HvPartition":true,"EndpointList":["63F24577-D177-4DE9-8071-9325D00D5499"],"HvRuntime":{"ImagePath":"C:\\ProgramData\\Docker\\windowsfilter\\2c662c56ef3ffafe3f5cb6180ac24154c081866bb0a6c0e3c27fa5a3bcc957a7\\UtilityVM"},"AllowUnqualifiedDNSQuery":true}).

score 16 · Answer 1 · edited Jan 30 '20 at 15:26

16

I had the same issue. Run Windows Powershell as "Administrator" and run the following commands to enable containers and Hyper -V. Restart machine after executing the second command -

Enable-WindowsOptionalFeature -Online -FeatureName containers –All
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All

edited Jan 30 '20 at 15:26

Community

1
1

answered Dec 13 '19 at 12:18

CloudArch

291
2
3

4

If running nested Hyper-V, remember to apply this on the host: Set-VMProcessor -VMName -ExposeVirtualizationExtensions $true – gimlichael Mar 07 '20 at 02:05
I tried this, but still getting the error. I'm running in a Virtual Machine – superachu Aug 19 '20 at 03:36
For me this worked even without restarting the machine. – Michael Villani May 03 '21 at 14:14
1

Outdated!, `Enable-WindowsOptionalFeature : Feature name containers is unknown.` – Bheid Jul 12 '21 at 05:50

score 2 · Answer 2 · answered Aug 26 '19 at 11:57

Enabling virtualization for BIOS fixed my issue. See below url, or search google to enable virtualization in BIOS. https://appuals.com/how-to-enable-vt-x-in-windows-10/

In Docker website it is mentioned that virtualization should be enabled as part of installation.

gReX · Answer 3 · 2021-12-10T21:00:29.523

May not really an answer for this question with the missing feature. But I had a similar error-Message and found this:

When runing my docker-compose up -d I got

ERROR: for xyz_server  Cannot start service sql_server: 
           hcsshim::CreateComputeSystem 5828482....c5e4: 
           The requested resource is in use.

When commented out in the docker-compose.yml the line with mem_limit: 8192m by adding #

container is starting. Got idea from dockerquestions

The resource in use was the memory.... May this will help someone.

Error response from daemon: hcsshim::CreateComputeSystem: The virtual machine could not be started because a required feature is not installed

3 Answers3

Linked