Base sandbox build broken: NodeSource yanked pinned Node.js 22.22.1 package
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- docker, github-actions, node.js
- Área
- build-system, ci-cd, devops
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Dockerfile
- Estrellas
- 191
- Forks
- 76
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NVIDIA/OpenShell-Community
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
opencode sandbox policy: npm child-process CONNECT denied (ECONNRESET) and no Vertex AI / WIF egress Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 74/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de NVIDIA/OpenShell-Community
Issues similares
-
core dependencies
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
-
bug github_actions
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
registrystack/registry-stack#1393 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Name consistency Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
eellak/triplestore#65 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100