** Description changed: [Impact] In order to follow our policy on keeping the container stack (docker.io- app, containerd-app, runc, runc-app, docker-buildx, and docker- compose-v2) up-to-date in our supported releases, let's backport the stack in Plucky to Oracular, Noble, Jammy, and Focal. [Test Plan] Per https://wiki.ubuntu.com/DockerUpdates, our test case is the autopkgtests. + All packages were built in https://launchpad.net/~athos- + ribeiro/+archive/ubuntu/container-stack-pp/+packages. + + Apart from runc-app, all packages are failing their autopkgtest runs in + our infrastructure due to the dockerhub pull rate limits. For those + (docker.io-app, containerd-app, docker-buildx, and docker-compose-v2), + we ran the autopkgtest suite locally. All tests are passing. + [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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085187 Title: Backport of container-stack for plucky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2085187/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
