[SPARK-56818][DOCS] Fix Binder build by pinning Debian Bookworm base …#55818
Open
stan-buren wants to merge 1 commit into
Open
[SPARK-56818][DOCS] Fix Binder build by pinning Debian Bookworm base …#55818stan-buren wants to merge 1 commit into
stan-buren wants to merge 1 commit into
Conversation
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.
What changes were proposed in this pull request?
This PR pins the base image in
binder/Dockerfiletopython:3.10-slim-bookworm.Why are the changes needed?
The floating tag
python:3.10-slimrecently migrated from Debian 12 (Bookworm) to Debian 13 (Trixie). Theopenjdk-17-jrepackage is no longer available in the Trixie repositories, causing the Binder build for interactive documentation (Quickstart notebooks) to fail withE: Package 'openjdk-17-jre' has no installation candidate.Pinning the image to
bookwormrestores the build stability.Resolves Jira issue: SPARK-56818
Does this PR introduce any user-facing change?
No. This only affects the Binder documentation build infrastructure.
How was this patch tested?
Verified locally by building the Docker image successfully with the
bookwormtag. Theapt-get installstep now completes without errors.Was this patch authored or co-authored using generative AI tooling?
No.