While adding new node to existing 1.9.0 cluster. kubeadm giving this error message.
My cluster is running on Centos 7 server. docker deamon is running, but there is no file /var/run/dockershim.sock found.
How to resolve this error message?
kubeadm join --token
[preflight] Some fatal errors occurred:
[ERROR CRI]: unable to check if the container runtime at "/var/run/dockershim.sock" is running: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`thanks SR
There is a discussion: I have the following problem when I want to use the client for CRI #153
that follows up with the cubeadm issue: How to get kubeadm init to not fail? #733
The issue was solved with Pull Request kubeadm init: skip checking cri socket in preflight checks #58802
Version v1.9.3 is the nearest release after the PR merge.
As a suggested workaround, you can disable the CRI check:
kubeadm init --ignore-preflight-errors=cri