Skip to content

ci: fix Docker builds by bumping Debian bullseye base images to bookworm - #2335

Open
sivukhin wants to merge 1 commit into
mainfrom
ci/docker-bullseye-to-bookworm
Open

sivukhin wants to merge 1 commit into
mainfrom
ci/docker-bullseye-to-bookworm

Conversation

@sivukhin

Copy link
Copy Markdown
Contributor

Problem

Dockerfile and Dockerfile.dev build on Debian 11 (bullseye) base images. Bullseye's package pools have been archived off the primary Debian mirrors, so apt-get update && apt-get install now fails with 404 Not Found from deb.debian.org:

E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/c/ca-certificates/...  404  Not Found
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/w/wget/...             404  Not Found
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/g/gnupg2/...           404  Not Found
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/o/openssl/...          404  Not Found
E: Failed to fetch http://deb.debian.org/debian-security/pool/updates/main/s/sqlite3/...          404  Not Found

This breaks the gosu install stage and the builder/runtime stages. It is pre-existing infrastructure bitrot, not a code regression.

Fix

Bump the base images from Debian 11 (bullseye) to Debian 12 (bookworm) in both Dockerfiles. The builder and runtime stages are bumped together so the glibc version stays consistent across stages:

  • rust:slim-bullseye → rust:slim-bookworm
  • debian:bullseye-slim → debian:bookworm-slim

There are no bullseye-specific pinned package versions in either file, so no other changes are needed. The change is scoped strictly to the base-image bump. Dockerfile.musl is unaffected (non-Debian base) and left untouched.

Files changed

  • Dockerfile — chef/builder, gosu, and runtime stages (3 lines)
  • Dockerfile.dev — builder, gosu, and runtime stages (3 lines)

Verification

Reproduced the failure and confirmed the fix locally (arm64):

  • debian:bullseye-slim + apt-get install ca-certificates gnupg wget → 404 Not Found (reproduced).
  • debian:bookworm-slim + same install → exit 0.
  • rust:slim-bookworm + the full builder dependency set (libclang-dev clang build-essential tcl protobuf-compiler file libssl-dev pkg-config git cmake) → exit 0.
  • docker build --target gosu on the edited Dockerfile → succeeds end-to-end (apt install, gosu download, GPG signature verification, gosu --version, gosu nobody true).

The full multi-hour Rust compile was not run locally; CI is the real gate for the complete image build.

🤖 Generated with Claude Code

The Dockerfiles use Debian 11 (bullseye) base images, whose package
pools have been archived off the primary Debian mirrors. As a result,
`apt-get update && apt-get install` now fails with `404 Not Found` from
deb.debian.org (e.g. ca-certificates, gnupg, wget, openssl, sqlite3),
breaking the Docker image builds. This is pre-existing infrastructure
bitrot, not a code regression.

Bump the base images to Debian 12 (bookworm) in both Dockerfiles,
updating the builder and runtime stages together so the glibc version
stays consistent across stages:

- rust:slim-bullseye  -> rust:slim-bookworm
- debian:bullseye-slim -> debian:bookworm-slim

Dockerfile.musl is unaffected (it uses a non-Debian base) and is left
unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant