Fail: Minikube on Windows 10 using HyperV

· by Raghu Rajagopalan · Read in about 1 min · (151 words) ·

So I’m stuck on windows 8.1 on my work machine - not that I mind too much.. It’s just too much work to set up the machine from scratch. However, windows 10’s WSL and docker for windows support using HyperV was something I wanted to give a spin.

With Azure now supporting nested virtualization, I set up a dev machine on azure on the Dv3 SKU’s and set up minikube on it. I created a new virtual switch in HyperV for the external network, rebooted and then fired off a minikube start

minikube start --vm-driver hyperv --hyperv-virtual-switch externalvs

Apparently that incantation should be enough to get minikube up but it wasn’t to be and I ran into this bug: Job for crio.service failed. Looking at minikube’s github, there’s 36 open issues on hyperv as of now. Looks like it’s going to be sometime before I can move off virtualbox for minikube.