-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
containerd: upgrade io.containerd.runtime.v1.linux
to io.containerd.runc.v2
(suppot cgroup v2)
#11325
Conversation
…d.runc.v2` To support cgroup v2, the runtime has to be upgraded to `io.containerd.runc.v2`. Also, `io.containerd.runtime.v1.linux` has been deprecated since containerd v1.4. Tested with `--driver=docker`, on Ubuntu 21.04 + Docker 20.10 + cgroup v2. Fix issue 11310 Signed-off-by: Akihiro Suda <[email protected]>
Hi @AkihiroSuda. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AkihiroSuda 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 |
io.containerd.runtime.v1.linux
to io.containerd.runc.v2
io.containerd.runtime.v1.linux
to io.containerd.runc.v2
(suppot cgroup v2)
Can one of the admins verify this patch? |
@AkihiroSuda thank you for this pr. Will it break users who dont have cgroup v2? In that case how about we enable cgroup v2 only for users who have it and keep v1 for others ? |
The io.containerd.runc.v2 runtime supports both cgroup v1 and cgroup v2. io.containerd.runtime.v1.linux is completely deprecated and unrecommended, even for cgroup v1 hosts. |
excellent thank you for educating me, there are a lot of things on containerd need to learn, minikube's default runtime been "docker" and our containerd is catching up, this seems like the right thing to do, I am gonna check the performance difference and integration tests |
/ok-to-test |
@AkihiroSuda: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
kvm2 driver with docker runtime
Times for minikube start: 55.4s 55.9s 55.8s 57.4s 55.2s Times for minikube (PR 11325) ingress: 43.8s 43.9s 43.9s 44.3s 42.9s docker driver with docker runtime
Times for minikube start: 24.2s 23.2s 23.8s 24.1s 23.3s Times for minikube (PR 11325) ingress: 34.1s 35.5s 32.5s 32.0s 36.1s docker driver with containerd runtime
Times for minikube start: 48.2s 48.4s 44.3s 44.4s 44.3s |
weird the integration test for docker_containerd_linux is taking more than 2 hours and counting...it usually ends in less than 70 minutes |
I would very much prefer if we could drop the inline configuration of containerd and dockerd And only update the fields that we care about, and leave the rest to the original installation... |
👍, but can we visit that in another PR? We also have to switch away from config format v1 to config format v2. |
Yes, it is a separate topic. But it would have avoided the need from having to update the embedded config. |
/retest-this-please |
kvm2 driver with docker runtime
Times for minikube (PR 11325) start: 46.2s 47.4s 50.5s 46.2s 47.6s Times for minikube ingress: 40.2s 34.2s 34.2s 38.4s 34.2s docker driver with docker runtime
Times for minikube start: 22.1s 23.5s 20.8s 22.0s 21.8s Times for minikube ingress: 29.9s 25.5s 29.0s 31.5s 31.5s docker driver with containerd runtime
Times for minikube start: 30.7s 46.8s 44.8s 43.4s 49.0s |
/retest-this-please |
kvm2 driver with docker runtime
Times for minikube start: 53.3s 50.4s 48.1s 47.8s 46.3s Times for minikube ingress: 34.3s 35.7s 34.3s 35.7s 34.2s docker driver with docker runtime
Times for minikube start: 23.7s 21.0s 21.6s 21.5s 22.0s Times for minikube ingress: 27.0s 30.5s 37.0s 28.0s 28.0s docker driver with containerd runtime
Times for minikube start: 31.4s 42.9s 47.4s 43.1s 42.9s |
To support cgroup v2, the runtime has to be upgraded to
io.containerd.runc.v2
.Also,
io.containerd.runtime.v1.linux
has been deprecated since containerd v1.4.Tested with
--driver=docker
, on Ubuntu 21.04 + Docker 20.10 + cgroup v2.fixes #11310