diff options
| author | Igor Beliakov <46579601+weisdd@users.noreply.github.com> | 2021-01-24 10:14:25 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-24 10:14:25 +0300 |
| commit | a7f11f8161af71b4951ca99cf410ce120cccff97 (patch) | |
| tree | 16e6486b486df731fab8191e9b375ecb2f5c93f3 | |
| parent | cac70c65e6b5b8a7a3eda55f83f9ceffdfdaba89 (diff) | |
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.
| -rw-r--r-- | g3doc/user_guide/FAQ.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/g3doc/user_guide/FAQ.md b/g3doc/user_guide/FAQ.md index 8e5721ad1..26c836ddf 100644 --- a/g3doc/user_guide/FAQ.md +++ b/g3doc/user_guide/FAQ.md @@ -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 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: ```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 |