Building the minikube ISO
The minikube ISO is booted by each hypervisor to provide a stable minimal Linux environment to start Kubernetes from. It is based on coreboot, uses systemd, and includes all necessary container runtimes and hypervisor guest drivers.
- A recent GNU Make distribution (>=4.0)
- A recent Go distribution (>=1.16)
- If you are on Windows or Mac, you’ll need Docker to be installed.
- 4GB of RAM
Downloading the source
git clone https://github.com/kubernetes/minikube.git cd minikube
Building in Docker
To build for x86
$ make buildroot-image $ make out/minikube-amd64.iso
To build for ARM
$ make buildroot-image $ make out/minikube-arm64.iso
The build will occur inside a docker container.
The bootable ISO image will be available in
Building on Baremetal
If you want to do this on baremetal, replace
make out/minikube-<arch>.iso with
IN_DOCKER=1 make out/minikube-<arch>.iso.
- Prerequisite build tools to install:
sudo apt-get install build-essential gnupg2 p7zip-full git wget cpio python \ unzip bc gcc-multilib automake libtool locales
Additionally, if you are on Fedora, you will need to install
sudo dnf install -y glibc-static
Using a local ISO image
$ ./out/minikube start --iso-url=file://$(pwd)/out/minikube-<arch>.iso
Modifying buildroot components
To change which Linux userland components are included by the guest VM, use this to modify the buildroot configuration:
cd out/buildroot make menuconfig make
To save these configuration changes, execute:
The changes will be reflected in the
Adding kernel modules
To make kernel configuration changes and save them, execute:
$ make linux-menuconfig
This will open the kernel configuration menu, and then save your changes to our iso directory after they’ve been selected.
Adding third-party packages
To add your own package to the minikube ISO, create a package directory under
iso/minikube-iso/package. This directory will require at least 3 files:
<package name>.mk - A Makefile describing how to download the source code and build the program
<package name>.hash - Checksums to verify the downloaded source code
Config.in - buildroot configuration
For a relatively simple example to start with, you may want to reference the
Continuous Integration Builds
We publish CI builds of minikube, built at every Pull Request. Builds are available at (substitute in the relevant PR number):
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.