-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 10.4.0 fails "npm install" when using node 18.19.1 and running under slow multi platform ARM build #7231
Comments
Found this issue that looks similar: nodejs/node#46188 |
A few more examples:
|
With a bit more log info:
|
We've recently started seeing this issue too after picking up an update from node Same symptoms, where this only seems to appear in the slow multi-platform ARM build from a linux/amd64 build machine. repo: https://github.com/mcneilco/acas Error:
|
We also seen the same issue: some logs:
Docker file used for the build: https://github.com/bpatrik/pigallery2/blob/e50861fce45899539f07dca32e44ecb30f46cf39/docker/debian-bullseye/Dockerfile.build using dockerx to build for arm64. This only happens on arm64 and only with debian. Works with alpine. Locking docker image to |
This issue may be a duplicate / other symptom of #7072 which has been fixed in npm |
* npm patch npm/cli#7231 (comment) * Delete huge unnecessary tools folder
And hopefully fixed in: nodejs/node#52505 |
Tested that with 10.5.2 that it fixed the issue. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
We are building our node docker images from this repo:
https://github.com/connectedcars/docker-node
This has been working well until we upgraded to npm 10.4.0, npm 9.8.1 works without issue.
The build is a multi platform(linux/amd64 and linux/arm64) docker build on a linux/amd64 build machine. For the ARM build it consistently fails when using npm 10.4.0 with EPIPE error while fetching different npm packages. The arm64 build is about 10x slower than the amd64 build so this could indicate that we are hitting a race condition of some sort. We also tested on a Macbook Pro M3(linux/arm64) and here we don't see the issue.
Expected Behavior
Install packages without errors.
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: