Automated Security Builds with Overlapping (Multiple) LTS Release Tracks

[tpo]

Ubuntu have updated their docker images yesterday:

• https://hub.docker.com/_/ubuntu/tags?name=jammy
• https://hub.docker.com/_/ubuntu/tags?name=noble

It would be nice if you could trigger a rebuild of your docker images to be based on those updated upstream Ubuntu docker images.

One of the advantages for your downstreams would be that when keeping up with security updates of packages in containers the number of packages that need to get pulled on each build due to package security updates would shrink significantly.

Heartfelt thanks to all of you!
*t

[Theaxiom]

noble build is currently running @tpo

[Theaxiom]

The CI process is not currently setup to maintain 2 separate tracks, perhaps this could be an area for improvement.

[tpo]

The CI process is not currently setup to maintain 2 separate tracks, perhaps this could be an area for improvement.

I'm guessing that what you are referring to here is that the CI process is currently only able to build new images against a single upstream distro release, as has just been done for Ubuntu 24.04/noble, however the phusion container images based on Ubuntu 22.04/jammy have not been updated (as of now).

[Theaxiom]

The CI process is not currently setup to maintain 2 separate tracks, perhaps this could be an area for improvement.

I'm guessing that what you are referring to here is that the CI process is currently only able to build new images against a single upstream distro release, as has just been done for Ubuntu 24.04/noble, however the phusion container images based on Ubuntu 22.04/jammy have not been updated (as of now).

That is indeed correct.