-
Notifications
You must be signed in to change notification settings - Fork 710
The main containerd config is soon version 3 #4185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Also the indent of the config was too much Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM
Our config is still version 2: lima/pkg/cidata/cidata.TEMPLATE.d/boot/40-install-containerd.sh Lines 44 to 91 in 852c0bc
Doesn't seem true |
Yeah, but this PR seems to work for any version of the main config because it specifies the |
It should work either way |
But it was still version 2 |
Also the indent of the config was too much
The configuration was not read, because it used the old config for config version 2 (it is now config version 3)
The configuration is automatically updated from the old version, so we can use the same as the upstream docs:
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd
It is a very minor difference in "pause" versions and it only mattered for Windows, and then systemd...
But you still get a warning from
kubeadm
, since it hasn't fully handed over the sandbox detection to the CRI:https://github.com/kubernetes/kubernetes/blob/release-1.34/cmd/kubeadm/app/preflight/checks.go#L830
The setting of the cgroup is from here, it has been hardcoded to systemd in kubeadm not not so in containerd:
https://github.com/containerd/containerd/blob/main/docs/cri/config.md