Replies: 3 comments 3 replies
-
Have you looked at the containerd.log file to see why it's not starting? |
Beta Was this translation helpful? Give feedback.
0 replies
-
no, but it is probably the same as reboot and should help. I just wanted to avoid kill/restart node. Not able to reproduce, but can test next time. Btw, can I remove the stale containers in advance? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I encountered issue in the following situation. I did upgrade rke2 from 1.27.10 to 1.27.12, but no reboot, just rke2-[server/agent] restart. Then, still no reboot, I did upgrade from 1.27.12 to 1.28.8. It was mostly ok, however, in about two cases (of 25 nodes) I run into the issue that containerd did not start. The process was running, but connection on the socket was refused.
Multiple rke2 restarts do not help. Even reverting back to 1.27.12 version and restart does not help. Node reboot solves it.
Is it something known/expected?
Beta Was this translation helpful? Give feedback.
All reactions