Backport of container-stack for plucky

Bug #2085187 reported by Bryce Harrington
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
containerd-app (Ubuntu)
Status tracked in Plucky
Plucky
New
Wishlist
Athos Ribeiro
docker.io-app (Ubuntu)
Status tracked in Plucky
Plucky
New
Wishlist
Athos Ribeiro
runc (Ubuntu)
Status tracked in Plucky
Plucky
New
Wishlist
Athos Ribeiro

Bug Description

Backport container-stack to plucky once the update for plucky has been completed.

<List exact versions being upgraded from and to for each release>

[Impact]
TBD

<List bug links to former cases of SRU backports for this package>[Major Changes]
TBD

[Test Plan]
<Link to wiki SRU backport page>TBD

[Regression Potential]
Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters.
<Also, ...>

Bryce Harrington (bryce)
Changed in containerd-app (Ubuntu):
importance: Undecided → Wishlist
milestone: none → ubuntu-25.02
Changed in docker.io-app (Ubuntu):
importance: Undecided → Wishlist
milestone: none → ubuntu-25.02
Changed in runc (Ubuntu):
importance: Undecided → Wishlist
milestone: none → ubuntu-25.02
Changed in containerd-app (Ubuntu Plucky):
assignee: nobody → Athos Ribeiro (athos-ribeiro)
Changed in docker.io-app (Ubuntu Plucky):
assignee: nobody → Athos Ribeiro (athos-ribeiro)
Changed in runc (Ubuntu Plucky):
assignee: nobody → Athos Ribeiro (athos-ribeiro)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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