Skip to content

Commit f31a8e4

Browse files
committed
Formatting and minor content fixes
Signed-off-by: Ihor Dvoretskyi <[email protected]>
1 parent 754b41f commit f31a8e4

File tree

1 file changed

+66
-4
lines changed

1 file changed

+66
-4
lines changed

docs/drivers.md

Lines changed: 66 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,23 @@ the host PATH:
1818

1919
To install the KVM2 driver, first install and configure the prereqs:
2020

21-
* Debian or Ubuntu 18.x: `sudo apt install libvirt-clients libvirt-daemon-system qemu-kvm`
22-
* Ubuntu 16.x or older: `sudo apt install libvirt-bin libvirt-daemon-system qemu-kvm`
23-
* Fedora/CentOS/RHEL: `sudo yum install libvirt-daemon-kvm qemu-kvm`
21+
* Debian or Ubuntu 18.x:
22+
23+
```shell
24+
sudo apt install libvirt-clients libvirt-daemon-system qemu-kvm
25+
```
26+
27+
* Ubuntu 16.x or older:
28+
29+
```shell
30+
sudo apt install libvirt-bin libvirt-daemon-system qemu-kvm
31+
```
32+
33+
* Fedora/CentOS/RHEL:
34+
35+
```shell
36+
sudo yum install libvirt-daemon-kvm qemu-kvm
37+
```
2438

2539
Then you will need to add yourself to libvirt group (older distributions may use libvirtd instead)
2640

@@ -39,7 +53,7 @@ curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-
3953

4054
NOTE: Ubuntu users on a release older than 18.04, or anyone experiencing [#3206: Error creating new host: dial tcp: missing address.](https://github.com/kubernetes/minikube/issues/3206) you will need to build your own driver until [#3689](https://github.com/kubernetes/minikube/issues/3689) is resolved. Building this binary will require [Go v1.11](https://golang.org/dl/) or newer to be installed.
4155

42-
```
56+
```shell
4357
sudo apt install libvirt-dev
4458
test -d $HOME/go/src/k8s.io/minikube || \
4559
git clone https://github.com/kubernetes/minikube.git $HOME/go/src/k8s.io/minikube
@@ -55,6 +69,18 @@ To use the kvm2 driver:
5569
minikube start --vm-driver kvm2
5670
```
5771

72+
or, to use kvm2 as a default driver:
73+
74+
```shell
75+
minikube config set vm-driver kvm2
76+
```
77+
78+
and run minikube as usual:
79+
80+
```shell
81+
minikube start
82+
```
83+
5884
#### Hyperkit driver
5985

6086
The Hyperkit driver will eventually replace the existing xhyve driver.
@@ -92,6 +118,18 @@ To use the driver:
92118
minikube start --vm-driver hyperkit
93119
```
94120

121+
or, to use hyperkit as a default driver:
122+
123+
```shell
124+
minikube config set vm-driver hyperkit
125+
```
126+
127+
and run minikube as usual:
128+
129+
```shell
130+
minikube start
131+
```
132+
95133
#### HyperV driver
96134

97135
Hyper-v users may need to create a new external network switch as described [here](https://docs.docker.com/machine/drivers/hyper-v/). 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.
@@ -103,6 +141,17 @@ To use the driver:
103141
```shell
104142
minikube start --vm-driver hyperv --hyperv-virtual-switch=switch-name
105143
```
144+
or, to use hyperv as a default driver:
145+
146+
```shell
147+
minikube config set vm-driver hyperv && minikube config set hyperv-virtual-switch switch-name
148+
```
149+
150+
and run minikube as usual:
151+
152+
```shell
153+
minikube start
154+
```
106155

107156
#### VMware unified driver
108157

@@ -131,3 +180,16 @@ To use the driver:
131180
```shell
132181
minikube start --vm-driver vmware
133182
```
183+
184+
or, to use vmware unified driver as a default driver:
185+
186+
```shell
187+
minikube config set vm-driver vmware
188+
```
189+
190+
and run minikube as usual:
191+
192+
```shell
193+
minikube start
194+
```
195+

0 commit comments

Comments
 (0)