-
Notifications
You must be signed in to change notification settings - Fork 5k
ISO: bump to containerd 2 #21409
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
base: master
Are you sure you want to change the base?
ISO: bump to containerd 2 #21409
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nirs The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-build-iso |
2 similar comments
/ok-to-build-iso |
/ok-to-build-iso |
deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk
Outdated
Show resolved
Hide resolved
/ok-to-build-iso |
See the logs at: for example for this PR |
/ok-to-build-iso |
Hi @nirs, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further. |
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.
The config.toml does not help with #21408 and may break code configuring containerd using sed(!?). We need to replace the configuration code with proper toml parsing but for now we can keep the existing config.
deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk
Show resolved
Hide resolved
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 47.5s 48.8s 47.3s 51.1s 49.4s Times for minikube ingress: 18.9s 15.9s 15.9s 15.9s 16.9s docker driver with docker runtime
Times for minikube start: 25.4s 23.9s 27.4s 24.1s 23.7s Times for minikube ingress: 13.7s 13.6s 13.6s 13.7s 13.6s docker driver with containerd runtime
Times for minikube start: 22.2s 22.7s 24.8s 27.5s 26.0s Times for minikube (PR 21409) ingress: 39.6s 23.7s 23.6s 30.6s 23.7s |
- Fix Makefile title in aarch64 - Unify whitespaec in *.mk files - Remove extra space between the hash and the tarball name - Remove empty line at the end hash file
Based on crictl-bin Config.in.
Containerd supports a simple and poorly documented drop-in configuration files using the imports option. If this option is set: imports = ["/etc/containerd/conf.d/*.toml"] Then toml files under /etc/containerd/conf.d/ are loaded and merged with the config read from /etc/containerd/config.toml. Unlike systemd drop-in files, you cannot override single option by adding drop-in configuration file. To override a single option you must set all options in the section, and the entire section is replaced by the drop-in file. We never used this feature since our config contains: # imports And we don't configure this dynamically. Our config on the host is: $ grep conf.d /etc/containerd/config.toml conf_dir = "/etc/cni/net.d" However we were creating: /etc/containerd/containerd.conf.d/ This path does not make sense (repeating containerd twice) and files in this directory are ignored. Finally this directory was created in CONFIGURE_CMDS instead of INSTALL_CMDS. Now that we install a binary we should not have any configure commands. Since we never had a working conf.d directory we can safely remove it.
This is the reason for the strange failure when build the x86_64 iso, about no hash for arm64 tarball. I seems that package for different architectures must have a different names to avoid confusing buildroot. The name was broken by mistake when updating to containerd 2.1.4. With this change iso build works for both aarch64 and x86_64.
/ok-to-build-iso |
Change sin latest version:
Need testing again since last time I test mostly with the new config. |
Hi @nirs, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further. |
This is #21368 with the following changes:
Status:
Fixes #20497