Related tasks for Alpine (musl) x64 promotion to Tier 2
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Dockerfile
- Estrellas
- 8.6k
- Forks
- 2k
- Merge medio
- 10 h 19 min
- PR fusionados (30 d)
- 16
Descripción
Current status
Platform list currently contains the following entry:
| Operating System | Architectures | Versions | Support Type | Notes |
|---|---|---|---|---|
| GNU/Linux | x64 | kernel >= 3.10, musl >= 1.1.19 | Experimental | e.g. Alpine 3.8 |
Other architectures are unlisted, and have no designated support type.
Official binary platforms and toolchains does not list any Alpine / musl build.
node Docker images for Alpine are built from https://unofficial-builds.nodejs.org/download/release/v<node-version>/node-v<node-version>-linux-x64-musl.tar.xz
- Alpine
x64images are built using thex64-muslbuild directly - Alpine
arm64,arm32ands390ximages are built from source
Update automation treats security releases differently and proceeds with these releases without waiting for musl build availability.
Proposed Node.js change
PR https://github.com/nodejs/node/pull/63737 proposes the promotion of Alpine/x64 to Tier 2.
This can be expected to add Alpine/x64 to the Platform list and to Official binary platforms and toolchains.
An x64-musl build can be expected to be available through the regular https://nodejs.org/download/release/ website.
Impact
Expected update tasks and impact will include:
- Documentation README references to support category and process
- Dockerfile-alpine.template to source the musl build from https://nodejs.org/download/release/
- update.sh script so that the
-s(security) option does not exclude Alpine builds, or for more simplification, remove the-soption entirely, since it becomes a no-op - build-automation.mjs remove checks against https://unofficial-builds.nodejs.org
Review other Alpine-related issues and PR for relevance and applicability.
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.
Línea de trabajo
Empieza por README, Dockerfile-alpine.template, update.sh y build-automation.mjs; después, revisa la promoción enlazada de Node.js y los demás issues de Alpine. Actualiza el proceso de soporte documentado, utiliza la fuente habitual de releases de Node.js para Alpine x64 y elimina las comprobaciones obsoletas de unofficial-builds y el manejo de las security releases cuando la promoción a Tier 2 esté implementada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- docker, dockerfile, nodejs
- Área
- build-system, devops, documentation
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 55/100