Unfortunately, the VM does need to be large enough to support nested virtualization. Well, why not? It will save me over $100 a month and the images I am running will be small. Being on a budget I picked a standard VM. First of all, I skipped the documentation and went strait to provisioning a VM.
Well, things are obvious in hindsight and it was in the documentation but here is how I missed it. It is hard to put into words regarding the feeling you get when you provision a new VM, enable Hyper-V, download Docker, install Docker and then receive aĬ:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: container 6cc2e3a20dcc82e47fd223de7b1fc8b8d6fd19a538079b23fde72d9dd441ef74 encountered an error during CreateContainer: failure in a Windows system call: No hypervisor is present on this system. The purpose of this post is to highlight some common issues faced when getting started with Docker in Azure. Getting started in a new technology can be frustrating when things go wrong, and Docker is no exception.
