Update Docker builder to Debian Bookworm - #9984
Merged
mergify[bot] merged 3 commits intoSep 7, 2026
Merged
Conversation
Keep Rust at 1.88.0 while moving the builder off Bullseye to avoid the failing Debian security package downloads. Update the Ubuntu runtime to 24.04 so its glibc is newer than the builder's.
michaelsproul
added
work-in-progress
Member
Author
|
This might technically be backwards incompat, if anyone is relying on the specific version of Ubuntu we use in the runner image. |
Member
Author
|
Docker builds are still failing, I think we need this. |
`lcli/Dockerfile` carries the same bullseye pin as the main `Dockerfile`, so it breaks the same way now that Debian 11 has reached LTS EOL. Apply the identical fix: bookworm builder, and Ubuntu 24.04 runtime so its glibc is newer than the builder's. Not built by CI (`docker.yml` uses `lcli/Dockerfile.cross`), but broken for local builds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qny4QevtjCbyAyAB7rT7M7
|
Queued — the merge queue status continues in this comment ↓. |
The reproducible build path still pins `rust:1.88-bullseye` by digest in three places, and pins exact bullseye package versions. Debian 11 reached LTS EOL on 2026-08-31, so `apt-get update` in this image fails once the `bullseye-security` Release file expires. Bump the per-arch digests to the current `rust:1.88-bookworm` and repin the build dependencies to their bookworm versions. Rust stays at 1.88. Verified both pinned images install the pinned packages cleanly: amd64 Debian 12, rustc 1.88.0, cmake 3.25.1, glibc 2.36 arm64 Debian 12, rustc 1.88.0, cmake 3.25.1, glibc 2.36 This also aligns the builder with the `distroless/cc-debian12` runtime, which previously ran a bullseye-built binary against a bookworm userland. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qny4QevtjCbyAyAB7rT7M7
dapplion
added
ready-for-merge
Merge Queue Status
This pull request spent 25 minutes 30 seconds in the queue, including 22 minutes 32 seconds running CI. Waiting for
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks
HintYou may have to fix your CI before adding the pull request to the queue again. Requeued — the merge queue status continues in this comment ↓. |
8 tasks
Collaborator
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 29 minutes 29 seconds in the queue, including 28 minutes 5 seconds running CI. Required conditions to merge
|
8 tasks
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.
Issue Addressed
Fix failing CI observed here:
Proposed Changes
Keep Rust at 1.88.0 while moving the builder off Bullseye to avoid the failing Debian security package downloads. Update the Ubuntu runtime to 24.04 so its glibc is newer than the builder's.