MRE updates of container stack

Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release.

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release.

PPA: https://launchpad.net/~athos-ribeiro/+archive/ubuntu/ubuntu-container-stack/+packages

Note for the SRU team: I upload this SRU set to jammy twice. Please, disconsider the first batch (the is one bogus/not-needed changelog entry there).

Here are the DEP8 test results. All of them, except for the docker-buildx and docker-compose-v2 ones, were run in the autopkgtest infrastructure in the PPA listed above. For those 2 exceptions, I ran the tests locally because they never passed in our infrastructure due to issues fetching containers from docker hub.

Here are the results:

  - containerd-app/1.7.19-0ubuntu1~20.04.1~ppa8
    + ✅ containerd-app on focal for amd64 @ 22.10.24 22:52:08 Log️ 🗒️
    + ✅ containerd-app on focal for arm64 @ 22.10.24 22:30:25 Log️ 🗒️
    + ✅ containerd-app on focal for armhf @ 22.10.24 22:31:26 Log️ 🗒️
    + ✅ containerd-app on focal for ppc64el @ 22.10.24 22:31:07 Log️ 🗒️
    + ✅ containerd-app on focal for s390x @ 22.10.24 22:30:58 Log️ 🗒️

  - containerd-app/1.7.19-0ubuntu1~22.04.1~ppa1
    + ✅ containerd-app on jammy for amd64 @ 15.10.24 01:44:06 Log️ 🗒️
    + ✅ containerd-app on jammy for arm64 @ 15.10.24 01:46:35 Log️ 🗒️
    + ✅ containerd-app on jammy for armhf @ 15.10.24 01:44:57 Log️ 🗒️
    + ✅ containerd-app on jammy for ppc64el @ 15.10.24 01:46:27 Log️ 🗒️
    + ✅ containerd-app on jammy for s390x @ 15.10.24 01:44:52 Log️ 🗒️

  - containerd-app/1.7.19-0ubuntu1~24.04.1~ppa1
    + ✅ containerd-app on noble for amd64 @ 15.10.24 01:43:24 Log️ 🗒️
    + ✅ containerd-app on noble for arm64 @ 15.10.24 01:46:19 Log️ 🗒️
    + ✅ containerd-app on noble for armhf @ 15.10.24 01:47:17 Log️ 🗒️
    + ✅ containerd-app on noble for ppc64el @ 15.10.24 01:46:42 Log️ 🗒️
    + ✅ containerd-app on noble for s390x @ 15.10.24 01:49:01 Log️ 🗒️

  - runc-app/1.1.12-0ubuntu4~22.04.1~ppa1
    + ✅ runc-app on jammy for amd64 @ 15.10.24 01:48:11 Log️ 🗒️
    + ✅ runc-app on jammy for arm64 @ 15.10.24 01:52:58 Log️ 🗒️
    + ✅ runc-app on jammy for armhf @ 15.10.24 01:47:04 Log️ 🗒️
    + ✅ runc-app on jammy for ppc64el @ 15.10.24 01:52:04 Log️ 🗒️
    + ✅ runc-app on jammy for s390x @ 15.10.24 01:51:17 Log️ 🗒️

  - runc-app/1.1.12-0ubuntu4~24.04.1~ppa1
    + ✅ runc-app on noble for amd64 @ 15.10.24 01:48:24 Log️ 🗒️
    + ✅ runc-app on noble for arm64 @ 15.10.24 01:52:54 Log️ 🗒️
    + ✅ runc-app on noble for armhf @ 15.10.24 01:47:10 Log️ 🗒️
    + ✅ runc-app on noble for ppc64el @ 15.10.24 01:51:24 Log️ 🗒️
    + ✅ runc-app on noble for s390x @ 15.10.24 01:51:13 Log️ 🗒️

    - runc-app/1.1.12-0ubuntu4~20.04.1~ppa3
    + ✅ runc-app on focal for amd64 @ 22.10.24 20:58:26 Log️ 🗒️
    + ✅ runc-app on focal for arm64 @ 22.10.24 20:05:50 Log️ 🗒️
    + ✅ runc-app on focal for armhf @ 22.10.24 20:01:50 Log️ 🗒️
    + ✅ runc-app on focal for ppc64el @ 22.10.24 20:08:10 Log️ 🗒️
    + ✅ runc-app on focal for s390x @ 22.10.24 20:08:57 Log️ 🗒️

  - docker.io-app/26.1.3-0ubuntu1~22.04.1~ppa1
    + ✅ docker.io-app on jammy for amd64 @ 15.10.24 13:55:47 Log️ 🗒️
    + ✅ docker.io-app on jammy for arm64 @ 15.10.24 14:01:04 Log️ 🗒️
    + ✅ docker.io-app on jammy for armhf @ 15.10.24 01:47:13 Log️ 🗒️
    + ✅ docker.io-app on jammy for ppc64el @ 15.10.24 14:02:55 Log️ 🗒️
    + ✅ docker.io-app on jammy for s390x @ 15.10.24 13:57:54 Log️ 🗒️

  - docker.io-app/26.1.3-0ubuntu1~20.0...

I don't see the need to MRE runc-app, because the proposed version is already in all stable releases, and devel:

runc-app | 1.1.12-0ubuntu2~20.04.1 | focal-updates/universe | source
runc-app | 1.1.12-0ubuntu2~22.04.1 | jammy-updates/universe | source
runc-app | 1.1.12-0ubuntu3 | noble | source
runc-app | 1.1.12-0ubuntu3.1 | noble-updates | source
runc-app | 1.1.12-0ubuntu4~20.04.1 | focal/unapproved/313157f | source
runc-app | 1.1.12-0ubuntu4~22.04.1 | jammy/unapproved/3334c95 | source
runc-app | 1.1.12-0ubuntu4~24.04.1 | noble/unapproved/890596d | source
runc-app | 1.1.12-0ubuntu4 | oracular | source
runc-app | 1.1.12-0ubuntu4 | plucky | source

Hello Bryce, or anyone else affected,

Accepted docker-buildx into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-buildx/0.14.1-0ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker.io-app into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/26.1.3-0ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted containerd-app into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.19-0ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker-compose-v2 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-compose-v2/2.27.1+ds1-0ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.19-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker.io-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/26.1.3-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker-buildx into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-buildx/0.14.1-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker-compose-v2 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-compose-v2/2.27.1+ds1-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker-compose-v2 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-compose-v2/2.27.1+ds1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker.io-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/26.1.3-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted docker-buildx into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker-buildx/0.14.1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.19-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html#docker.io-app is clear

I also checked the individual runs in https://autopkgtest.ubuntu.com/packages/docker.io-app for noble in all architectures, and they are either green, or an expected failure like on i386.

The tests in the infrastructure are failing, but have been failing before, due to firewall restrictions.

Because it's not a new failure, the excuses report is not flagging it as a regression, and the packages appear ready to release.

However, since the whole test plan for this SRU is the autopkgtests, they need to be run, even if just locally.

I'm attempting that for a couple of hours now, but I can't get them to pass locally. Some networking issue.

Since there are other SRUs to review, and I only have today, it's not fair to keep spending time here. I already spent too much.

This SRU is blocked from release until someone does a successful autopkgtest run of all packages and states so here with a comment, including the package versions.

All autopkgtests for the newly accepted docker.io-app (26.1.3-0ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-fan/unknown (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#docker.io-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted docker.io-app (26.1.3-0ubuntu1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#docker.io-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

There is nothing blocking these from migrating as per
https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html
https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html

The containerd-app tests are passing in our infrastructure for all series (noble, jammy, focal).

The docker.io-app tests are passing in our infrastructure for jammy and focal, but are failing for noble (no regressions here. I will run this locally).

The tests for docker-compose-v2 and docker-buildx are failing for all series (noble, jammy, focal). I will also run these locally.

docker-compose-v2 version 2.27.1+ds1-0ubuntu1~20.04.1:
basic-smoke PASS
docker-compose-v2 version 2.27.1+ds1-0ubuntu1~22.04.1:
basic-smoke PASS
docker-compose-v2 version 2.27.1+ds1-0ubuntu1~24.04.1:
basic-smoke PASS

docker-buildx version 0.14.1-0ubuntu1~20.04.1:
basic-smoke FAIL non-zero exit status 1
docker-buildx version 0.14.1-0ubuntu1~22.04.1:
basic-smoke FAIL non-zero exit status 1
docker-buildx version 0.14.1-0ubuntu1~24.04.1:
basic-smoke FAIL non-zero exit status 1

Still missing the docker.io-app tests (autopkgtest is through errors when trying to install the package from -proposed due to gpg sig verification errors).

I am investigating the docker-buildx failures now.

docker.io-app version 26.1.3-0ubuntu1~24.04.1 (noble):
autopkgtest [12:47:34]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

For docker-buildx, the failure was related to a missing package (file) in my local image. The package is seeded and is usually available in our autopkgtest env images. I will fix the package in devel to include this test dependency for future runs, but this should not block this MRE IMHO.

docker-buildx version 0.14.1-0ubuntu1~20.04.1:
basic-smoke PASS
docker-buildx version 0.14.1-0ubuntu1~22.04.1:
basic-smoke PASS
docker-buildx version 0.14.1-0ubuntu1~24.04.1:
basic-smoke PASS

With this, all the packages are verified in all series.

This bug was fixed in the package containerd-app - 1.7.19-0ubuntu1~24.04.1

---------------
containerd-app (1.7.19-0ubuntu1~24.04.1) noble; urgency=medium

  * Backport from oracular to noble. (LP: #2040461)
    - d/containerd.postinst: notify that a reboot is required to reload the
      AppArmor profile. (LP: #2065423)
    - d/p/0002-Skip-tests-which-require-a-certain-level-of-privileg.patch:
      drop bogus entry.
    - d/rules: do not skip pkg/cri/server tests. These were being skipped due
      to a bogus entry in d/patches.

containerd-app (1.7.19-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * d/t/basic-smoke: set proxy environment variables.

containerd-app (1.7.17-0ubuntu1) oracular; urgency=medium

  * New upstream release.
    - Update AppArmor template to allow confined runc to kill containers
      (LP: #2065423).
  * Refresh patches.
    - d/p/{0006-Skip-test-setting-OOM-score-to-negative-number-in-un,
      0007-seccomp-apparmor-add-go-noinline}.patch: removed, applied by
      upstream.
  * d/rules: skip cri server tests.
  * d/rules: fix path of containerd commands.

 -- Athos Ribeiro <email address hidden> Fri, 11 Oct 2024 16:19:07 -0300

The verification of the Stable Release Update for containerd-app has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package docker-buildx - 0.14.1-0ubuntu1~24.04.1

---------------
docker-buildx (0.14.1-0ubuntu1~24.04.1) noble; urgency=medium

  * Backport from oracular to noble. (LP: #2040461)

docker-buildx (0.14.1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * d/docker-buildx.docs: remove NOTICE file of a removed dependency.

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 09:19:33 -0300

This bug was fixed in the package docker-compose-v2 - 2.27.1+ds1-0ubuntu1~24.04.1

---------------
docker-compose-v2 (2.27.1+ds1-0ubuntu1~24.04.1) noble; urgency=medium

  * Backport from oracular to noble. (LP: #2040461)

docker-compose-v2 (2.27.1+ds1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * Refresh patch.

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 11:16:52 -0300

This bug was fixed in the package docker.io-app - 26.1.3-0ubuntu1~24.04.1

---------------
docker.io-app (26.1.3-0ubuntu1~24.04.1) noble; urgency=medium

  * Backport from oracular to noble. (LP: #2040461)
    - d/t/docker-in-lxd: workaround Apparmor/kernel bug. (LP #2067900)
    - Update AppArmor template to allow confined runc to kill containers
      (LP: #2065423).
      + d/docker.io.postinst: notify that a reboot is required to apply the
        fix (the AppArmor profile need to be reloaded).

docker.io-app (26.1.3-0ubuntu1) oracular; urgency=medium

  * New upstream release.
    - Allow runc to kill containers when confined to the runc profile in
      AppArmor version 4.0.0 and later.
  * d/helpers/build-manpages.sh: build manpages with Go 1.21.
  * d/manpages: update them all.
  * d/docker.io.docs: remove NOTICE file of a dependency removed from cli.

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 11:29:26 -0300

https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2065423/comments/41 containerd-app regression

Opened https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2089704 to handle this regression.

Adding block-proposed-* tags. Please, do not release these until further notice.See LP: #2089704

Hello Bryce, or anyone else affected,

Accepted containerd-app into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.24-0ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.24-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Bryce, or anyone else affected,

Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd-app/1.7.24-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted containerd-app (1.7.24-0ubuntu1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/24.0.7-0ubuntu2~22.04.1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#containerd-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted containerd-app (1.7.24-0ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

containerd-app/1.7.24-0ubuntu1~20.04.1 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#containerd-app

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All DEP-8 tests are passing as expected. The failures listed above were due to flakiness, have been re triggered and are now passing. As per the test plan, I am marking this as verified.

This bug was fixed in the package containerd-app - 1.7.24-0ubuntu1~24.04.1

---------------
containerd-app (1.7.24-0ubuntu1~24.04.1) noble; urgency=medium

  * Backport version 1.7.19-0ubuntu3 from plucky to noble. (LP: #2040461)
  * New 1.7.24 upstream version. (LP #2089704)
  * d/containerd.postinst: notify that a reboot is required to reload the
    AppArmor profile. (LP #2065423)
  * d/p/{0001-...,0002-...}: restore the version of these patches which
    applies to 1.7.x.
  * d/rules: revert path of containerd commands

 -- Athos Ribeiro <email address hidden> Fri, 11 Oct 2024 16:19:07 -0300

This bug was fixed in the package containerd-app - 1.7.24-0ubuntu1~22.04.1

---------------
containerd-app (1.7.24-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport version 1.7.19-0ubuntu3 from plucky to jammy. (LP: #2040461)
  * New 1.7.24 upstream version. (LP: #2089704)
  * d/rules: fix path of the containerd systemd service file.
  * d/p/{0001-...,0002-...}: restore the version of these patches which
    applies to 1.7.x.
  * d/rules: revert path of containerd commands

 -- Athos Ribeiro <email address hidden> Fri, 11 Oct 2024 16:30:33 -0300

This bug was fixed in the package docker-buildx - 0.14.1-0ubuntu1~22.04.1

---------------
docker-buildx (0.14.1-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport from oracular to jammy. (LP: #2040461)

docker-buildx (0.14.1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * d/docker-buildx.docs: remove NOTICE file of a removed dependency.

docker-buildx (0.12.1-0ubuntu2) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 09:43:26 -0300

This bug was fixed in the package docker-compose-v2 - 2.27.1+ds1-0ubuntu1~22.04.1

---------------
docker-compose-v2 (2.27.1+ds1-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport from oracular to jammy. (LP: #2040461)

docker-compose-v2 (2.27.1+ds1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * Refresh patch.

docker-compose-v2 (2.24.6+ds1-0ubuntu2) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 11:21:04 -0300

This bug was fixed in the package docker.io-app - 26.1.3-0ubuntu1~22.04.1

---------------
docker.io-app (26.1.3-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport from oracular to jammy. (LP: #2040461)

docker.io-app (26.1.3-0ubuntu1) oracular; urgency=medium

  * New upstream release.
    - Allow runc to kill containers when confined to the runc profile in
      AppArmor version 4.0.0 and later.
  * d/helpers/build-manpages.sh: build manpages with Go 1.21.
  * d/manpages: update them all.
  * d/docker.io.docs: remove NOTICE file of a dependency removed from cli.

docker.io-app (24.0.7-0ubuntu4) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

docker.io-app (24.0.7-0ubuntu3) noble; urgency=medium

  * No-change rebuild for CVE-2024-3094

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 18:24:40 -0300

This bug was fixed in the package containerd-app - 1.7.24-0ubuntu1~20.04.1

---------------
containerd-app (1.7.24-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport version 1.7.19-0ubuntu3 from plucky to focal. (LP: #2040461)
  * New 1.7.24 upstream version. (LP: #2089704)
  * d/rules: fix path of the containerd systemd service file.
  * d/control: BuildDepends on procps. It is missing for riscv64 in focal.
  * d/p/{0001-...,0002-...}: restore the version of these patches which
    applies to 1.7.x.
  * d/rules: revert path of containerd commands

 -- Athos Ribeiro <email address hidden> Fri, 11 Oct 2024 16:36:50 -0300

This bug was fixed in the package docker-buildx - 0.14.1-0ubuntu1~20.04.1

---------------
docker-buildx (0.14.1-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport from oracular to focal. (LP: #2040461)

docker-buildx (0.14.1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * d/docker-buildx.docs: remove NOTICE file of a removed dependency.

docker-buildx (0.12.1-0ubuntu2) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 09:50:41 -0300

This bug was fixed in the package docker-compose-v2 - 2.27.1+ds1-0ubuntu1~20.04.1

---------------
docker-compose-v2 (2.27.1+ds1-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport from oracular to focal. (LP: #2040461)

docker-compose-v2 (2.27.1+ds1-0ubuntu1) oracular; urgency=medium

  * New upstream release.
  * Refresh patch.

docker-compose-v2 (2.24.6+ds1-0ubuntu2) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 11:22:12 -0300

This bug was fixed in the package docker.io-app - 26.1.3-0ubuntu1~20.04.1

---------------
docker.io-app (26.1.3-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport from oracular to focal. (LP: #2040461)
    - d/t/basic-smoke: import GPG key from Debian stable. The
      debian-archive-keyring package is out-dated after the release of Debian
      12. Now, the key is downloaded from the ftp-master keyring directly.

docker.io-app (26.1.3-0ubuntu1) oracular; urgency=medium

  * New upstream release.
    - Allow runc to kill containers when confined to the runc profile in
      AppArmor version 4.0.0 and later.
  * d/helpers/build-manpages.sh: build manpages with Go 1.21.
  * d/manpages: update them all.
  * d/docker.io.docs: remove NOTICE file of a dependency removed from cli.

docker.io-app (24.0.7-0ubuntu4) noble; urgency=medium

  * Build with Go 1.22.
    - d/control: b-d on golang-1.22-go instead of golang-1.21-go
    - d/rules: add Go 1.22 to $PATH

docker.io-app (24.0.7-0ubuntu3) noble; urgency=medium

  * No-change rebuild for CVE-2024-3094

 -- Athos Ribeiro <email address hidden> Mon, 14 Oct 2024 19:06:01 -0300

Potential regression in https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2098106