From a7f11f8161af71b4951ca99cf410ce120cccff97 Mon Sep 17 00:00:00 2001
From: Igor Beliakov <46579601+weisdd@users.noreply.github.com>
Date: Sun, 24 Jan 2021 10:14:25 +0300
Subject: 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.
---
 g3doc/user_guide/FAQ.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'g3doc')

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
-- 
cgit v1.2.3