Backport container stack from Lunar

[Lucas Kanashiro]

[Impact]

In order to follow our policy on keeping the container stack (docker.io, containerd, and runc) up-to-date in our supported releases, let's backport the stack in Lunar to Kinetic, Jammy, Focal, and Bionic.

[Test Plan]

Per https://wiki.ubuntu.com/DockerUpdates, our test case is the autopkgtests.

[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.

[Andreas Hasenack (ahasenack)]

I'm reviewing this today as part of my SRU shift.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.4-0ubuntu1~22.10.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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.10.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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted containerd into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~22.10.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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.4-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted containerd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.4-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted containerd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted runc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.1.4-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted containerd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.6.12-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

golang-github-fsouza-go-dockerclient/1.6.0-2ubuntu0.20.04.1 (s390x, armhf, amd64, ppc64el, arm64)
golang-github-openshift-imagebuilder/1.1.0-2ubuntu0.20.04.1 (s390x, armhf, amd64, ppc64el, 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#docker.io

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

docker.io/20.10.21-0ubuntu1~18.04.1 (ppc64el, arm64, s390x)

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/bionic/update_excuses.html#docker.io

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

golang-github-fsouza-go-dockerclient and golang-github-openshift-imagebuilder are FTBFSing against the docker.io version in focal-proposed right now because the docker library cannot be built with Golang 1.16. We need to make them build with Golang 1.18 now to fix it.

[Lucas Kanashiro (lucaskanashiro)]

golang-github-fsouza-go-dockerclient and golang-github-openshift-imagebuilder built fine with Golang 1.18 and autopkgtest passed locally as well.

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-backports/+packages

[Lucas Kanashiro (lucaskanashiro)]

For the docker.io regression in Bionic, the issue is that apparently we cannot debootstrap bionic in bionic on arm64, ppc64el and s390x. We changed the suite to bionic because previously it was not able to debootstrap debian unstable in bionic due to keyring issues. What should we use as debootstrap suite in bionic?

[Lucas Kanashiro (lucaskanashiro)]

I uploaded to my PPA docker.io not passing any mirror url to the debootstrap call in the basic-smoke test and fixed all the regressions:

Results: (from http://autopkgtest.ubuntu.com/results/autopkgtest-bionic-lucaskanashiro-container-backports/?format=plain)
  docker.io @ amd64:
    30.01.23 20:56:46 Log 🗒️ ✅ Triggers: docker.io/20.10.21-0ubuntu1~18.04.2~ppa2
  docker.io @ arm64:
    30.01.23 20:43:06 Log 🗒️ ⚪ Triggers: docker.io/20.10.21-0ubuntu1~18.04.2~ppa2
      No valid results
  docker.io @ armhf:
    30.01.23 20:29:56 Log 🗒️ ✅ Triggers: docker.io/20.10.21-0ubuntu1~18.04.2~ppa2
  docker.io @ ppc64el:
    30.01.23 20:43:27 Log 🗒️ ✅ Triggers: docker.io/20.10.21-0ubuntu1~18.04.2~ppa2
  docker.io @ s390x:

in arm64 there was an issue to set up the testbed but since it got fixed in the other architectures I expect the same for arm64. I'll be uploading a new version to -unapproved with this change.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~18.04.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

docker.io/20.10.21-0ubuntu1~18.04.1 (arm64, s390x, ppc64el)

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/bionic/update_excuses.html#docker.io

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

Thank you!

[Andreas Hasenack (ahasenack)]

The above comment is bogus. In comment #22 we accepted 20.10.21-0ubuntu1~18.04.2, and the comment about autopkgtest regression is for 20.10.21-0ubuntu1~18.04.1.

I just checked and at this moment, https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#docker.io is showing 20.10.21-0ubuntu1~18.04.2 being tested, so let's wait.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted golang-github-openshift-imagebuilder into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-github-openshift-imagebuilder/1.1.0-2ubuntu0.20.04.2 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted golang-github-fsouza-go-dockerclient into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/1.6.0-2ubuntu0.20.04.2 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

docker.io/unknown (arm64)
docker.io/20.10.21-0ubuntu1~18.04.2 (i386, ppc64el, amd64, s390x)

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/bionic/update_excuses.html#docker.io

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

Thank you!

[Lucas Kanashiro (lucaskanashiro)]

All regressions were fixed after some test re-triggers.

[Lucas Kanashiro (lucaskanashiro)]

# Bionic verification

## Running autopkgtest with -proposed enabled

### runc

autopkgtest [11:56:41]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

### containerd

autopkgtest [11:53:41]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

### docker.io

autopkgtest [12:00:38]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

[Lucas Kanashiro (lucaskanashiro)]

# Focal verification

## Running autopkgtest with -proposed enabled

### runc

autopkgtest [12:15:01]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

### containerd

autopkgtest [11:53:58]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

### docker.io

autopkgtest [12:01:31]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

[Lucas Kanashiro (lucaskanashiro)]

Jammy and Kinetic (also Lunar) have a test failure (docker-in-lxd test) because it tries to install lxd via apt, and since Jammy it is not available as a .deb anymore. I'll update the packages to install lxd via snap.

[Lucas Kanashiro (lucaskanashiro)]

I fixed docker.io in Jammy and Kinetic (also Lunar). It is in -unapproved again, waiting for review.

[Andreas Hasenack (ahasenack)]

> Jammy and Kinetic (also Lunar) have a test failure (docker-in-lxd test) because it tries
> to install lxd via apt, and since Jammy it is not available as a .deb anymore. I'll update
> the packages to install lxd via snap.

Your upload contains another change, not discussed here: the docker-in-lxd test is now using a privileged container for kinetic (and lunar, for that matter).

Do we know why we now need a privileged lxd container to run docker, and more importantly, why that is not a regression? The test caught it, right, since you had to change the test.

And why isn't that needed for focal, which is also using a snap for lxd, so presumably the same lxd version as kinetic? Different kernel?

[Andreas Hasenack (ahasenack)]

I tried multiple times to run the dep8 test locally with a vm, with different ubuntu releases, but they just don't work, some networking issue. From inside the container, apt just won't work. And it's not my proxy.

Perhaps we should wait to see if these packages finally pass dep8 tests in lunar? Although that could take days and days, given the state of the queues.

Do you have the error log for the failure when the container wasn't privileged? With a ppa perhaps, with only these packages for the SRU?

[Lucas Kanashiro (lucaskanashiro)]

No, I do not. I have been executing all those tests locally as part of the verification process. If you want I can re-run it locally without the change and attach the logs here.

If possible I would prefer to not wait for lunar migration, as you mentioned it will likely take a week.

[Andreas Hasenack (ahasenack)]

What about the questions from comment #33?

[Lucas Kanashiro (lucaskanashiro)]

And I do not believe this is a regression in docker.io because the daemon tries to create a directory to store the image and the filesystem is read-only. Outside the lxd container the same command works fine. The error is in the commit message here:

https://github.com/tianon/debian-docker/commit/e44fd120bbd0381a08baef2cbac789b82635af2d

But I do not know whether the behavior change comes from lxd or linux. It will require further investigation.

[Lucas Kanashiro (lucaskanashiro)]

Searching for the error on the Internet I found the following threads:

https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017
https://discuss.linuxcontainers.org/t/run-docker-on-lxd-container/11575
https://discuss.linuxcontainers.org/t/docker-with-overlay-driver-in-lxd-cluster-not-working/9243

The error might be related to how lxd storage is setup and the kernel. I believe the best solution is to add the following to the unprivileged container configuration:

security.nesting=true
security.syscalls.intercept.mknod=true
security.syscalls.intercept.setxattr=true

Instead of running a privileged container (see @stgraber's comments on those threads).

[Lucas Kanashiro (lucaskanashiro)]

I just tried what I described in comment #38 in Kinetic and Lunar and it did not work, I still get the following error:

+ lxc exec docker -- docker run amd64/hello-world
Unable to find image 'amd64/hello-world:latest' locally
latest: Pulling from amd64/hello-world
2db29710123e: Pulling fs layer
2db29710123e: Verifying Checksum
2db29710123e: Download complete
2db29710123e: Pull complete
Digest: sha256:e62ef360f4588f4e64a0b31a1e5e975502e16aeda62f00fab662eca6317edfde
Status: Downloaded newer image for amd64/hello-world:latest
docker: Error response from daemon: mkdir /var/lib/docker/overlay2/e1369ac27f929368353dea87aed51f99c694e3fe12dccf8a1fbcfb6be63f19e1-init/merged/dev: read-only file system.
See 'docker run --help'.

This might mean that we use zfs backend as lxd storage which does not support overlay2. However, this works when executed in a privileged container.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.10.2 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Andreas Hasenack (ahasenack)]

Hello Lucas, or anyone else affected,

Accepted docker.io into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1~22.04.2 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.

[Lucas Kanashiro (lucaskanashiro)]

# Jammy verification

## Running autopkgtest with -proposed enabled

### runc

autopkgtest [17:30:55]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

## containerd

autopkgtest [17:25:23]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

## docker.io

autopkgtest [17:38:04]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

[Lucas Kanashiro (lucaskanashiro)]

# Kinetic verification

## Running autopkgtest with -proposed enabled

### runc

autopkgtest [17:35:43]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
command1 PASS

## containerd

autopkgtest [17:28:20]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS

## docker.io

autopkgtest [17:42:54]: @@@@@@@@@@@@@@@@@@@@ summary
basic-smoke PASS
docker-in-lxd PASS

[Andreas Hasenack (ahasenack)]

I verified the test results and am satisfied that they show the executed planned test case, and that the results are correct.

The package built correctly in all architectures and Ubuntu releases it was meant for.

There are no DEP8 regressions.

There is no SRU freeze ongoing at the moment.

There is no halted phasing on the previous update.

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.4-0ubuntu1~22.10.1

---------------
runc (1.1.4-0ubuntu1~22.10.1) kinetic; urgency=medium

  * Backport version 1.1.4-0ubuntu1 from Lunar (LP: #1996909).

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 11:57:32 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.12-0ubuntu1~22.10.1

---------------
containerd (1.6.12-0ubuntu1~22.10.1) kinetic; urgency=medium

  * Backport version 1.6.12-0ubuntu1 from Lunar (LP: #1996909).

 -- Lucas Kanashiro <email address hidden> Tue, 03 Jan 2023 17:55:47 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu1~22.10.2

---------------
docker.io (20.10.21-0ubuntu1~22.10.2) kinetic; urgency=medium

  * d/tests: install lxd via snap in docker-in-lxd test.
    Since Jammy, lxd is not available as a .deb anymore. Let's install it via
    snap.
  * d/t/docker-in-lxd: set up lxd container storage using btrfs.
    Do not use privileged lxd container to run the test.
    Follow the official Ubuntu documentation:
    https://ubuntu.com/tutorials/how-to-run-docker-inside-lxd-containers

docker.io (20.10.21-0ubuntu1~22.10.1) kinetic; urgency=medium

  * Backport version 20.10.21-0ubuntu1 from Lunar (LP: #1996909).

 -- Lucas Kanashiro <email address hidden> Wed, 28 Feb 2023 11:32:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.4-0ubuntu1~22.04.1

---------------
runc (1.1.4-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport version 1.1.4-0ubuntu1 from Lunar (LP: #1996909).

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 12:17:32 -0300

[Launchpad Janitor (janitor)]

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

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

  * Backport version 1.6.12-0ubuntu1 from Lunar (LP: #1996909, #1996534).

 -- Lucas Kanashiro <email address hidden> Tue, 03 Jan 2023 17:58:41 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu1~22.04.2

---------------
docker.io (20.10.21-0ubuntu1~22.04.2) jammy; urgency=medium

  * d/tests: install lxd via snap in docker-in-lxd test.
    Since Jammy, lxd is not available as a .deb anymore. Let's install it via
    snap.

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

  * Backport version 20.10.21-0ubuntu1 from Lunar (LP: #1996909).

 -- Lucas Kanashiro <email address hidden> Wed, 15 Feb 2023 12:26:57 -0300

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for runc 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.4-0ubuntu1~20.04.1

---------------
runc (1.1.4-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport version 1.1.4-0ubuntu1 from Lunar (LP: #1996909).
    - d/control: b-d on golang-1.18-go instead of golang-any.
    - d/rules: build with Golang 1.18.

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 12:24:35 -0300

[Launchpad Janitor (janitor)]

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

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

  * Backport version 1.6.12-0ubuntu1 from Lunar (LP: #1996909, #1996534).
    - d/rules: set GO111MODULE to off.
    - d/control: b-d on golang-1.18-go instead of golang-go.
    - d/rules: build with Golang 1.18.
    - d/p/do-not-rebuild-manpage-during-installation.patch: avoid running go
      script during installation.

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 14:38:11 -0300

[Launchpad Janitor (janitor)]

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

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

  * Backport version 20.10.21-0ubuntu1 from Lunar (LP: #1996909).
    - d/control: b-d on golang-1.18-go instead of golang-go.
    - d/rules: build with Golang 1.18.
    - d/control: do not build docker.io in riscv64.

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 17:19:30 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package golang-github-fsouza-go-dockerclient - 1.6.0-2ubuntu0.20.04.2

---------------
golang-github-fsouza-go-dockerclient (1.6.0-2ubuntu0.20.04.2) focal; urgency=medium

  * Build with Golang 1.18 (LP: #1996909).
    - d/control: b-d on golang-1.18-go instead of golang-1.16-go.
    - d/rules: add Golang 1.18 to $PATH.

 -- Lucas Kanashiro <email address hidden> Fri, 27 Jan 2023 15:10:58 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package golang-github-openshift-imagebuilder - 1.1.0-2ubuntu0.20.04.2

---------------
golang-github-openshift-imagebuilder (1.1.0-2ubuntu0.20.04.2) focal; urgency=medium

  * Build with Golang 1.18 (LP: #1996909).
    - d/control: b-d on golang-1.18-go instead of golang-1.16-go.
    - d/rules: add Golang 1.18 to $PATH.

 -- Lucas Kanashiro <email address hidden> Fri, 27 Jan 2023 15:09:41 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.1.4-0ubuntu1~18.04.1

---------------
runc (1.1.4-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport version 1.1.4-0ubuntu1 from Lunar (LP: #1996909).
    - d/control: b-d on golang-1.18-go instead of golang-any.
    - d/rules: build with Golang 1.18.
    - d/rules: set GO111MODULE to off.
    - d/rules: set GOCACHE.

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 14:05:31 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 1.6.12-0ubuntu1~18.04.1

---------------
containerd (1.6.12-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport version 1.6.12-0ubuntu1 from Lunar (LP: #1996909, #1996534).
    - d/rules: set GO111MODULE to off.
    - d/control: b-d on golang-1.18-go instead of golang-go.
    - d/rules: build with Golang 1.18.
    - d/control: do not b-d on libbtrfs-dev, it is not available in Bionic.
    - d/p/do-not-rebuild-manpage-during-installation.patch: avoid running go
      script during installation.

 -- Lucas Kanashiro <email address hidden> Thu, 17 Nov 2022 15:43:46 -0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 20.10.21-0ubuntu1~18.04.2

---------------
docker.io (20.10.21-0ubuntu1~18.04.2) bionic; urgency=medium

  * d/t/basic-smoke: do not pass mirror url to debootstrap call, since, in
    Ubuntu, this url changes for non-amd64/non-i386 architectures. By not
    passing the url, we pick the default one, which will be correct for the
    architecture being tested.

docker.io (20.10.21-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport version 20.10.21-0ubuntu1 from Lunar (LP: #1996909).
    - Build with Go 1.18.
    - d/control: do not b-d on libbtrfs-dev, it is not available in Bionic.
    - d/control: do not build docker.io for riscv64, not supported in Bionic.
    - d/t/basic-smoke: debootstrap bionic instead of debian stable.

 -- Lucas Kanashiro <email address hidden> Mon, 30 Jan 2023 18:07:30 -0300