Repository navigation
npm 10.4.0 fails "npm install" when using node 18.19.1 and running under slow multi platform ARM build #7231
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
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.
#21 [builder 14/16] RUN --mount=type=ssh --mount=type=secret,id=NPM_TOKEN,uid=1000 secrets2env npm install
#21 298.6 npm ERR! code EPIPE
#21 298.7 npm ERR! syscall write
#21 298.7 npm ERR! errno EPIPE
#21 298.9 npm ERR! request to https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz failed, reason: write EPIPE
#21 299.2
#21 299.2 npm ERR! A complete log of this run can be found in: /home/builder/.npm/_logs/2024-02-19T12_48_51_863Z-debug-0.log
#21 ERROR: executor failed running [/bin/sh -c secrets2env npm install]: exit code: 1
Expected Behavior
Install packages without errors.
Steps To Reproduce
- Build linux/arm64 image on google cloud build amd64 machine (10x slower than normal)
- With this package.json https://github.com/connectedcars/docker-node/blob/master/test/package.json
- Run 'npm install'
- See error 'chore: use the extracted stringify-package module #21 298.6 npm ERR! code EPIPE'
Environment
- npm:10.4.0
- Node.js: 18.19.1
- OS Name: Linux/Docker (Google Cloud Build)
- System Model Name:
- npm config:
# Disable npm color output and be less verbose
npm config set color false --global
# Read NPM token from environment variable
npm config set '//registry.npmjs.org/:_authToken' '${NPM_TOKEN}' --globalReacted by KatarinaSimnova and Alexandros Solanos
Activity
tlbdk commentedon Feb 19, 2024
Found this issue that looks similar: nodejs/node#46188
tlbdk commentedon Feb 19, 2024
A few more examples:
tlbdk commentedon Feb 20, 2024
With a bit more log info:
bffrost commentedon Mar 29, 2024
We've recently started seeing this issue too after picking up an update from node
v18.19.1tov18.20.0which included an update of npm from10.2.4to10.5.0.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:
bpatrik commentedon Apr 17, 2024
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
node:18.19-bustersolved the issue.bffrost commentedon Apr 17, 2024
This issue may be a duplicate / other symptom of #7072 which has been fixed in npm
10.5.1. We were able to explicitly install a later npm version and get around these build failures.RUN npm install npm@10.5.1 -gnpm patch
Applied npm patch for build errors (#1326)
melroy89 commentedon Apr 24, 2024
And hopefully fixed in: nodejs/node#52505
tlbdk commentedon Apr 29, 2024
Tested that with 10.5.2 that it fixed the issue.
🌱 Update project to use nodejs 20, npm >=10.5.2
🌱 Update project to use nodejs 20, npm >=10.5.2
🌱 Update project to use nodejs 20, npm >=10.5.2
🌱 Update project to use nodejs 20, npm >=10.5.2 (#2062)
🌱 Update project to use nodejs 20, npm >=10.5.2 (konveyor#2062)
🌱 Update project to use nodejs 20, npm >=10.5.2 (#2062) (#2064)
🌱 Update project to use nodejs 20, npm >=10.5.2 (konveyor#2062)