arm64v8/ghost (both debian as alpine) not beeing build

[h3rj4n]

There are currently only old images available for arm based devices. Jenkins fails for some reason.

I'm trying to build the images local. It seems there is an old bug that causes the builds to fail:

• Error: could not get uid/gid npm/uid-number#3

I've added npm config set unsafe-perm true as solution to the docker file and now it's being build. Is it possible to add this solution to the docker files?

[yosifkit]

The reason for the build failures on the Debian images is that Debian Jessie (which all the Debian-based node images still use) no longer supports arm64v8 and many other arches since it transitioned to LTS (docker-library/official-images#4593, https://wiki.debian.org/LTS/, and nodejs/docker-node#863). So there is nothing we can do to bring these back until node moves their images to Debian Stretch.

As for the Alpine based builds, it seems weird that unsafe-perm is required at all since the arm32v6 builds for Alpine work fine. 😕

There are up-to-date arm32v7 builds for the Debian images.

[axeII]

Thanks @h3rj4n for this quick fix. 🙃

[tianon]

Looks like this npm bug is now filed at https://npm.community/t/old-closed-issue-from-npm-uid-number-error-could-not-get-uid-gid/2697? (Having trouble determining exactly where npm bugs ought to be filed given the archiving of https://github.com/npm/npm and the no-issues on https://github.com/npm/cli.)

Given that this works fine on other architectures (including arm32v7 and arm32v6), I'm inclined to believe this really is just an npm bug, and that we ought to wait for them to provide an appropriate fix for it instead of enabling a hacky workaround just for arm64v8 (the most puzzling part of all being that arm64v8 seems to be the only architecture affected, which simply doesn't make sense given the bug linked above).

[tianon]

I did some digging in the image. I added a bunch of debug statements to /usr/local/lib/node_modules/npm/node_modules/uid-number/get-uid-gid.js, and it segfaults while invoking process.setgid(group) (https://github.com/npm/uid-number/blob/6e9bdb302ae4799d05abf12e922ccdb4bd9ea023/get-uid-gid.js#L19).

This is looking like it's potentially related to npm/uid-number#6.

[tianon]

Aha, nodejs/docker-node#813 describes these symptoms, especially nodejs/docker-node#813 (comment).

This is failing on s390x as well, but not on ppc64le or arm32v6 which is extra bizarre.

The trivial reproducer is to simply run node /usr/local/lib/node_modules/npm/node_modules/uid-number/get-uid-gid.js, which should output [ 0, 0 ] (debugging output), then segfault on affected platforms.

[tianon]

(If it succeeds, like it does on my local amd64 box, it should output {"uid":0,"gid":0})

[pascalandy]

In my Travis builds, ARM builds are working normally using Node V8 and V10.
EDIT: here is my conclusion #163 (comment)

[axeII]

Can this image for amr64v8 get also updated https://hub.docker.com/r/arm64v8/ghost/ 🙏

[tianon]

Builds are still failing with this same error weird UID-related error (just as described in nodejs/docker-node#813): https://doi-janky.infosiftr.net/job/multiarch/job/arm64v8/job/ghost/