Build on bookworm, since bullseye's security metadata has expired - #681
Merged
Conversation
Bullseye is end of life and its InRelease file lapsed two days ago, so apt-get update fails and no image can be built at all.
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
1 participant
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.
Short Description
Builds on Debian bookworm instead of bullseye, so an image can be built at all.
Implementation Details
Bullseye is end of life and its security
InReleasefile expired two days ago.apt-get updatetreats that as fatal, soDockerfile:14fails and no Apollo image builds. That is what broke the 3.2.0 image build, and it will break every build until this changes.I reproduced it in isolation and confirmed the fix the same way:
The full image then builds on
linux/amd64, the platform CI uses, and runs: Python 3.11.16, Node 20.20.2, Poetry 2.4.3, Bun 1.3.14, docs clone present. Nothing else in the repo referenced bullseye.No changeset, because this is folded into the existing 3.2.0 tag rather than released separately.
AI Usage
You can read more details in our Responsible AI Policy