-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubeadm join fails #83
Comments
closed. Docker was confusing kubeadm join |
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
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 |
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 |
Changes in 1.14 (https://github.com/kubernetes/kubernetes/pull/69366/files) are meant to change the usage of --cri-socket argument. After seting up the k8s master with the PR #80, in client I'm getting the following errors:
The text was updated successfully, but these errors were encountered: