We have deployed a new #rke2 cluster (version v1.25.3+rke2r1). The pods are failing 'Crashloopbackoff' because of Container runtime error. We are only using RKE2 conatinerd (not systemd) and it is unable to locate cri socket at unix:///var/run/containerd/containerd.sock since it is present at /run/k3s/containerd/containerd.sock. Error message: {"level":"fatal","version":"v1.4.6","scannerId":"infra:5cdd91cc-f0c5-4204-b371-7a002b65299f:<nodename>","containerRuntimeName":"containerd","error":"could not connect to the cri socket unix😕//var/run/containerd/containerd.sock: context deadline exceeded","time":"2023-04-04T12:35:32Z","message":"failed to instantiate container runtime client"} As a workaround, we have created softlink (it works): /var/run/containerd/containerd.sock -> /run/k3s/containerd/containerd.sock Please let us know how to make /run/k3s/containerd/containerd.sock the default cri socket

Prerequisites packages like rkecommon, selinux are installed?