pin wolfi glibc and related packages to workaround broke APKINDEXes #10645
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
ae13f8d to
7863cad
Compare
For some reason Wolfi has been occasionally publishing APKINDEX files where the latest version of ld-linux specifies a hard dependency on an exact version of glibc which is not present in the APKINDEX yet. It goes away within an hour usually, but it's frustrating in the meantime to not be able to build the engine obviously. For now, attempting to resolve this by just specifying glibc, ld-linux and libcrypt1 versions that are one minor version ago. I repro'd the problem by manually constructing an APKINDEX with the missing glibc version (got the exact same error we see) and verified this approach fixed it. We will see if it works in the real world too. Signed-off-by: Erik Sipsma <erik@sipsma.dev>
vito
approved these changes
Jun 25, 2025
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.
For some reason Wolfi has been occasionally publishing APKINDEX files where the latest version of ld-linux specifies a hard dependency on an exact version of glibc which is not present in the APKINDEX yet. It goes away within an hour usually, but it's frustrating in the meantime to not be able to build the engine obviously.
For now, attempting to resolve this by just specifying glibc, ld-linux and libcrypt1 versions that are pinned to the current epoch. I repro'd the problem by manually constructing an APKINDEX with the missing glibc version (got the exact same error we see) and verified this approach fixed it. We will see if it works in the real world too.