-
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 install stucks with node:20 #1946
Comments
I have the same issue with yarn |
Same here. My image works with Node 16, 18 and 19. With 20 even Update: on my pipeline based on Ubuntu-22.04 linux/amd64 works |
I just tried on Ventura with an M2 chip and it didn't hang |
I am ablwe to reproduce the behavior when disabling my network. I am wondering if some firewall rule might be blocking traffic. |
Hi, I'm also facing the same issue. I'm using M1 Mac. I'm observing this issue since last week. I have tried Node 20,18 alpine, slim and latest. The issue persist. |
I was able to run yarn and npm commands now after disabling Use Rosetta for x86/amd64 emulation on Apple Silicon option in docker settings. Not sure this is a fix. |
I'm encountering the same issue - docker build hangs on (Why do this? I want to test an image on my mac laptop that will eventually run in an amd64 environment, and one apt dependency does not have an arm64 version) Workarounds I found:
Dockerfile
package.json
index.js
Console output
|
Same issue affecting npm and yarn when using |
got same issues , you can easily duplicate this issue with below commands
Then it stucks at installation forever. run tests on below platforms
|
My workaround at the moment is to stay on Node 18.x. |
Also have the same issue, and reverted back to Node 18.x for my docker builds. |
It seems that this is a duplicate of #1798? I see the same seqence of |
Upgrading from Docker Desktop 4.21 to 4.26.1 (Latest at the time of this writing) seems to have fixed this problem for me on an M2 Mac. |
# linux/arm/v7 arm32 is not supported by node20 nodejs/docker-node#1946
TriggerWhat triggered this problem for me was updating my SolutionThe key solution for me was using DetailsHere are some additional details I gathered before finding the final solution, in case it's helpful for others, or for debugging the root problem. Sorta SolutionsThese attempts somewhat worked but not in a satisfactory way...
Non-SolutionsThese attempts didn't work...
|
Using |
My finding is that it eventually goes through the installation process, but hangs for 2 - 5 minutes. In my build process there are two node applications installed in node:20, the other one goes through fine, the second one hangs. Both have lockfileVersion 3. Only difference I can find is that the non-functioning one is defined as a "type": "module" in package.json. |
* chore: Upgrade stack versions * Revert node upgrade See nodejs/docker-node#1946
It's still a thing on node 22 :/ |
any news? :/ |
I suddenly faced this issue since last week, building on a Cloud platform |
Same problem, i upgrade to puppeteer 22.4.1 but problem still occurs :-( |
Using a Dockerfile to specify the image seems to fix it. |
Environment
Expected Behavior
NPM install should be started. I've tested this with node:18 image instead and it works. node:20-slim stucks too.
Current Behavior
NPM install does not start and stucks.
I've tried other npm commands like
npm cache clean --force
but those stuck too.Possible Solution
Steps to Reproduce
I'm using the docker file from official nodejs example :
Additional Information
The text was updated successfully, but these errors were encountered: