``` [email protected]:~# kubeadm join --token 4pozrf.32urbunhd2u3y709 . . .

Priyanka Maheshwari:

[email protected]:~# kubeadm join --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

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

Adeola Adefolaju:

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

Adeola Adefolaju:
snapshots in the above doc

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

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