kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
minikube/docs/alternative_runtimes.md

42 lines
1.2 KiB
Markdown
Raw Normal View History

Run markdownlint on all the md files in docs
2019-03-10 19:02:52 +00:00
# Alternative runtimes
## Using CRI-O
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
Show name as CRI-O, even if class is CRIO Should use the proper name for display, even if we use a name more suitable to naming classes and methods for the implementation... Also use the --runtime=cri-o when testing, and update the github repository now that cri-o has graduated from incubator to a sig. See https://cri-o.io/
2019-02-12 19:50:50 +00:00
To use [CRI-O](https://github.com/kubernetes-sigs/cri-o) as the container runtime, run:
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
highlight shell samples quoted in docs
2018-02-12 11:42:03 +00:00
```shell
Document that cni is now default for runtimes
2019-02-02 17:43:01 +00:00
$ minikube start --container-runtime=cri-o
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
```
Or you can use the extended version:
highlight shell samples quoted in docs
2018-02-12 11:42:03 +00:00
```shell
Document that cni is now default for runtimes
2019-02-02 17:43:01 +00:00
$ minikube start --container-runtime=cri-o \
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
--network-plugin=cni \
Do not include the default CNI config by default Previously, minikube has been shipped with the default CNI config (/etc/cni/net.d/k8s.conf) in its rootfs. This complicated a lot when using a custom CNI plugin, as the default config was picked by kubelet before the custom CNI plugin has installed its own CNI config. So, the end result was that some Pods were attached to a network defined in the default config, and some got managed by the custom plugin. This commit introduces the flag "--enable-default-cni" to "minikube start" to trigger the provisioning of the default CNI config. Signed-off-by: Martynas Pumputis <m@lambda.lt>
2018-12-11 13:30:46 +00:00
--enable-default-cni \
Add config parameter for the cri socket path (#3154) * Add config parameter for the cri socket path Closes #3153 * Remove stray newline, when not using criSocket * Add the --cri-socket parameter to configuration Also fix the syntax for CRI-O, adding unix://
2018-11-15 00:36:02 +00:00
--cri-socket=/var/run/crio/crio.sock \
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
--extra-config=kubelet.container-runtime=remote \
Add config parameter for the cri socket path (#3154) * Add config parameter for the cri socket path Closes #3153 * Remove stray newline, when not using criSocket * Add the --cri-socket parameter to configuration Also fix the syntax for CRI-O, adding unix://
2018-11-15 00:36:02 +00:00
--extra-config=kubelet.container-runtime-endpoint=unix:///var/run/crio/crio.sock \
--extra-config=kubelet.image-service-endpoint=unix:///var/run/crio/crio.sock
Documentation: Cite CRI-O as available container runtime. closes #2207 Signed-off-by: Lorenzo Fontana <lo@linux.com>
2017-11-18 23:40:35 +00:00
```
add example in docs for containerd Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
2018-08-02 11:58:40 +00:00
Run markdownlint on all the md files in docs
2019-03-10 19:02:52 +00:00
## Using containerd
add example in docs for containerd Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
2018-08-02 11:58:40 +00:00
To use [containerd](https://github.com/containerd/containerd) as the container runtime, run:
```shell
Document that cni is now default for runtimes
2019-02-02 17:43:01 +00:00
$ minikube start --container-runtime=containerd
add example in docs for containerd Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
2018-08-02 11:58:40 +00:00
```
Or you can use the extended version:
```shell
Document that cni is now default for runtimes
2019-02-02 17:43:01 +00:00
$ minikube start --container-runtime=containerd \
add example in docs for containerd Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
2018-08-02 11:58:40 +00:00
--network-plugin=cni \
Do not include the default CNI config by default Previously, minikube has been shipped with the default CNI config (/etc/cni/net.d/k8s.conf) in its rootfs. This complicated a lot when using a custom CNI plugin, as the default config was picked by kubelet before the custom CNI plugin has installed its own CNI config. So, the end result was that some Pods were attached to a network defined in the default config, and some got managed by the custom plugin. This commit introduces the flag "--enable-default-cni" to "minikube start" to trigger the provisioning of the default CNI config. Signed-off-by: Martynas Pumputis <m@lambda.lt>
2018-12-11 13:30:46 +00:00
--enable-default-cni \
Add config parameter for the cri socket path (#3154) * Add config parameter for the cri socket path Closes #3153 * Remove stray newline, when not using criSocket * Add the --cri-socket parameter to configuration Also fix the syntax for CRI-O, adding unix://
2018-11-15 00:36:02 +00:00
--cri-socket=/run/containerd/containerd.sock \
add example in docs for containerd Signed-off-by: yanxuean <yan.xuean@zte.com.cn>
2018-08-02 11:58:40 +00:00
--extra-config=kubelet.container-runtime=remote \
--extra-config=kubelet.container-runtime-endpoint=unix:///run/containerd/containerd.sock \
There is only one bootstrapper left anyway Remove the explicit --bootstrapper=kubeadm
2018-09-30 13:25:56 +00:00
--extra-config=kubelet.image-service-endpoint=unix:///run/containerd/containerd.sock
```