Backport container-stack as MRE for bionic, focal, jammy (September)

Bug #1975769 reported by Bryce Harrington
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
containerd (Ubuntu)
New
Undecided
Lucas Kanashiro
Bionic
New
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Impish
Won't Fix
Undecided
Unassigned
Jammy
New
Undecided
Unassigned
docker.io (Ubuntu)
New
Undecided
Lucas Kanashiro
Bionic
New
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Impish
Won't Fix
Undecided
Unassigned
Jammy
New
Undecided
Unassigned
runc (Ubuntu)
New
Undecided
Lucas Kanashiro
Bionic
New
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Impish
Won't Fix
Undecided
Unassigned
Jammy
New
Undecided
Unassigned

Bug Description

Backport container-stack as MRE for bionic, focal, jammy

Bryce Harrington (bryce)
Changed in containerd (Ubuntu):
milestone: none → ubuntu-22.08
Changed in docker.io (Ubuntu):
milestone: none → ubuntu-22.08
Changed in runc (Ubuntu):
milestone: none → ubuntu-22.08
Bryce Harrington (bryce)
summary: Backport container-stack as MRE for bionic, focal, impish, jammy
+ (August)
summary: - Backport container-stack as MRE for bionic, focal, impish, jammy
- (August)
+ Backport container-stack as MRE for bionic, focal, jammy (September)
Changed in containerd (Ubuntu):
assignee: nobody → Lucas Kanashiro (lucaskanashiro)
milestone: ubuntu-22.08 → ubuntu-22.09
Changed in docker.io (Ubuntu):
assignee: nobody → Lucas Kanashiro (lucaskanashiro)
milestone: ubuntu-22.08 → ubuntu-22.09
Changed in runc (Ubuntu):
assignee: nobody → Lucas Kanashiro (lucaskanashiro)
milestone: ubuntu-22.08 → ubuntu-22.09
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote (last edit ):

I'd not call those updates as MREs because we update all the releases sometimes with a major bump of the upstream version.

description: updated
Changed in containerd (Ubuntu Impish):
status: New → Won't Fix
Changed in docker.io (Ubuntu Impish):
status: New → Won't Fix
Changed in runc (Ubuntu Impish):
status: New → Won't Fix
Revision history for this message
Gert van den Berg (mohag1) wrote :

This prevents Kubernetes 1.26 from being used without a third-party repo for containerd.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.