This message was deleted.
# rke2
a
This message was deleted.
m
And I can start containrd myself manually through the binary, although then rke2 never tries to deploy to it. Also, the service doesn't mention a containerd process running - just rke2-server.
c
If you watch the logs, you should see that it continues waiting for containerd to start
if containerd is failing to start for some reason, you can probably see why in the containerd log at
/var/lib/rancher/rke2/agent/containerd/containerd.log
You should also see a “running containerd” log message at some point. unless you for some reason set the
container-runtime-endpoint
option in your config, in which case it expects that container runtime to already be started
m
It does indeed continue to waiting for containerd to start, but a few hours later and it will still not have started. It never sends a message of it attempting to start it. The containerd.log is empty of anything new, the last entry is from before the machine was turned off.
c
can you attach the complete rke2-server log, along with the contents of your rke2 config.yaml?
m
It's deployed from Rancher, so I don't see any config.yaml
I sent you a DM with a link to the rke2-server logs.
Of note, these are etcd nodes that can't seem to start containerd