FAQ.md: fix kubeadm init instructions
The current version of FAQ.md contains an incorrect example of how to instruct kubelet to prefer containerd over docker. More specifically, it refers to a non-existent `--cni-socket` flag whereas it should have been `--cri-socket`. The suggested PR fixes that.
This commit is contained in:
parent
cac70c65e6
commit
a7f11f8161
|
@ -107,11 +107,11 @@ kubeadm to create your cluster please check if Docker is also installed on that
|
||||||
system. Kubeadm prefers using Docker if both Docker and containerd are
|
system. Kubeadm prefers using Docker if both Docker and containerd are
|
||||||
installed.
|
installed.
|
||||||
|
|
||||||
Please recreate your cluster and set the `--cni-socket` option on kubeadm
|
Please recreate your cluster and set the `--cri-socket` option on kubeadm
|
||||||
commands. For example:
|
commands. For example:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
kubeadm init --cni-socket=/var/run/containerd/containerd.sock ...
|
kubeadm init --cri-socket=/var/run/containerd/containerd.sock ...
|
||||||
```
|
```
|
||||||
|
|
||||||
To fix an existing cluster edit the `/var/lib/kubelet/kubeadm-flags.env` file
|
To fix an existing cluster edit the `/var/lib/kubelet/kubeadm-flags.env` file
|
||||||
|
|
Loading…
Reference in New Issue