** Description changed: [Impact] In order to follow our policy [1,2] on keeping the container stack (docker.io-app, containerd-app, runc-app, docker-buildx, docker- compose-v2, containerd-stable, and runc-stable) up-to-date in our supported releases, let's backport the stack in resolute to questing, noble, and jammy. Special cases: - containerd-stable and runc-stable are only present from questing and on. Therefore, these packages will only be backported to questing. - - Since noble and jammy have no *-stable versions of containerd and runc, for those series, containerd-app will be upgraded to the newest version of 1.7.x and runc-app will be upgraded to the newest version of 1.3.y to to avoid major disruptions as covered by the process described in [1]. + - runc-app will be upgraded to the newest version of 1.3.y in noble and jammy to to avoid major disruptions as covered by the process described in [1]. CVEs: TBD [Test Plan] As described in [1], our test case is the autopkgtests. All packages were built in https://launchpad.net/~athos- ribeiro/+archive/ubuntu/container-stack-rr/+packages. TBD: autopkgtest results [Where problems could occur] As usual, we deliver most benefit to our users by delivering an upstream experience. A risk of regressions is part of that. [Past MREs] - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040461 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040460 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2085187 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2112523 [ References ] [1] https://documentation.ubuntu.com/sru/en/latest/reference/exception-Docker-Updates/ [2] https://discourse.ubuntu.com/t/ubuntu-server-gazette-issue-8-containers-steady-paths-for-agile-stacks/68680
** Description changed: [Impact] In order to follow our policy [1,2] on keeping the container stack (docker.io-app, containerd-app, runc-app, docker-buildx, docker- compose-v2, containerd-stable, and runc-stable) up-to-date in our supported releases, let's backport the stack in resolute to questing, noble, and jammy. Special cases: - containerd-stable and runc-stable are only present from questing and on. Therefore, these packages will only be backported to questing. - runc-app will be upgraded to the newest version of 1.3.y in noble and jammy to to avoid major disruptions as covered by the process described in [1]. - - CVEs: TBD [Test Plan] As described in [1], our test case is the autopkgtests. All packages were built in https://launchpad.net/~athos- ribeiro/+archive/ubuntu/container-stack-rr/+packages. TBD: autopkgtest results [Where problems could occur] As usual, we deliver most benefit to our users by delivering an upstream experience. A risk of regressions is part of that. [Past MREs] - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040461 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040460 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2085187 - https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2112523 [ References ] [1] https://documentation.ubuntu.com/sru/en/latest/reference/exception-Docker-Updates/ [2] https://discourse.ubuntu.com/t/ubuntu-server-gazette-issue-8-containers-steady-paths-for-agile-stacks/68680 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127661 Title: Backport of container-stack for jammy, noble and questing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2127661/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
