Base sandbox build broken: NodeSource yanked pinned Node.js 22.22.1 package
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 68/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Calme
- Stack technique
- docker, github-actions, node.js
- Domaine
- build-system, ci-cd, devops
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- Dockerfile
- Étoiles
- 191
- Forks
- 76
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de NVIDIA/OpenShell-Community
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
-
opencode sandbox policy: npm child-process CONNECT denied (ECONNRESET) and no Vertex AI / WIF egress Ouverte
Difficulté 3/5 1-2 jours Accessibilité débutants 74/100
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
-
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
Toutes les issues de NVIDIA/OpenShell-Community
Issues similaires
-
core dependencies
Difficulté 1/5 Moins d'une heure Accessibilité débutants 80/100
-
bug github_actions
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
registrystack/registry-stack#1393 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
-
Name consistency Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
eellak/triplestore#65 · 1 commentaire ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100