7.6 KiB
VM Driver plugin installation
Minikube uses Docker Machine to manage the Kubernetes VM so it benefits from the driver plugin architecture that Docker Machine uses to provide a consistent way to manage various VM providers. Minikube embeds VirtualBox and VMware Fusion drivers so there are no additional steps to use them. However, other drivers require an extra binary to be present in the host PATH.
The following drivers currently require driver plugin binaries to be present in the host PATH:
KVM2 driver
KVM2 install
To install the KVM2 driver, first install and configure the prerequisites, namely libvirt 1.3.1 or higher, and qemu-kvm:
- Debian or Ubuntu 18.x:
sudo apt install libvirt-clients libvirt-daemon-system qemu-kvm - Ubuntu 16.x or older:
sudo apt install libvirt-bin libvirt-daemon-system qemu-kvm - Fedora/CentOS/RHEL:
sudo yum install libvirt-daemon-kvm qemu-kvm - openSUSE/SLES:
sudo zypper install libvirt qemu-kvm
Check your installed virsh version:
virsh --version
If your version of virsh is newer than 1.3.1 (January 2016), you may download our pre-built driver:
curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-kvm2 \
&& sudo install docker-machine-driver-kvm2 /usr/local/bin/
If your version of virsh is older than 1.3.1 (Januarry 2016), you may build your own driver binary if you have go 1.12+ installed.
$ sudo apt install libvirt-dev
$ git clone https://github.com/kubernetes/minikube.git
$ cd minikube
$ make out/docker-machine-driver-kvm2
$ sudo install out/docker-machine-driver-kvm2 /usr/local/bin
$
To finish the kvm installation, start and verify the libvirtd service
sudo systemctl enable libvirtd.service
sudo systemctl start libvirtd.service
sudo systemctl status libvirtd.service
Add your user to libvirt group (older distributions may use libvirtd instead)
sudo usermod -a -G libvirt $(whoami)
Join the libvirt group with your current shell session:
newgrp libvirt
To use the kvm2 driver:
minikube start --vm-driver kvm2
or, to use kvm2 as a default driver for minikube start:
minikube config set vm-driver kvm2
KVM2 upgrade
curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-kvm2 \
&& sudo install docker-machine-driver-kvm2 /usr/local/bin/
KVM2 troubleshoot
If minikube can't start, check if the kvm default network exists.
virsh net-list
Name State Autostart Persistent
----------------------------------------------------------
default active yes yes
In case the default network doesn't exist you can define it.
curl https://raw.githubusercontent.com/libvirt/libvirt/master/src/network/default.xml > kvm-default.xml
virsh net-define kvm-default.xml
virsh net-start default
Make sure you are running the lastest version of your driver.
docker-machine-driver-kvm2 version
Hyperkit driver
Install the hyperkit VM manager using brew:
brew install hyperkit
Then install the most recent version of minikube's fork of the hyperkit driver:
curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit \
&& sudo install -o root -g wheel -m 4755 docker-machine-driver-hyperkit /usr/local/bin/
If you are using dnsmasq in your setup and cluster creation fails (stuck at kube-dns initialization) you might need to add listen-address=192.168.64.1 to dnsmasq.conf.
Note: If dnsmasq.conf contains listen-address=127.0.0.1 kubernetes discovers dns at 127.0.0.1:53 and tries to use it using bridge ip address, but dnsmasq replies only to requests from 127.0.0.1
To use the driver:
minikube start --vm-driver hyperkit
or, to use hyperkit as a default driver for minikube:
minikube config set vm-driver hyperkit
Hyperkit troubleshoot
Make sure you are running the lastest version of your driver.
docker-machine-driver-hyperkit version
Hyper-V driver
Hyper-V users will need to create a new external network switch as described here. This step may prevent a problem in which minikube start hangs indefinitely, unable to ssh into the minikube virtual machine. In this add, add the --hyperv-virtual-switch=switch-name argument to the minikube start command.
Older Hyper-V VM's may have dynamic memory management enabled, which can cause problems of unexpected and random restarts which manifests itself in simply losing the connection to the cluster, after which minikube status would simply state stopped. Solution: run minikube delete to delete the old VM.
To use the driver:
minikube start --vm-driver hyperv --hyperv-virtual-switch=switch-name
or, to use hyperv as a default driver:
minikube config set vm-driver hyperv && minikube config set hyperv-virtual-switch switch-name
and run minikube as usual:
minikube start
VMware unified driver
The VMware unified driver will eventually replace the existing vmwarefusion driver. The new unified driver supports both VMware Fusion (on macOS) and VMware Workstation (on Linux and Windows)
To install the vmware unified driver, head over at https://github.com/machine-drivers/docker-machine-driver-vmware/releases and download the release for your operating system.
The driver must be:
- Stored in
$PATH - Named
docker-machine-driver-vmware - Executable (
chmod +xon UNIX based platforms)
If you're running on macOS with Fusion, this is an easy way install the driver:
export LATEST_VERSION=$(curl -L -s -H 'Accept: application/json' https://github.com/machine-drivers/docker-machine-driver-vmware/releases/latest | sed -e 's/.*"tag_name":"\([^"]*\)".*/\1/') \
&& curl -L -o docker-machine-driver-vmware https://github.com/machine-drivers/docker-machine-driver-vmware/releases/download/$LATEST_VERSION/docker-machine-driver-vmware_darwin_amd64 \
&& chmod +x docker-machine-driver-vmware \
&& mv docker-machine-driver-vmware /usr/local/bin/
To use the driver:
minikube start --vm-driver vmware
or, to use vmware unified driver as a default driver:
minikube config set vm-driver vmware
and run minikube as usual:
minikube start
Parallels driver
This driver is useful for users who own Parallels Desktop for Mac that do not have VT-x hardware support required by the hyperkit driver.
Pre-requisites: Parallels Desktop for Mac
Install the Parallels docker-machine driver using brew:
brew install docker-machine-parallels
To use the driver:
minikube start --vm-driver parallels
or, to use parallels as a default driver for minikube:
minikube config set vm-driver parallels
Troubleshooting
minikube is currently unable to display the error message received back from the VM driver. Users can however reveal the error by passing --alsologtostderr -v=8 to minikube start. For instance:
minikube start --vm-driver=kvm2 --alsologtostderr -v=8
Output:
Found binary path at /usr/local/bin/docker-machine-driver-kvm2
Launching plugin server for driver kvm2
Error starting plugin binary: fork/exec /usr/local/bin/docker-machine-driver-kvm2: exec format error