Skip to content

Commit

Permalink
Documentation: Cite CRI-O as available container runtime. closes #2207
Browse files Browse the repository at this point in the history
Signed-off-by: Lorenzo Fontana <lo@linux.com>
  • Loading branch information
fntlnz committed Nov 18, 2017
1 parent 8ee34ac commit c216a06
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 0 deletions.
22 changes: 22 additions & 0 deletions docs/alternative_runtimes.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,25 @@ $ minikube start \
--network-plugin=cni \
--container-runtime=rkt
```


### Using CRI-O

To use [CRI-O](https://github.com/kubernetes-incubator/cri-o) as the container runtime, run:

```bash
$ minikube start \
--network-plugin=cni \
--container-runtime=cri-o \
--bootstrapper=kubeadm
```

Or you can use the extended version:

```bash
$ minikube start \
--network-plugin=cni \
--extra-config=kubelet.container-runtime=remote \
--extra-config=kubelet.container-runtime-endpoint=/var/run/crio.sock \
--extra-config=image-service-endpoint=/var/run/crio.sock
```
1 change: 1 addition & 0 deletions docs/contributors/minikube_iso.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ It includes:
- systemd as the init system
- rkt
- docker
- CRI-O

## Hacking

Expand Down

0 comments on commit c216a06

Please sign in to comment.