Ever since the build container we use [1][2] updated to use npm@10,
the image builder github action has encountered a number of problems.
The first was solved with #1746. The second more random problem has been
with network connections erroring out when installing dependencies.
To work around the network and nofiles errors:
enforce the use of npm@9
pin the Dockerfile base images to specific version tags;
builder at :1-88, and runtime at :1-93
Additional solutions:
Add the force to npm@9 directly in the Dockerfile for use in all
circumstances
Find a way to use something like verdaccio to proxy/mirror the npmjs
repo during the build so npmjs fetches can be pooled across the parallel
image builds
Ever since the build container we use [1][2] updated to use
npm@10, the image builder github action has encountered a number of problems. The first was solved with #1746. The second more random problem has been with network connections erroring out when installing dependencies.To work around the network and nofiles errors:
npm@9:1-88, and runtime at:1-93Additional solutions:
npm@9directly in the Dockerfile for use in all circumstances[1] registry.access.redhat.com/ubi9/nodejs-18:latest [2] https://catalog.redhat.com/software/containers/ubi9/nodejs-18/62e8e7ed22d1d3c2dfe2ca01
Signed-off-by: Scott J Dickerson sdickers@redhat.com Signed-off-by: Cherry Picker noreply@github.com