Repository navigation
fix: move base images to distroless cc-debian13 - #59
Open
ravisingal wants to merge 1 commit into
Open
ravisingal wants to merge 1 commit into
ravisingal wants to merge 1 commit into
Conversation
Debian 12 (bookworm) is approaching the end of its full-support window, so move the runtime base for both Java images to gcr.io/distroless/cc-debian13. The helper stages move to trixie alongside it so the JRE and jemalloc are built against the same glibc (2.41) as the runtime base, and the SSL stage moves to java-base-debian13 so the Java cacerts come from a matching release. cc-debian13 already ships zlib (libz.so.1 -> libz.so.1.3.1), unlike cc-debian12, so copying libz in from the build stage is no longer needed. Replace it with an assertion that the base still provides the library, left unversioned so a routine zlib patch bump does not break the weekly update-docker-args PR. Verified by building both images on amd64 and arm64: java 11.0.33 and 21.0.13 start, jemalloc preloads, cacerts are present, and the eMudhra blocked.certs entry survives jlink. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ravisingal
requested review from
JBAhire,
aaron-steinfeld and
kotharironak
as code owners
October 25, 2026 11:09
Contributor
Author
|
Root CA certificate |
hibohra1398
approved these changes
Oct 25, 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
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.
Why
Debian 12 (bookworm) is approaching the end of its full-support window. This moves the runtime base for both Java images to
gcr.io/distroless/cc-debian13.Changes
java-11/base.image,java-21/base.image— point atgcr.io/distroless/cc-debian13:debugat the current digest.update-docker-args.yml— the weekly digest-bump workflow now trackscc-debian13, so it won't revert the migration.jreandbuilderstages →debian:trixie-slim, so the JRE and jemalloc are built against the same glibc (2.41) as the runtime base.sslstage →gcr.io/distroless/java-base-debian13:debug, so the Javacacertscome from a matching release.cc-debian13already shipslibz.so.1 -> libz.so.1.3.1, unlikecc-debian12. Copyinglibzin from the build stage is no longer needed (and would now fail: the oldln -scollides with the base's own symlink). It's replaced by an assertion that the base still provides the library, left unversioned so a routine zlib patch bump doesn't break the weekly digest PR.java-11/Dockerfile—As builder→AS builder, clearing theFromAsCasingbuild warning.Testing
Both images built locally on amd64 and arm64:
java -versionLD_PRELOAD/etc/ssl/certs/java/cacertsblocked.certsThe zlib assertion was also checked against a deliberately bad path to confirm it fails the build rather than passing silently.
Remaining build warnings are pre-existing
InvalidDefaultArgInFromnotices forARG BASE_IMAGE, which both CI workflows always supply.🤖 Generated with Claude Code