-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm doesn't run in 19.3.0-alpine3.17 container #1829
Comments
Sounds like a duplicate of #1798 to me: I was able to reproduce the same behavior, i.e. running Node v19 in an armv7 Alpine container hangs indefinitely. |
I'm having the same issue. |
The same for Node v20 images. |
2 tasks
ismarslomic
added a commit
to ismarslomic/skistar-activities-ical
that referenced
this issue
Nov 13, 2023
It is known issue that `npm install` is stuck when building on platforms arm/v6 and arm/v7 of Docker images Node v19 and Node v20. See nodejs/docker-node#1829 and nodejs/docker-node#1798
jaymoulin
added a commit
to femtopixel/docker-eleventy
that referenced
this issue
May 1, 2024
Also, this needed to rollback node image to 18 due to nodejs/docker-node#1829 This may have implications on #3. The image still install latest available eleventy from NPM, so each beta build is just another latest stable. This issue is due to process between github-release-notifier and eleventy team making a tag on github on each beta build. This should be handled by github-release-notifier
jaymoulin
added a commit
to femtopixel/docker-eleventy
that referenced
this issue
May 2, 2024
Also, this needed to rollback node image to 18 due to nodejs/docker-node#1829 This may have implications on #3. The image still install latest available eleventy from NPM, so each beta build is just another latest stable. This issue is due to process between github-release-notifier and eleventy team making a tag on github on each beta build. This should be handled by github-release-notifier
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Expected Behavior
npm responding to calls such as (but not limited to as this affects the totallity of npm) :
Current Behavior
currently running any npm command inside this image wil cause npm to take the shell (as expected) and proceed to do nothing until being forcibly closed effectively never crashing or giving back the shell in any way
Possible Solution
this is an error on your end as pulling directly from alpine:3.17 for arm and adding node and npm from apk gives the expected output
Steps to Reproduce
pull the image and run any npm command inside a container running it
Additional Information
The text was updated successfully, but these errors were encountered: