How to fix: Error response from daemon: container *** encountered an error during CreateContainer: failure in a Windows system call: No hypervisor is present on this system

The problem

Last week I provided a Docker on Windows workshop for one of our customers. Some developers got stuck in the installation of Docker on Windows on their Windows 10 development machines. While the Docker on Windows installer succeeded, they got the following issue thrown by the Docker daemon when trying to initialize new Windows containers from the Docker CLI.

C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: container 6314c9d6f09bc751b86d99277

e0840037c78ca5da31a591a0544bb8de1b29179 encountered an error during CreateContainer: failure in a Windows system call: N

o hypervisor is present on this system. (0xc0351000) extra info: {“SystemType”:”Container”,”Name”:”6314c9d6f09bc751b86d9

9277e0840037c78ca5da31a591a0544bb8de1b29179″,”Owner”:”docker”,”IsDummy”:false,”IgnoreFlushesDuringBoot”:true,”LayerFolde

rPath”:”C:\\ProgramData\\Docker\\windowsfilter\\6314c9d6f09bc751b86d99277e0840037c78ca5da31a591a0544bb8de1b29179″,”Layer

s”:[{“ID”:”330e1892-ab72-5af5-9029-2dba818740f2″,”Path”:”C:\\ProgramData\\Docker\\windowsfilter\\7d3353dfd3626f71d85cdd9

2073caa629be47788bf19ad69cead29324bc3284c”},{“ID”:”58769865-f1ab-511f-9f09-6a45f9d324cb”,”Path”:”C:\\ProgramData\\Docker

\\windowsfilter\\1136d91f8b39eed82e2883e213665024e93ac70fd955e3cdea909d37108f6bf4″}],”HostName”:”6314c9d6f09b”,”MappedDi

rectories”:[],”SandboxPath”:”C:\\ProgramData\\Docker\\windowsfilter”,”HvPartition”:true,”EndpointList”:[“8da1f34c-339b-4

a9f-ba2c-18d42a8780a2″],”HvRuntime”:{“ImagePath”:”C:\\ProgramData\\Docker\\windowsfilter\\7d3353dfd3626f71d85cdd92073caa

629be47788bf19ad69cead29324bc3284c\\UtilityVM”},”Servicing”:false,”AllowUnqualifiedDNSQuery”:true}.

A quick Google search did not give the solution we where looking for. So I thought it would be helpful to share the steps we followed to solve this issue.

The situation

The Docker installer did enable the necessary Hyper-V feature to be able to run Windows containers natively on Windows 10 via Hyper-V (Windows 10 only supports Hyper-V containers). However Docker also needs the new “Container” feature to be able to run containers on Windows. Searching for this feature with the powershell Get-WindowsOptionalFeature -Online commandlet showed us the reason for this error message: the Containers feature was missing on the Windows 10 installations of the development machines.

The solution

It appeared that we missed some Windows updates. So to solve this issue you have to execute the following steps:

  1. Deinstall Docker
  2. Install all missing Windows updates
  3. Install Docker
  4. Once you’ve done that, you’ll get the following pop-up window to enable the Containers feature on Windows.
Container feature is not enabed
Container feature is not enabed

Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Verplichte velden zijn gemarkeerd met *