Repository navigation
Install libatomic so Node can start - #7
Merged
Merged
Conversation
The official Node 26 Linux binaries are dynamically linked against libatomic.so.1, which the minimal Ubuntu base image does not ship. The image built fine but node could not start, so the break only surfaced downstream: browsertime's Docker build failed at npm install with exit code 127. sitespeed.io only worked because build-essential pulled libatomic1 in by accident. Running node at the end of the build makes a missing runtime library fail here, in the image that ships Node, instead of in the images built on top of it. Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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.
The official Node 26 Linux binaries are dynamically linked against libatomic.so.1, which the minimal Ubuntu base image does not ship. The image built fine but node could not start, so the break only surfaced downstream: browsertime's Docker build failed at npm install with exit code 127. sitespeed.io only worked because build-essential pulled libatomic1 in by accident.
Running node at the end of the build makes a missing runtime library fail here, in the image that ships Node, instead of in the images built on top of it.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com