ci: bump packager base image from bullseye to bookworm - #1925
Merged
ShubhenduSinghF5 merged 3 commits intoSep 10, 2026
Conversation
Debian 11 (bullseye) reached LTS end-of-life on 2026-08-31. The bullseye-security suite is no longer being re-signed, so its InRelease file '"Valid-Until"' timestamp has expired. apt-get install now fails inside the CI packager image with: E: Release file for .../bullseye-security/InRelease is expired This breaks the "Build unsigned snapshot" and "Build signed snapshot" jobs on every PR against dev-v2. Bump the base image to golang:1.24-bookworm (Debian 12, currently the stable release with a fresh security suite). All apt packages used by the packager image (gpgv1, monkeysphere, aptly, debsig-verify, createrepo-c, dnf, rpm, and the lib*-dev family) are still available in bookworm. Signed-off-by: shusingh <shu.singh@f5.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev-v2 #1925 +/- ##
=========================================
Coverage ? 52.16%
=========================================
Files ? 51
Lines ? 3518
Branches ? 0
=========================================
Hits ? 1835
Misses ? 1538
Partials ? 145 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Debian bookworm dropped gnupg1, gpgv1 and monkeysphere (all GPG 1.x-era tooling). apt-get install fails on bookworm with: E: Package 'monkeysphere' has no installation candidate None of these three packages are actually invoked by any script, Makefile, or packaging helper in this repo (grep confirms zero references outside this Dockerfile). They were vestigial residue from an era when debsig-verify needed PGP v3 tooling; modern gpg 2.x (installed as the gnupg package, still present) handles everything the packager and debsig-verify need. Also drops a pre-existing duplicate "make" in the same apt-get line. Signed-off-by: shusingh <shu.singh@f5.com>
Debian bullseye reached LTS end-of-life on 2026-08-31 and the bullseye-security InRelease signature expired on 2026-09-08, causing apt-get update to fail in every debian:bullseye-slim CI job since. Debian bullseye is no longer a supportable target for nginx-agent v2.47+. Remove it from the integration test matrix in ci.yml and update the supported-OS table in Makefile accordingly. Customers still on bullseye should upgrade to bookworm; the packages built by the bookworm packager (bumped in the previous commit) remain compatible with bullseye runtimes that pull from unfrozen third-party repos.
karensantana
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Debian 11 (bullseye) reached its LTS end-of-life on 2026-08-31. The Debian LTS team has stopped re-signing the
bullseye-securitysuite, so itsInReleasefile'sValid-Until:timestamp is now expired.apt-get installinside the CI packager image fails hard as a result:This breaks the Build unsigned snapshot and Build signed snapshot jobs on every open PR against
dev-v2right now (not tied to any single PR — it's environmental drift).Fix
Bump the packager base image one release forward:
aptpackages the packager installs (gpgv1,monkeysphere,aptly,debsig-verify,createrepo-c,dnf,rpm, and thelib*-devfamily) are available in bookworm..deb/.rpm/.apkartifacts we ship to customers are unchanged (they are produced bynfpminside this container).Scope
scripts/packages/packager/Dockerfile(1 line)Test plan
CI on this PR will exercise the change end-to-end:
Build unsigned snapshot— must go green (this is the currently-red job).Locally I confirmed that
bookwormis the only bullseye reference in an active Dockerfile (test/docker/performance/Dockerfilehas a commented-out1~bullseyePKG_RELEASE line that is inert; the 500+ matches underpkgs*.nginx.*are published customer package filenames, unrelated to the build image).Risk
Very low. Base image bump on a builder-only container.
Related
Blocks every open PR that runs
build-unsigned-snapshot— including #1837 (nginx master process bug fix).