Most users of this driver should consider the newer Docker driver, as it is significantly easier to configure and does not require root access. The ‘none’ driver is recommended for advanced users only.
This document is written for system integrators who wish to run minikube within a customized VM environment. The
none driver allows advanced minikube users to skip VM creation, allowing minikube to be run on a user-supplied VM.
A Linux VM with the following:
- systemd (OpenRC based systems are also supported in v1.10+)
This VM must also meet thekubeadm requirements
The none driver requires minikube to be run as root, until #3760 can be addressed.
sudo minikube start --driver=none
none the default driver:
sudo minikube config set driver none
- minikube starts services that may be available on the Internet. Please ensure that you have a firewall to protect your host from unexpected access. For instance:
- apiserver listens on TCP *:8443
- kubelet listens on TCP *:10250 and *:10255
- kube-scheduler listens on TCP *:10259
- kube-controller listens on TCP *:10257
- Containers may have full access to your filesystem.
- Containers may be able to execute arbitrary code on your host, by using container escape vulnerabilities such as CVE-2019-5736. Please keep your release of minikube up to date.
minikube with the none driver may be tricky to configure correctly at first, because there are many more chances for interference with other locally run services, such as dnsmasq.
When run in
nonemode, minikube has no built-in resource limit mechanism, which means you could deploy pods which would consume all of the hosts resources.
minikube and the Kubernetes services it starts may interfere with other running software on the system. For instance, minikube will start and stop container runtimes via systemd, such as docker, containerd, cri-o.
none driver, minikube will overwrite the following system paths:
- /etc/kubernetes - configuration files
These paths will be erased when running
As Kubernetes has full access to both your filesystem as well as your docker images, it is possible that other unexpected data loss issues may arise.
-p(profiles) are unsupported: It is not possible to run more than one
minikubecommands are not supported, such as:
minikube with the
nonedriver has a confusing permissions model, as some commands need to be run as root (“start”), and others by a regular user (“dashboard”)
CoreDNS detects resolver loop, goes into CrashLoopBackOff - #3511
Some versions of Linux have a version of docker that is newer than what Kubernetes expects. To overwrite this, run minikube with the following parameters:
sudo -E minikube start --driver=none --kubernetes-version v1.11.8 --extra-config kubeadm.ignore-preflight-errors=SystemVerification
minikube start --alsologtostderr -v=4to debug crashes