Bugfix/research memory issues downstream #35
Merged
Conversation
This file contains 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
…th the newer bookworm release
… with the newer lts release
… with the newer lts release
|
Found a discussion under redis' and python's base Docker image upgrades from bullseye to bookworm. This appears to be the same behavior that I've seen on our downstream automated builds. Not seeing this behavior anywhere else (locally, GitHub Action builds, etc), so this cc @jvanceACX |
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.
The downstream issues seem to be related to the main jenkins/jenkins:lts upgrading from Bullseye to Bookworm. For now going to pin Jankins to the last Bullseye release. Longer term if this project isn't archived I'm thinking we pivot over to RHEL UBI based builds.
cc @jvanceACX
For more details: