nodejs / nodejs/node

Node should run on Debian/Ubuntu-based images without having to manually install libatomic first

Offen
#60,790 13 Kommentare 18 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

feature request v26.x
Vorherrschende Sprache
JavaScript
Sterne
122k
Forks
37.3k
Ø Merge
4 T. 2 Std.
Gemergte PRs (30 T.)
283

Beschreibung

What is the problem this feature will solve?
Summary

Node 25.0.0 requires the libatomic library, it's in the docs since 25.2.0.

I've tried some current official Ubuntu images (24.04, 25.10, 26.04) and Debian images (12.12, 13.12) and none comes with libatomic installed.

Consequently installing node on Debian or Ubuntu will work, but running any commands will fail.

Why should this be supported

I assume that having a seamless installation experience, at least on major linux distros, is something Node would like to provide. I'm thinking a) install nvm, b) install node via nvm, c) done, you can use node now.

This is also how, for example, the npm docs tell you to install npm. And it no longer works on Debian or Ubuntu based images unless you also install "libatomic".

Debian and Ubuntu are two of the major linux distros. Many projects are using one of their images as the basis for their official docker images. For example, the official Jenkins image is debian based and the latest version (jenkins/jenkins:2.538-jdk21) can not run node 25+, unless you first install "libatomic" into the container that is.

What is the feature you are proposing to solve the problem?

I am not familiar enough with linux or node to tell whether or not node could include libatomic. But if that was possible and practical then that would allow debian and ubuntu based images to run node again without having to install libatomic first.

What alternatives have you considered?
  1. nvm could plausibly install libatomic, that said, over at nvm the sentiment was that Node was the place to address this.
  2. debian / ubuntu could plausibly include libatomic in their images
  3. all projects that provide debian / ubuntu based images and imagine their image could be used to run node could plausibly provide libatomic
  4. the end user that wants to run node in any debian / ubuntu based image could plausibly install libatomic

Out of these I've only really considered 1 and 4 real possibilities, though with the folks at nvm saying it's not their job it's either on Node itself or the end user, probably.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit den offiziellen Hinweisen zu Binärplattform und Toolchain in BUILDING.md und reproduziere anschließend Node 25+ in den aufgeführten Debian- und Ubuntu-Images. Ermittle, ob die Node-Distribution die fehlende libatomic-Abhängigkeit beheben kann, und validiere, dass Node-Befehle ausgeführt werden, ohne sie manuell zu installieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
debian, javascript, linux, node.js, ubuntu
Bereich
devops, operating-systems
Issue-Typ
Bug
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.