Skip to content

Latest commit

 

History

History
30 lines (18 loc) · 1.53 KB

vmdriver-none.md

File metadata and controls

30 lines (18 loc) · 1.53 KB

vm-driver=None

Overview

This document is written for system integrators who are familiar with minikube, and wish to run it within a customized VM environment.

--vm-driver=None allows advanced minikube users to skip VM creation, allowing minikube to be run on an user-supplied VM.

What operating systems are supported?

--vm-driver=None supports releases of Debian, Fedora, and buildroot that are less than 2 years old.

While the standard minikube guest VM uses buildroot, minikube integration tests are also regularly run against Debian 9 for compatibility. In practice, any systemd-based modern distribution is likely to work, and we will happily accept pull requests which improve compatibility with other systems.

Should vm-driver=None be used outside of a VM?

No.

Running minikube --vm-driver=None outside of a VM could result in data loss, system instability and decreased security.

minikube was designed to run within a dedicated VM, and executes arbitrary processes as root, and when used with --vm-driver=none, may overwrites system binaries, configuration files, and system logs. Usage of --vm-driver=none outside of a VM could also result in services being exposed in a way that may make them accessible to the public internet.

Known Issues

  • You cannot run more than one minikube instance #2781
  • minikube mount is not supported
  • minikube ssh is not supported
  • minikube stop does not work #3217
  • None driver deletes other local docker images #2705
  • None driver fails on distro's which do not use systemd #2704