Docker-node: Alpine 3.13 support

[nschonni]

Problem

There is a new release line for Alpine out now https://github.com/docker-library/official-images/pull/9424

Solution

Decide what versions should the image be new image version be added to

Alternatives to Consider

Wait till the next major Node 16 before introducing it

[SimenB]

I think we should introduce it now, but not as default for anything. Then make it the default for 16

[nschonni]

I'm thinking only for 14 & 15 if we add it, since those are the only "Active" releases, and 10 and 12 are in in "Maintenance" https://github.com/nodejs/Release

Should probably document some sort of support policy for the versions under https://github.com/nodejs/docker-node#nodealpine

[yetithefoot]

Would be possible to add node12:alpine3.13 as well?

[nschonni]

@nodejs/docker I'm going to land https://github.com/nodejs/docker-node/pull/1426 to add support to v14 and v15 if I don't hear any objects by Friday

[DaKaZ]

Would you be open to a PR for v12 as well? I am currently using it with a custom build based off of your Alpine 3.12 Node 12 version and would rather just use the "official" ones from Dockerhub. Happy to contribute but only if its actually wanted

[nschonni]

Personally I don't think it should be add to v12 as mentioned above, because that version is in maintenance now. Maybe some of the other maintainers might disagree.

[hairyhenderson]

I'd be interested in this being backported to v12 as well - it may be "Maintenance LTS" but it's still "LTS" until April 2022 😉

[nschonni]

https://github.com/nodejs/Release is more around Node features, but I think it applies to OSes as well

Maintenance - Critical bug fixes and security updates. New features may be added at the discretion of the LTS team - typically only in cases where the new feature supports migration to later release lines.

It still hasn't been documented in the README, but I think that's the same reason v10 didn't get 3.12

[hairyhenderson]

Ok, fair enough. My reasons for wanting an Alpine v3.13-based image were based on a CVE that was present in the 3.12-based one, but it appears that's since been solved (at least, neither Snyk or Trivy find it now), so this is not a big deal 😉

[DaKaZ]

I did submit a PR for v12 #1439