[BUG] RUN npm ci --unsafe-perm fails in docker container with https registry - works with http

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

RUN npm ci --unsafe-perm fails on some Macs when trying to build a docker container. It does work locally. And it does work if changing the registry from https to http for with the docker command RUN npm config set registry http://registry.npmjs.org/

We're unable to determine why that should cause any issue?

There error generated is npm ERR! code ECONNRESET

We are using npm 8.19.3 and Node 16.13.0

Expected Behavior

Docker build files work with npm. (Previously we used yarn and have ported to npm)

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm: 8.19.2 and .3
• Node.js: 16.13.0
• OS Name: MacOS 12.6.1
• System Model Name: 2019 MacBook Pro. Docker: mlupin/docker-lambda:nodejs16.x-build-x86_64
• npm config:

; copy and paste output from `npm config ls` here

Start by reproducing the Docker build with mlupin/docker-lambda:nodejs16.x-build-x86_64, npm 8.19.3, Node 16.13.0, and the registry switched between HTTPS and HTTP. Inspect the npm config and the ECONNRESET failure during npm ci --unsafe-perm; done means identifying the HTTPS-specific cause and establishing whether the Docker build can complete against the HTTPS registry.