You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and later #3219
The "Production: SSR / Node.js server app" Dockerfile copies the resolved Node.js binary into debian:bookworm-slim. Official Linux builds link libatomic from Node.js 25 on (BUILDING.md, nodejs/node#60790), and the slim image doesn't include it, so with Node.js 26 the runtime stage fails to start:
node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
The "Smaller still" tip has the same gap: gcr.io/distroless/cc doesn't include libatomic1 either, while distroless's Node.js images do.
Your Suggestion for Changes
Install it in the runtime stage (apt-get install -y --no-install-recommends libatomic1), and in the tip either name distroless's Node.js image or mention the library.
I think it's important to make it clear that this is a temporary fix and that it will eventually be resolved (either through a Node.js hotfix or by fixing their build system), so we don't end up with this additional library installation step sticking around in all Dockerfiles for years to come.
Activity
Norbiros commentedon Oct 24, 2026
I think it's important to make it clear that this is a temporary fix and that it will eventually be resolved (either through a Node.js hotfix or by fixing their build system), so we don't end up with this additional library installation step sticking around in all Dockerfiles for years to come.