http://bugzilla.opensuse.org/show_bug.cgi?id=1093132
http://bugzilla.opensuse.org/show_bug.cgi?id=1093132#c2
--- Comment #2 from Panagiotis Georgiadis
[WARNING FileExisting-crictl]: crictl not found in system path
As you can see, during the pre-flight checks, kubeadm is looking for 'crictl' binary. If it's present on the system (this is the case when cri-tools package is installed) is trying to use it, and it fails with that message:
ERROR CRI: unable to check if the container runtime at "/var/run/dockershim.sock" is running: exit status 1
By removing the package and trying again. I end up with a different error:
[markmaster] Will mark node ultron as master by adding a label and a taint error marking master: timed out waiting for the condition.
As a result, I conclude that the 'ERROR CRI' is triggered when 'cri-tools' package is installed. -- You are receiving this mail because: You are on the CC list for the bug.