IBX-12474: Moved Varnish image to Debian 12 (bookworm) - #67
Closed
KamilSznajdrowicz wants to merge 1 commit into
Closed
IBX-12474: Moved Varnish image to Debian 12 (bookworm)#67KamilSznajdrowicz wants to merge 1 commit into
KamilSznajdrowicz wants to merge 1 commit into
Conversation
Debian 11 (bullseye) reached end of LTS on 2026-08-31, and its archive is
now being decommissioned. `deb.debian.org` and `security.debian.org` still
publish the bullseye package indexes, but individual `.deb` files are already
disappearing from the pools, so `apt-get install` fails with a 404 mid-build:
E: Failed to fetch .../g/gnupg2/gpgsm_2.2.27-2+deb11u3_amd64.deb 404 Not Found
E: Failed to fetch .../g/gnupg2/gnupg_2.2.27-2+deb11u3_all.deb 404 Not Found
Unable to install GPG! ... Repository installation aborted.
This breaks the `varnish` leg of Browser tests in every product repository
that uses `doc/docker/varnish.yml`. The 404s come and go depending on which
Fastly node the runner hits, so re-running the job is a lottery rather than
a fix.
Varnish 6.0 LTS is unchanged - `varnish`/`varnish-dev` 6.0.12 are published
for bookworm as well, so only the base OS moves here.
Verified locally (`docker build --platform linux/amd64`):
- the packagecloud script installs GPG and the Varnish repo without 404s
- all build dependencies resolve on bookworm
- `varnish-modules` 0.15.0 still compiles, `libvmod_xkey.so` is installed
- resulting image reports Debian 12 with `varnish 6.0.12-1~bookworm`
The same change is needed on 5.0 and 6.0, where the file is identical.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
10 tasks
KamilSznajdrowicz
changed the title
Contributor
Author
|
Closed due to a similar solution already being implemented here: #68 |
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
1 participant
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.
Related PRs:
Description:
Debian 11 (bullseye) reached end of LTS on 2026-08-31 and its archive is being decommissioned. The package indexes are still published, but individual
.debfiles are already vanishing from the pools, so the Varnish image build dies mid-apt-get:That turns the
varnishleg of Browser tests red in every product repository usingdoc/docker/varnish.yml(e.g. ibexa/commerce#1990). The 404s come and go depending on which Fastly node the runner hits, so re-running a job is a lottery rather than a fix.What it changes
docker/Dockerfile-varnish, three lines:debian:bullseye-slim→debian:bookworm-slimvarnish=6.0.12-1~bullseye→~bookwormvarnish-dev=6.0.12-1~bullseye→~bookwormRuntime (entrypoint,
parameters.vcl, real VCL fromibexa/http-cache) is not covered by that local build — CI'svarnishleg is the actual check.For QA:
Nothing to verify manually - this is a build-infrastructure fix. The only meaningful check is a green
varnishleg of Browser tests in a product repository once this reaches4.6and is merged up (e.g. ibexa/commerce#1990); that leg exercises Varnish andxkey-based cache invalidation end to end. Note thatdocker/Dockerfile-varnishis not built by this repository's CI, and the redbuild-and-publishchecks here are pre-existing on4.6- the same bullseye 404s in the PHP images that #68 addresses.Documentation:
No documentation required.
🤖 Generated with Claude Code