fix(docker): resolve arm64 apk failures with deno alpine image#268
Merged
Conversation
c4664f2 to
af1475a
Compare
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.
Summary
denoland/deno:alpine-2.6.8shipping glibc-linkedlibcrypto.so.3in/usr/local/lib/apkcommands withLD_LIBRARY_PATH=/usr/libto use Alpine's musl-based system libraries insteadContext
The Deno Alpine Docker image bundles its own
libcrypto.so.3andlibgcc_s.so.1compiled against glibc, which conflicts with Alpine's musl libc on arm64. This causesapkto fail with "Error relocating" symbol errors (exit code 127).Known upstream issue: denoland/deno_docker#373
Test plan