Base sandbox build broken: NodeSource yanked pinned Node.js 22.22.1 package
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 68/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Ruhig
- Tech-Stack
- docker, github-actions, node.js
- Bereich
- build-system, ci-cd, devops
Rechercherichtung
Start with sandboxes/base/Dockerfile at line 61 and the Build Sandbox Images workflow, then reproduce the failed build to confirm the unavailable NodeSource pin. Compare the proposed installation approaches and verify that the chosen approach builds the base sandbox image successfully without depending on the missing package version.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
The Build Sandbox Images workflow is failing because NodeSource removed nodejs=22.22.1-1nodesource1 from their apt repository. The base sandbox Dockerfile pins this exact version at line 61, causing the Docker build to fail with:
E: Version '22.22.1-1nodesource1' for 'nodejs' was not found
Failed run: https://github.com/NVIDIA/OpenShell-Community/actions/runs/23721670468
Root Cause
NodeSource has a recurring issue where they publish patch releases to their apt repo and then remove them shortly after, keeping only the .0 release. This is documented in multiple upstream issues:
- nodesource/distributions#1931 — opened Mar 28, 2026, reports
22.22.1,22.22.2,20.20.1,20.20.2,24.14.1all missing - nodesource/distributions#1897 — same pattern observed with
22.21.1back in Nov 2025
The version 22.22.1-1nodesource1 was available when the pin was introduced in commit d5073c3 (Mar 12) and built successfully as recently as Mar 24 (run 23503799247). NodeSource yanked it between Mar 24–28.
The highest version currently available in the NodeSource repo is 22.22.0-1nodesource1.
Suggested Fix
Pinning to NodeSource apt packages is unreliable since they remove versions without notice. Consider one of:
- Install from official Node.js tarballs — download pre-built binaries directly from
https://nodejs.org/dist/which are never removed. This is the most robust option. - Pin to the latest available NodeSource version (
22.22.0-1nodesource1) as a short-term fix, accepting it will likely break again on the next patch release cycle. - Remove the version pin and just install
nodejswithout a version suffix, trading reproducibility for resilience.
Option 1 is recommended since it avoids this class of problem entirely.
- Vorherrschende Sprache
- Dockerfile
- Sterne
- 191
- Forks
- 76
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus NVIDIA/OpenShell-Community
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
-
opencode sandbox policy: npm child-process CONNECT denied (ECONNRESET) and no Vertex AI / WIF egress Offen
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 74/100
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
Alle Issues in NVIDIA/OpenShell-Community
Ähnliche Issues
-
core dependencies
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 80/100
-
bug github_actions
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
registrystack/registry-stack#1393 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
-
Name consistency Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
eellak/triplestore#65 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100