build: use official musl builds for 24+

[nschonni]

Description

Opening as a draft, as this is just a paper test right now.

Motivation and Context

There is still some work going on with v22 in the build repo, so this is a "step 1" to start using the official builds for musl for the newer releases.
Copied the setup from the Debian template for the steps grab and verify the artifcats. The fallback build is left for the ARM architecture and some old ones still included as part of v22.

Testing Details

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[MikeMcC399]

As you commented in #2550 (comment), Node.js is now building x64-musl for every currently supported release line and promoting each of them to the official download site https://nodejs.org/download/release.

The PR nodejs/node#63737 to document this officially as Tier 2 supported is however still pending.

Are you going to continue to work on this PR or a follow-on PR to pick up the official x64-musl builds instead of the unofficial builds? That would be great! I did take a look at doing this before you opened this PR, but it doesn't make sense to have us both working on the same thing.

[nschonni]

@MikeMcC399 feel free if you want to take a cut at this. You don't even need to use anything from this PR. I'll try and get back to it, but I haven't come back to this since I opened the draft

[MikeMcC399]

I'll take a look again next week. It was mid August when I looked at a possible solution previously so I've already lost my train of thought, and I'll need to refresh my memory before continuing 🙂 !

I haven't compared your proposal with mine at this stage, but I did also address documentation, not just the scripts.

[nschonni]

@MikeMcC399 I kind of got it working, but I think the v26 issue might be a real runtime thing. I believe it might have been fixed in the unofficial at some point

[MikeMcC399]

@nschonni

I kind of got it working, but I think the v26 issue might be a real runtime thing. I believe it might have been fixed in the unofficial at some point

Node.js official builds starting with Node.js 25.0.0 are built with gcc-toolset-14-libatomic-devel. See https://github.com/nodejs/node/blob/v26.x/BUILDING.md#official-binary-platforms-and-toolchains

This is a difference compared to the unofficial musl builds. There is an additional prerequisite libatomic necessary when migrating to use Node.js 26 official musl builds.

It needs apk add libatomic added. This will also be needed in the documentation examples.

The prerequisites for Node.js 26 Alpine x64 are then:

apk add libatomic libstdc++ libgcc

[MikeMcC399]

Needs libatomic

[MikeMcC399]

Suggested change

	libstdc++ \
	libatomic libstdc++ \

This needs adding to the generated Dockerfiles as well.

[nschonni]

If you want to push any changes and re-run update.sh feel free

[nschonni]

I'd probably put this on it's own line like the other apk add calls though

[MikeMcC399]

I'd prefer to leave the changes to you for simplicity's sake. It would be nice to get this finished before Node.js 27 comes along, but otherwise there's no great urgency.

[MikeMcC399]

Would you check the PR title and description? The PR is now covering 22, 24 & 26 whereas the title refers to 24+.