Related tasks for Alpine (musl) x64 promotion to Tier 2
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Dockerfile
- Sterne
- 8.6k
- Forks
- 2k
- Ø Merge
- 10 Std. 19 Min.
- Gemergte PRs (30 T.)
- 16
Beschreibung
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.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit README, Dockerfile-alpine.template, update.sh und build-automation.mjs und überprüfe anschließend die verlinkte Node.js-Promotion sowie die anderen Alpine-Issues. Aktualisiere den dokumentierten Supportprozess, verwende die reguläre Node.js-Release-Quelle für Alpine x64 und entferne die veralteten unofficial-builds-Prüfungen sowie die Behandlung von Security-Releases, sobald die Tier-2-Promotion eingerichtet ist.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- docker, dockerfile, nodejs
- Bereich
- build-system, devops, documentation
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 55/100