Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up"npm i" crashes with exit code 134 on ARM64 #1254
Comments
|
Here's the documentation on how to do this: https://github.com/nodejs/docker-node/blob/master/docs/BestPractices.md#node-gyp-alpine |
|
@LaurentGoderre Thanks, I might try this as a workaround. However, this doesn't change the fact, that the ARM64 image simply doesn't work |
|
I too am using arm64 based Ubuntu 20.04, and ran into the same issue as @SuNNjek. I've found its specifically the stretch (and slim variant) containers that are producing this. It works with buster (and slim variant), so that's an easier workaround than using alpine! |
|
I have the same issue on a raspberry pi 4 running ubuntu server 20.04. Every yarn or npm command in a container immediately returns I tried stretch packages from node 10 - 14, all with the same error. Buster package works. |
|
I think my issue is related to this. node --version works, but trying to execute index.js file does not and results in Aborted (core dumped). Container image: node:14.4 gdb:
bt full trace via gdb:
|
|
I solved my problem specifying node and npm version "engines": {
"node": "12.1.0",
"npm": "6.9.0"
} |
Hello,
I'm trying to build a simple web app via Docker using the
node:12(also triednode:14, no luck) image on my Raspberry Pi 4 running Ubuntu 20.04. When the build process wants to executenpm iI just get the error:Even when I go into a new interactive container and execute
npm(no arguments) myself I get the same error.For some reason, the
node:14-alpineimage worked, but since my app requires native dependencies that I need to recompile and the image doesn't come with the right build tools I can't use that.