Update minikube documentation (#19756)

* Update vm-driver param and driver links

* Fix mistakes

* Fix spaces

* Revert "Fix spaces"

This reverts commit c08906d6

* Revert "Fix mistakes"

This reverts commit c6c14b69

* Revert "Update vm-driver param and driver links"

This reverts commit 164729db

* Update vm-driver param and driver links
This commit is contained in:
Christian Wansart
2020-03-26 04:42:25 +00:00
committed by GitHub
parent 73ddd2f43e
commit fca1d58ce0
2 changed files with 14 additions and 12 deletions
@@ -26,7 +26,7 @@ grep -E --color 'vmx|svm' /proc/cpuinfo
{{% tab name="macOS" %}}
To check if virtualization is supported on macOS, run the following command on your terminal.
```
sysctl -a | grep -E --color 'machdep.cpu.features|VMX'
sysctl -a | grep -E --color 'machdep.cpu.features|VMX'
```
If you see `VMX` in the output (should be colored), the VT-x feature is enabled in your machine.
{{% /tab %}}
@@ -74,7 +74,7 @@ If you do not already have a hypervisor installed, install one of these now:
• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
Minikube also supports a `--vm-driver=none` option that runs the Kubernetes components on the host and not in a VM.
Minikube also supports a `--driver=none` option that runs the Kubernetes components on the host and not in a VM.
Using this driver requires [Docker](https://www.docker.com/products/docker-desktop) and a Linux environment but not a hypervisor.
If you're using the `none` driver in Debian or a derivative, use the `.deb` packages for
@@ -83,7 +83,7 @@ You can download `.deb` packages from [Docker](https://www.docker.com/products/d
{{< caution >}}
The `none` VM driver can result in security and data loss issues.
Before using `--vm-driver=none`, consult [this documentation](https://minikube.sigs.k8s.io/docs/reference/drivers/none/) for more information.
Before using `--driver=none`, consult [this documentation](https://minikube.sigs.k8s.io/docs/reference/drivers/none/) for more information.
{{< /caution >}}
Minikube also supports a `vm-driver=podman` similar to the Docker driver. Podman run as superuser privilege (root user) is the best way to ensure that your containers have full access to any feature available on your system.
@@ -214,12 +214,12 @@ To confirm successful installation of both a hypervisor and Minikube, you can ru
{{< note >}}
For setting the `--vm-driver` with `minikube start`, enter the name of the hypervisor you installed in lowercase letters where `<driver_name>` is mentioned below. A full list of `--vm-driver` values is available in [specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver).
For setting the `--driver` with `minikube start`, enter the name of the hypervisor you installed in lowercase letters where `<driver_name>` is mentioned below. A full list of `--driver` values is available in [specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver).
{{< /note >}}
```shell
minikube start --vm-driver=<driver_name>
minikube start --driver=<driver_name>
```
Once `minikube start` finishes, run the command below to check the status of the cluster: