Skip to content

Commit

Permalink
Document none driver compatibility with non docker runtime. (kubernet…
Browse files Browse the repository at this point in the history
  • Loading branch information
RA489 authored and wawa0210 committed Mar 2, 2020
1 parent ec162ca commit b1eead0
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion content/en/docs/setup/learning-environment/minikube.md
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,11 @@ plugins.
* hyperv ([driver installation](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#hyperv-driver))
Note that the IP below is dynamic and can change. It can be retrieved with `minikube ip`.
* vmware ([driver installation](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#vmware-unified-driver)) (VMware unified driver)
* none (Runs the Kubernetes components on the host and not in a VM. It is not recommended to run the none driver on personal workstations. Using this driver requires Docker ([docker install](https://docs.docker.com/install/linux/docker-ce/ubuntu/)) and a Linux environment)
* none (Runs the Kubernetes components on the host and not in a virtual machine. You need to be running Linux and to have {{< glossary_tooltip term_id="docker" >}} installed.)

{{< caution >}}
If you use the `none` driver, some Kubernetes components run as privileged containers that have side effects outside of the Minikube environment. Those side effects mean that the `none` driver is not recommended for personal workstations.
{{< /caution >}}

#### Starting a cluster on alternative container runtimes
You can start Minikube on the following container runtimes.
Expand Down

0 comments on commit b1eead0

Please sign in to comment.