Skip to content

Commit b90003a

Browse files
authored
Merge pull request #220 from porridge/minikube-fixes
Fixes for minikube usage instructions.
2 parents a3c8f6c + da91543 commit b90003a

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

docs/dev/setup.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ NAME STATUS AGE VERSION
4949
a sandboxed local cluster. You will first need to [install](https://github.com/kubernetes/minikube/releases)
5050
the minikube binary, then bring up a cluster
5151
```console
52-
$ minikube up
52+
$ minikube start
5353
```
5454

5555
Check for Ready nodes
@@ -71,12 +71,16 @@ $ minikube addons list
7171
If this list already contains the ingress controller, you don't need to
7272
redeploy it. If the addon controller is disabled, you can enable it with
7373
```console
74-
$ minikube enable addons ingress
74+
$ minikube addons enable ingress
7575
```
7676

7777
If the list *does not* contain the ingress controller, you can either update
7878
minikube, or deploy it yourself as shown in the next section.
7979

80+
You may want to consider [using the VM's docker
81+
daemon](https://github.com/kubernetes/minikube/blob/master/README.md#reusing-the-docker-daemon)
82+
when developing.
83+
8084
## Deploy the ingress controller
8185

8286
You can deploy an ingress controller on the cluster setup in the previous step

0 commit comments

Comments
 (0)