Bump containerd to 2.0 #11375
Milestone
Comments
|
We are aiming for containerd 2.0 sometime in Q1 of 2025. |
|
It's only been out for three weeks, that's not "a while" for a new major version. We will probably wait for a couple patch releases at least. We will probably also pick a new Kubernetes minor release and only ship containerd 2.0 with that, and leave the older minors on containerd 1.7. |
kranurag7
added a commit
to kranurag7/os
that referenced
this issue
Nov 27, 2024
# containerd-shim-runc-v2 is now pulling in versions > 2.0.0 by default. (containerd/containerd#10984) # pinning is required because any version >2.0.0 is not compatible with daemon < 2.0.0 # daemon in this case is coming from k3s itself and they've not migrated yet to version > 2.0.0 # there's is an issue tracking k3s update to containerd > 2.0.0 (k3s-io/k3s#11375) # remove pin once upstream migrates to containerd > 2.0.0 Signed-off-by: kranurag7 <[email protected]>
kranurag7
added a commit
to kranurag7/os
that referenced
this issue
Nov 27, 2024
containerd-shim-runc-v2 is now pulling in versions > 2.0.0 by default. (containerd/containerd#10984) pinning is required because any version >2.0.0 is not compatible with daemon < 2.0.0 daemon in this case is coming from k3s itself and upstream k3s project have not migrated yet to version > 2.0.0 there's is an issue tracking k3s update to containerd > 2.0.0 (k3s-io/k3s#11375) remove pin once upstream migrates to containerd > 2.0.0 Signed-off-by: kranurag7 <[email protected]>
kranurag7
added a commit
to kranurag7/os
that referenced
this issue
Nov 27, 2024
containerd-shim-runc-v2 is now pulling in versions > 2.0.0 by default. (containerd/containerd#10984) pinning is required because any version >2.0.0 is not compatible with daemon < 2.0.0 daemon in this case is coming from k3s itself and upstream k3s project have not migrated yet to version > 2.0.0 there's is an issue tracking k3s update to containerd > 2.0.0 (k3s-io/k3s#11375) remove pin once upstream migrates to containerd > 2.0.0 Signed-off-by: kranurag7 <[email protected]>
joshrwolf
added a commit
to wolfi-dev/os
that referenced
this issue
Nov 27, 2024
notes: containerd-shim-runc-v2 is now pulling in versions > 2.0.0 by default. (containerd/containerd#10984) pinning is required because any version >2.0.0 is not compatible with daemon < 2.0.0 daemon in this case is coming from k3s itself and upstream k3s project have not migrated yet to version > 2.0.0 there's is an issue tracking k3s update to containerd > 2.0.0 (k3s-io/k3s#11375) remove pin once upstream migrates to containerd > 2.0.0 this also removes k3s-images subpackage because we no longer have those images available. --------- Signed-off-by: kranurag7 <[email protected]> Co-authored-by: Josh Wolf <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Containerd 2.0 has been released for a while, bring in a lot of nice features, should we consider to upgrade ?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: