How to Install Minikube on Windows 10 (Step-by-Step)

To install Minikube on Windows 10, install kubectl first, then run winget install Kubernetes.minikube in PowerShell and start the cluster with minikube start --driver=docker. Your PC needs two CPU cores, 2 GB of free RAM, 20 GB of free disk space and hardware virtualization enabled in the BIOS. Budget about fifteen minutes for the first run.

Minikube runs a single-node Kubernetes cluster on your own machine, which makes it the cheapest way to learn Kubernetes or test manifests before they hit a real cluster. The current release is Minikube v1.38.1, and its default Kubernetes version is v1.36.2. You will spend most of your setup time on one decision: which driver hosts the cluster. Get that right and the rest is three commands.

Step 1: Check that your PC can actually run it

Minikube’s published minimum requirements are modest, but they are minimums, not comfortable working numbers. The table below shows what the docs ask for and what I would actually plan around on a Windows 10 laptop.

Check virtualization without rebooting: open Task Manager, go to the Performance tab, click CPU, and look for “Virtualization: Enabled” in the bottom right. If it says Disabled, you need to turn on Intel VT-x or AMD-V (sometimes labeled SVM Mode) in your firmware setup screen.

Step 2: Pick a driver

A driver is the thing that hosts the Kubernetes node. On Windows you have three realistic options, and they are not interchangeable. Minikube supports Docker, Hyper-V, VirtualBox, QEMU, VMware, Podman and others depending on the platform, but these three cover almost every Windows 10 case.

Step 3: Install kubectl

Minikube ships a bundled kubectl you can reach with minikube kubectl -- get pods, but a standalone binary is far less annoying. Pick one:

# winget (recommended)
winget install -e --id Kubernetes.kubectl

# Chocolatey
choco install kubernetes-cli

# Scoop
scoop install kubectl

# Or download the binary directly
curl.exe -LO "https://dl.k8s.io/release/v1.36.2/bin/windows/amd64/kubectl.exe"

If you download the binary manually, move kubectl.exe into a folder on your PATH, then confirm it works:

kubectl version --client

Kubernetes only supports a client within one minor version of the control plane. A v1.36 kubectl talks to v1.35, v1.36 and v1.37 clusters. Since Minikube’s current default is v1.36.2, a fresh kubectl is exactly right.

Step 4: Install Minikube

The official Minikube quickstart lists three Windows paths. Use a package manager if you have one.

# Windows Package Manager
winget install Kubernetes.minikube

# Chocolatey (run as Administrator)
choco install minikube

If neither is available, grab the executable yourself. Run this in an Administrator PowerShell window:

New-Item -Path 'c:\' -Name 'minikube' -ItemType Directory -Force
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest -OutFile 'c:\minikube\minikube.exe' `
  -Uri 'https://github.com/kubernetes/minikube/releases/latest/download/minikube-windows-amd64.exe' `
  -UseBasicParsing

Then add C:\minikube to your system PATH. Close and reopen your terminal, then check the version:

minikube version

A signed .exe installer on the Minikube releases page does the same thing and handles PATH for you.

Step 5: Start the cluster

Make sure Docker Desktop is running and shows “Engine running” in its status bar, then:

minikube start --driver=docker

# Give it more headroom if your machine can spare it
minikube start --driver=docker --cpus=4 --memory=6g

# Hyper-V instead (Administrator PowerShell required)
minikube start --driver=hyperv

# VirtualBox instead
minikube start --driver=virtualbox

Set your choice as the default so you stop typing the flag:

minikube config set driver docker

Hyper-V needs to be switched on first, which requires a reboot if it was off:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Step 6: Verify the cluster

minikube status
kubectl get nodes
kubectl get pods -A

minikube status should report host, kubelet, apiserver and kubeconfig all as Running or Configured. kubectl get nodes should show a single node named minikube with status Ready. If the node sits in NotReady for more than a minute or two, jump to the troubleshooting section.

Step 7: Enable the dashboard and metrics-server

Addons are Minikube’s built-in extensions. List what is available and what is on:

minikube addons list
minikube addons enable metrics-server
minikube dashboard

minikube dashboard enables the dashboard addon and opens a proxy in your default browser. Use minikube dashboard --url if you want the URL printed instead of a browser tab. Leave that terminal open; closing it kills the proxy.

Step 8: Deploy a test nginx pod

A cluster that starts is not the same as a cluster that works. Push a real workload through it:

kubectl create deployment web --image=nginx
kubectl expose deployment web --type=NodePort --port=80
kubectl get pods -w

Once the pod reports Running, ask Minikube for the URL and open it:

minikube service web --url
minikube service web

NodePort services land in the 30000–32767 range. With the Docker driver on Windows, minikube service runs as a foreground process that tunnels to the cluster, so keep it in its own terminal window. Services of type LoadBalancer need minikube tunnel running separately instead, and it will prompt for elevated permissions because it adds a network route on the host.

With the cluster proven, the natural next move is a package manager for Kubernetes. Our walkthrough on how to install Helm in Minikube and deploy your first chart picks up exactly here.

Step 9: Stop, start and delete

# Shut down but keep the cluster on disk
minikube stop

# Bring it back later
minikube start

# Destroy this cluster
minikube delete

# Destroy every cluster and profile
minikube delete --all

Use stop at the end of the day and delete when something is broken beyond diagnosis. A delete-and-restart cycle takes a couple of minutes and fixes an embarrassing share of Minikube problems.

Troubleshooting Minikube on Windows 10

“This computer doesn’t have VT-X/AMD-v enabled”

Hardware virtualization is off in firmware, or another hypervisor has claimed it. Reboot into BIOS/UEFI setup and enable Intel VT-x or AMD-V (AMD boards often label it SVM Mode). If you are on an AMD machine with the VirtualBox driver and you are certain virtualization is on, --no-vtx-check skips the availability test, but treat that as a last resort rather than a fix.

Hyper-V and WSL 2 versus VirtualBox

Docker Desktop’s WSL 2 backend needs the Windows hypervisor platform, which is the same layer Hyper-V uses. That is fine: Docker Desktop and the Hyper-V driver coexist. VirtualBox is the odd one out. If VirtualBox VMs suddenly refuse to boot or crawl after you install Docker Desktop, you now have two hypervisors competing. Either switch Minikube to the Docker driver, or disable the Hyper-V and Windows Hypervisor Platform features and go all-in on VirtualBox.

“Cannot connect to the Docker daemon”

Docker Desktop is not running, or it is still starting. Open it, wait for the whale icon to stop animating, and confirm with docker info. On Windows 10 Home and Education editions, Docker Desktop only runs Linux containers, which is all Minikube needs.

minikube start hangs on “Pulling base image”

Minikube is downloading a container image of a few hundred megabytes. On a slow link the first pull genuinely takes several minutes, so give it time before you panic. If it stalls completely, run it verbosely to see where it stops, and consider an alternate registry:

minikube start --driver=docker --alsologtostderr --v=2

# If gcr.io is unreachable from your network
minikube start --driver=docker --image-repository=auto

# Then collect diagnostics
minikube logs --problems

Corporate proxies and TLS-inspecting firewalls are the usual culprits. Set HTTP_PROXY, HTTPS_PROXY and NO_PROXY before minikube start so both Minikube and the in-cluster components see them.

Your Windows 10 machine is out of support

Mainstream Windows 10 support ended on 14 October 2025. Free consumer Extended Security Updates now run to 12 October 2027, and enrollment is free if you sync your PC settings, 1,000 Microsoft Rewards points, or a one-time $30 purchase covering up to ten devices. Enroll. An unpatched machine running container workloads pulled from the public internet is a bad combination, and Docker only commits to supporting Windows releases inside Microsoft’s servicing timeline.

Everything is slow

Minikube defaults to 2 CPUs. On a laptop with 8 GB of RAM shared with a browser, that is tight. Delete the cluster and recreate it with more resources. If you only need a local web stack rather than Kubernetes, our guide to installing WordPress on a local host is a lighter fit.

Frequently asked questions

Can I install Minikube on Windows 10 Home?

Yes. Windows 10 Home cannot run the Hyper-V driver, but the Docker and VirtualBox drivers both work. Docker Desktop on Home and Education editions is limited to Linux containers, which is exactly what Minikube uses. The Minikube docs describe VirtualBox as the most stable driver for Windows Home users.

Do I need Docker Desktop to install Minikube on Windows 10?

No, but it is the easiest route. Minikube’s Docker driver needs a working Docker Engine, and on Windows that means Docker Desktop. If you would rather not install it, use the VirtualBox driver on Home or the Hyper-V driver on Pro, Enterprise and Education.

How much RAM does Minikube need?

Minikube’s documented minimum is 2 GB of free memory and its default allocation is 2 CPUs. In practice, plan on 8 GB of total system RAM, which is also Docker Desktop’s own stated requirement for the WSL 2 and Hyper-V backends. Anything less and the node will be Ready but painfully slow.

What Kubernetes version does Minikube install?

Minikube v1.38.1 defaults to the stable channel, which is Kubernetes v1.36.2. Override it with minikube start --kubernetes-version=v1.35.6 when you need to match a production cluster. Keep kubectl within one minor version of whichever you pick.

Is Minikube good enough for production?

No. Minikube is a single-node development cluster with no high availability and no real network isolation. It is excellent for learning, CI and local testing of manifests and Helm charts. For anything user-facing, use a managed control plane or a properly built multi-node cluster.

Does Minikube work the same on Linux?

Mostly, and it is faster there because the Docker driver talks to a native Docker Engine. Two addons, ingress and ingress-dns, only work on Linux hosts. If you have a Linux box handy, our guide to installing Minikube on Ubuntu covers the differences.

Wrapping up

For nearly everyone on Windows 10, the answer is Docker Desktop plus minikube start --driver=docker. It starts in well under a minute, survives reboots, and does not fight with WSL 2. Reach for Hyper-V only if you are already invested in it, and for VirtualBox only on Windows 10 Home where Docker Desktop is not an option.

One last piece of honest advice: enroll that machine in Windows 10 ESU before you build anything on it. You have until October 2027, the consumer path can cost nothing, and Docker’s support policy follows Microsoft’s servicing timeline rather than your preferences. Once the cluster is up and verified, install Helm and start deploying charts instead of hand-writing YAML.