Upgrade alpine in node>=8 to 3.7

[michael-k]

No description provided.

[SimenB]

Breaking change, can only be done for new images. See #473 for discussion on alternatives.

@nodejs/docker feel free to reopen if you disagree

[michael-k]

Yes, it is a breaking change, but on the other hand, staying with an old alpine version is a security risk. Therefore both ways (staying with one version of alpine or bumping it) have their flaw and anybody using node in production have to build their own images.

At least for the generic alpine tag (not 9-alpine), I'd consider it ok to do breaking changes for alpine releases as well. It doesn't even guarantee any non-breaking changes for node.

I love that many images on docker hub addressed this by including alpine's version number in the image tag. The issue you references is half a year old and I found no work being done in this direction. :/ (Yes, I know, that's how it is with OSS and I can always do the work myself, if I care enough.)

[hulkish]

+1 Can somebody please explain why it's a breaking change for this to go to 3.7?

[michael-k]

@hulkish See the discussion in docker-library/golang#131 and the linked issues.

[SimenB]

Thanks for the link showing the potential breakage!

We would love to publish different versions though. PR very much welcome for making that happen