# Minikube on Windows

Author: [Mete Atamel](https://atamel.dev/) | Published: 2018-02-14 | Updated: 2020-04-19 | Canonical: https://atamel.dev/posts/2018/02-14_minikube-on-windows/


When I’m playing with Kubernetes, I usually get a cluster from [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) (GKE) because it’s literally [a single gcloud command](https://cloud.google.com/sdk/gcloud/reference/container/clusters/create) to get a Kubernetes cluster up and running on GKE. It is sometimes useful though to have a Kubernetes cluster running locally for testing and debugging. [Minikube](https://github.com/kubernetes/minikube) is perfect for this.

![](/img/2018/0__CUxIJLODCN__MLSa8.)

Minikube runs a single-node Kubernetes cluster inside a VM on your laptop. There are instructions on how to install it on Linux, Mac and Windows. Unfortunately, [instructions for Windows](https://github.com/kubernetes/minikube#windows) is a little lacking, so I want to document how I got Minikube up and running on my Windows 10 machine.

First, you need to download the minikube-windows-amd64.exe file, rename it to minikube.exe and add it to your path, as explained in the [instructions for Windows](https://github.com/kubernetes/minikube#windows). Instructions make it sound like you’re done at this point but if you try to start minikube in PowerShell admin mode, you will get an error like this:

![](/img/2018/0__UGSR2bTsheG8w6ud.)

This is because Minikube needs a VM and by default, it tries to use VirtualBox. On Windows, you can either use Hyper-V (available natively on Windows 10) or you can install VirtualBox. Many people ([here](https://rominirani.com/tutorial-getting-started-with-kubernetes-on-your-windows-laptop-with-minikube-3269b54a226) and [here](https://www.ibm.com/support/knowledgecenter/en/SS5PWC/minikube.html)) recommend VirtualBox to avoid issues but I didn’t want to install something extra like VirtualBox, so I decided to go with Hyper-V. You can tell Minikube via _–vm-driver=hyperv_ flag to use Hyper-V but this also failed with the same error earlier.

![](/img/2018/0__FfP3wKIzbkG6rtdR.)

What’s happening? Turns out, there’s a bug on Minikube and Windows 10. This [GitHub issue](https://github.com/kubernetes/minikube/issues/754) explains the details if you’re interested and this [very useful comment](https://github.com/kubernetes/minikube/issues/754#issuecomment-258129252) explains what you need to do. You basically need to create a Virtual Switch in Hyper-V and allow your actual internet connection share its connection with this Virtual Switch.

After you create the Virtual Switch, you can start minikube with Hyper-V with additional _–hyperv-virtual-switch_ flag.

![](/img/2018/0__5aYMFWTWoY0T4sIu.)

This takes a while for the first time as it needs to download ISO images etc. but once done, you can test the local cluster by creating a deployment and deploying an echoserver pod:

![](/img/2018/0__BXXT35P__9KATsFVL.)

That’s it! Hope this was useful for you to get Minikube up and running on Windows.

_Originally published at_ [_meteatamel.wordpress.com_](https://meteatamel.wordpress.com/2018/02/14/minikube-on-windows/) _on February 14, 2018._

