fix(docker): pin libatomic1 for arm64 pnpm builds - #29
Merged
Merged
Conversation
pnpm's standalone binary (@pnpm/exe) requires libatomic.so.1 on arm64, which node:*-slim doesn't install by default. Production builds started failing with "error while loading shared libraries: libatomic.so.1". Pin the package explicitly instead of depending on it being present by luck/layer-cache inheritance.
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.
Hotfix
Production Docker builds on arm64 were failing at
pnpm install --frozen-lockfilewith
libatomic.so.1: cannot open shared object file. pnpm's standalone binaryneeds
libatomic1, which isn't installed by default onnode:*-slim.Pins
libatomic1explicitly in the build stage beforenpm i -g pnpm.Not a version release — package.json version stays at 1.3.0.