kubeadm join fails about cloud-native-setup HOT 3 CLOSED

Docker comes from containers-basic bundle which is not installed by the cloud-native-setup scripts, so currently reset_stack is only looking for containerd or crio running since those are two options supported by cloud-native-setup. You must have at some point installed containers-basic and then done a systemctl enable docker command. You can just stop docker and disable it
systemctl stop docker
systemctl disable docker
The error message is actually coming from kubadm when Kubelet tries to start it doesn't know which CRI to talk to, and it's just randomly listing docker and crio.

from cloud-native-setup.

closed. Docker was confusing kubeadm join

from cloud-native-setup.

OOI @hnanni - do you remember what the confusion/solution was? I appear to be seeing something similar (multiple CRI sockets) with an upto date system (v31370). It was complaining about having crio and containerd. I nuked containerd, and now it complains about having crio and dockershim

$ ./reset_stack.sh
Found multiple CRI sockets, please use --cri-socket to select one: /var/run/dockershim.sock, /var/run/crio/crio.sock

... [other stuff]

Found multiple CRI sockets, please use --cri-socket to select one: /var/run/dockershim.sock, /var/run/crio/crio.sock
To see the stack trace of this error execute with --v=5 or higher

I'll try dropping docker from my clear installation (if it is present), and see if that fixes it - but, this feels like a niggling annoyance. A side note, it is also quite confusing when the error says please use --cri-socket to select one: /var/run/dockershim.sock, /var/run/crio/crio.sock, it looks like it is saying add that to the reset_stack.sh command line etc., which I know it is not, but that is what I originally tried to do ;-) That is significantly harder to fix - the scripts would probably have to capture stderr/out of the sub-commands and try to annotate the issues more clearly. ho hum.

from cloud-native-setup.