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).

Deep dive into Windows Server Containers and Docker – Part 2 – Underlying implementation of Windows Server Containers

With the introduction of Windows Server 2016 Technical Preview 3 in August 2015, Microsoft enabled the container technology on the Windows platform. While Linux had its container technology since August 2008 such functionality was not supported on Microsoft operating systems before. Thanks to the success of Docker on Linux, Microsoft decided almost 3 years ago to start working on a container implementation for Windows. Since September 2016 we are able to work with a public released version of this new container technology in Windows Server 2016 and Windows 10. But what is the difference between containers and VMs? And how are Windows containers implemented internally within the Windows architecture? In this blogpost we’ll dive into the underlying implementation of containers on Windows. Containers vs VMs Many container introductions start with the phrase that “Containers are lightweight VMs”. Although this may help people to get a conceptual understanding of what containers are,  it is important to notice that this statement is a 100% wrong and can be very