search

alta3 / kubernetes-the-alta3-way

The greatest k8s installer on the planet!
223 stars 34 forks source link

crictl throwing errors related to dockerd/shim #34

Open BicycleWalrus opened 2 years ago

BicycleWalrus commented 2 years ago

On a fresh playbook install, these errors occur for crictl.

WARN[0000] runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead. 
ERRO[0000] unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory" 
WARN[0000] image connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead. 
ERRO[0000] unable to determine image API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /var/run/dockershim.sock: connect: no such file or directory"

Steps to reproduce:

  1. Run playbook
  2. ssh node-1
  3. sudo crictl ps

These errors seem to be related to the recent deprecation of Dockershim in v1.23 -- Probably needs a new config of some type.

bryfry commented 1 year ago

Upstream cri-tools has an open issue - https://github.com/kubernetes-sigs/cri-tools/issues/870

Marked as blocked until upstream updates (expected in k8s version 1.26)