``` root@node01:~# kubeadm join 172.25.0.7:6443 --token 4pozrf.32urbunhd2u3y709 . . .

Kubernetes-Slack Discussions
#1

Priyanka Maheshwari:

root@node01:~# kubeadm join 172.25.0.7:6443 --token 4pozrf.32urbunhd2u3y709 --discovery-token-ca-cert-hash sha256:c01810896dc3145f1a773c24834e3639a080977e4e71f6ca3cafa0c568ace8ea
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at <https://kubernetes.io/docs/setup/cri/>
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR DirAvailable--etc-kubernetes-manifests]: /etc/kubernetes/manifests is not empty
        [ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
        [ERROR Port-10250]: Port 10250 is in use
        [ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
#2

Adeola Adefolaju:
You need to change the cgroup driver from cgroupfs to systemd. A cluster setup with kubeadm tool recommends using systemd.

image.png
image.png806×315 133 KB

#3

Adeola Adefolaju:
https://kodekloud.slack.com/files/U01PP2F8NCC/F031CQ0BJRG/k8s-cluster-setup-on-v1.22.odt

#4

Adeola Adefolaju:
@Priyanka Maheshwari check the document in the link above for the steps on how to change the cgroup driver from cgroupfs to systemd on both nodes. You will also have to do a daemon-reload and restart kubelet on both nodes after changing to systemd

#5

Adeola Adefolaju:
snapshots in the above doc

image.png
image.png922×361 84.9 KB

image.png
image.png1004×421 85.3 KB

#6

Priyanka Maheshwari:
oh ok so do we need to edit this?

#7

Adeola Adefolaju:
yes you will need to edit it once you open the file.