-
Notifications
You must be signed in to change notification settings - Fork 5.1k
iso/kicbase: bump to containerd/nerdctl 2.x #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?
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 |
This comment has been minimized.
This comment has been minimized.
d56d7f2
to
0d79fb4
Compare
/ok-to-build-iso |
$(INSTALL) -Dm755 \ | ||
$(@D)/bin/containerd-shim-runc-v2 \ | ||
$(TARGET_DIR)/usr/bin | ||
$(INSTALL) -Dm755 \ | ||
$(@D)/bin/ctr \ | ||
$(TARGET_DIR)/usr/bin | ||
$(INSTALL) -Dm755 \ |
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.
whats this ?
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.
Part of the release, looks like a stress test. Maybe we can remove it but I'm not sure it worth the effort.
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.
nice job now that did this nice surgery how about adding a tiny Test to the functional test,
that systemctl status the containerd and checks for No Errors or Weird Failures?
minikube ssh --- systemctl... or journalctl ... time to add some Tiny Tests for Container Runtimes
or maybe checking if containerd loaded the Config without any parsing issues ? so in future when someone breaks the config we can see in a small subtest
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.
-lets make a follow up PR to bump for KIC as well https://github.com/kubernetes/minikube/blob/af31c001ad72c82983c1cc59a80689fef4c0de94/deploy/kicbase/Dockerfile#L51-
/ok-to-build-image |
title of PR should be iso/kicbase: |
Good idea for future work, but this should not be a test but a self-test that minkube does after configuring containerd (or other components). For the implementation we should use only command returning machine readable format. minikube ssh -- sudo nerdctl info --format json {
"ID": "e49f45dc-65fc-4ecd-99d5-469a39db14ee",
"Driver": "overlayfs",
"Plugins": {
"Log": [
"fluentd",
"journald",
"json-file",
"none",
"syslog"
],
"Storage": [
"native",
"overlayfs"
]
},
"MemoryLimit": true,
"SwapLimit": true,
"CpuCfsPeriod": true,
"CpuCfsQuota": true,
"CPUShares": true,
"CPUSet": true,
"CPURealtime": false,
"PidsLimit": true,
"IPv4Forwarding": true,
"BridgeNfIptables": true,
"BridgeNfIp6tables": true,
"OomKillDisable": false,
"SystemTime": "2025-09-03T19:43:48.800224305Z",
"LoggingDriver": "json-file",
"CgroupDriver": "systemd",
"CgroupVersion": "2",
"KernelVersion": "6.6.95",
"OperatingSystem": "Buildroot 2025.02",
"OSType": "linux",
"Architecture": "aarch64",
"NCPU": 2,
"MemTotal": 6222721024,
"Name": "minikube",
"ServerVersion": "v2.1.4",
"SecurityOptions": [
"name=seccomp,profile=builtin",
"name=cgroupns"
],
"Warnings": null
} minikube ssh -- systemctl show containerd --no-pager -p LoadState,ActiveState,MainPID,ControlPID,SubState,StateChangeTimestamp
|
This comment has been minimized.
This comment has been minimized.
Hi @nirs, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
/retest-this-please |
This comment has been minimized.
This comment has been minimized.
@nirs please take a look at Docker Linux conainerd test https://storage.googleapis.com/minikube-builds/logs/21409/41274/Docker_Linux_containerd.html#fail_TestDockerEnvContainerd |
/restest-this-please |
This comment has been minimized.
This comment has been minimized.
kvm2 driver with docker runtime
Times for minikube start: 51.3s 49.6s 48.9s 48.6s 49.0s Times for minikube ingress: 15.8s 15.8s 15.8s 15.8s 15.8s docker driver with docker runtime
Times for minikube start: 24.9s 22.9s 26.3s 25.1s 25.1s Times for minikube ingress: 13.6s 13.6s 13.6s 13.6s 13.6s docker driver with containerd runtime
Times for minikube start: 21.9s 22.0s 22.3s 20.9s 22.1s Times for minikube ingress: 23.6s 24.1s 24.1s 24.1s 40.1s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests:
To see the flake rates of all tests by environment, click here. |
I did not see this failure before and have no idea bout the dockerenv feature and also cannot test it (no docker here). Lets do a retest. |
/retest |
We are missing containerd update for kicbase:
|
also $ make update-containerd-version
cd hack && go run update/containerd_version/containerd_version.go
I0904 20:19:56.988592 24785 update.go:91] The Plan:
{
"deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk": {
"Content": null,
"Replace": {
"CONTAINERD_BIN_AARCH64_COMMIT = .*": "CONTAINERD_BIN_AARCH64_COMMIT = 75cb2b7193e4e490e9fbdc236c0e811ccaba3376",
"CONTAINERD_BIN_AARCH64_VERSION = .*": "CONTAINERD_BIN_AARCH64_VERSION = v2.1.4"
}
},
"deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.mk": {
"Content": null,
"Replace": {
"CONTAINERD_BIN_COMMIT = .*": "CONTAINERD_BIN_COMMIT = 75cb2b7193e4e490e9fbdc236c0e811ccaba3376",
"CONTAINERD_BIN_VERSION = .*": "CONTAINERD_BIN_VERSION = v2.1.4"
}
}
}
I0904 20:19:56.990394 24785 update.go:100] Local repo successfully updated $ git diff
diff --git a/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.hash b/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.hash
index 2496b9d51..22c57a285 100644
--- a/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.hash
+++ b/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.hash
@@ -1 +1,2 @@
sha256 846d13bc2bf1c01ae2f20d13beb9b3a1e50b52c86e955b4ac7d658f5847f2b0e containerd-2.1.4-linux-arm64.tar.gz
+sha256 8c409f8a0ba6015cb365a95e039a0fc9f3663c891a26eb52c0fb8cd291ba75d4 v2.1.4.tar.gz
diff --git a/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk b/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk
index 9b44802e2..85591afe5 100644
--- a/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk
+++ b/deploy/iso/minikube-iso/arch/aarch64/package/containerd-bin-aarch64/containerd-bin.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CONTAINERD_BIN_AARCH64_VERSION = 2.1.4
+CONTAINERD_BIN_AARCH64_VERSION = v2.1.4
CONTAINERD_BIN_AARCH64_SITE = https://github.com/containerd/containerd/releases/download/v$(CONTAINERD_BIN_AARCH64_VERSION)
CONTAINERD_BIN_AARCH64_SOURCE = containerd-$(CONTAINERD_BIN_AARCH64_VERSION)-linux-arm64.tar.gz
CONTAINERD_BIN_AARCH64_STRIP_COMPONENTS = 0
diff --git a/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.hash b/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.hash
index 45abbd6ee..dd3ae3bcd 100644
--- a/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.hash
+++ b/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.hash
@@ -1 +1,2 @@
sha256 316d510a0428276d931023f72c09fdff1a6ba81d6cc36f31805fea6a3c88f515 containerd-2.1.4-linux-amd64.tar.gz
+sha256 8c409f8a0ba6015cb365a95e039a0fc9f3663c891a26eb52c0fb8cd291ba75d4 v2.1.4.tar.gz
diff --git a/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.mk b/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.mk
index 40c3338c2..434d8b493 100644
--- a/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.mk
+++ b/deploy/iso/minikube-iso/arch/x86_64/package/containerd-bin/containerd-bin.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CONTAINERD_BIN_VERSION = 2.1.4
+CONTAINERD_BIN_VERSION = v2.1.4
CONTAINERD_BIN_SITE = https://github.com/containerd/containerd/releases/download/v$(CONTAINERD_BIN_VERSION)
CONTAINERD_BIN_SOURCE = containerd-$(CONTAINERD_BIN_VERSION)-linux-amd64.tar.gz
CONTAINERD_BIN_STRIP_COMPONENTS = 0 Issues:
|
@nirs regarding the test TestDockerEnvContainerd it is a legit failure I did 2 retests, if you wanna know what this test is it evals minikube docker-env in to the bash and it expects the "Docker client" talks to the Containerd inside minikube this is done by some network technics we do I forgot is it port forwarding or what |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This is #21368 with the following changes:
Fixes #20497
Based on #21490 for testing