Installing Minikube using Homebrew
Requirements
- Homebrew
- Minikube
- Docker
- Visual Studio (or your favorite IDE)
- iTerm or Terminal
Install Minikube
What’s Minikube? Minikube is an open-source tool that helps you set up a local, single-node Kubernetes cluster and gives you the ability to test applications locally. You can create services, check deployments, and use it to learn essential Kubernetes concepts.
Now that we have Homebrew installed, weβll use Homebrew to install Minikube.
Run the following command:
brew install minikube
Start Minikube
minikube start
Common Error
If you happen to get the following error:
Exiting due to DRV_UNSUPPORTED_OS: The driver 'virtualbox' is not supported on darwin/arm64
Make sure Docker is running. You can check by running the following command:
docker version
You can then run:
minikube start --driver=docker
What is this doing exactly?
This is telling Minikube to use Docker as a driver in order to run Kubernetes.
Successful Output
If youβve done everything correctly up until now, you should see something like the following:
john@johnsmacbookpro ~ % minikube start
π minikube v1.38.1 on Darwin 26.3.1 (arm64)
β¨ Using the docker driver based on existing profile
π Starting "minikube" primary control-plane node in "minikube" cluster
π Pulling base image v0.0.50 ...
π Restarting existing docker container for "minikube" ...
π³ Preparing Kubernetes v1.35.1 on Docker 29.2.1 ...
π Verifying Kubernetes components...
βͺ Using image gcr.io/k8s-minikube/storage-provisioner:v5
π Enabled addons: storage-provisioner, default-storageclass
π Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Stopping Minikube
If at any point you need to stop Minikube, you can run the following command:
minikube stop
Example output:
john@johnsmacbookpro ~ % minikube stop
β Stopping node "minikube" ...
π Powering off "minikube" via SSH ...
π 1 node stopped.
What is this output telling us?
- This output is telling us the version of Minikube that we have installed
- Itβs starting up a control-plane node in our Minikube cluster
- This is essentially all Minikube is doing for us, providing us with a cluster that contains a node we can use for running and testing applications
- Providing the base image that we are working with
Context to keep in mind
- Minikube is our cluster
- Our default namespace is
default