Repository navigation
Conversation
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
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
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.
Problem
DockerfileandDockerfile.devbuild on Debian 11 (bullseye) base images. Bullseye's package pools have been archived off the primary Debian mirrors, soapt-get update && apt-get installnow fails with404 Not Foundfromdeb.debian.org: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-bookwormdebian:bullseye-slim→debian:bookworm-slimThere 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.muslis 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 gosuon the editedDockerfile→ 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