Docker deploy fails due to network error

[maxb2]

Occasionally the arm64 image fails to build due to a network error during npm install:

#31 [linux/arm64 dependency-builder 5/5] RUN npm install
#31 651.2 npm ERR! code ERR_SOCKET_TIMEOUT
#31 651.4 npm ERR! network Socket timeout
#31 651.4 npm ERR! network This is a problem related to network connectivity.
#31 651.4 npm ERR! network In most cases you are behind a proxy or have bad network settings.
#31 651.4 npm ERR! network 
#31 651.4 npm ERR! network If you are behind a proxy, please make sure that the
#31 651.4 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
#31 655.0 
#31 655.0 npm ERR! A complete log of this run can be found in:
#31 655.0 npm ERR!     /root/.npm/_logs/2023-03-17T14_01_42_616Z-debug-0.log
#31 ERROR: process "/bin/sh -c npm install" did not complete successfully: exit code: 1

#26 [linux/arm/v7 dependency-builder 5/5] RUN npm install
#26 CANCELED
------
 > [linux/arm64 dependency-builder 5/5] RUN npm install:
 ERR! code ERR_SOCKET_TIMEOUT
ERR! network In most cases you are behind a proxy or have bad network settings.
#31 651.4 npm ERR! network 
#31 651.4 npm ERR! network If you are behind a proxy, please make sure that the
#31 651.4 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
#31 655.0 
#31 655.0 npm ERR! A complete log of this run can be found in:
#31 655.0 npm ERR!     /root/.npm/_logs/2023-03-17T14_01_42_616Z-debug-0.log
------
Dockerfile:9
--------------------
   7 |     COPY . .
   8 |     
   9 | >>> RUN npm install
  10 |     
  11 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1

I think the only thing we can do is restart the job until it succeeds. Or we add a retry mechanism to the workflow.

[wsGolden]

I have encountered the same problem. Have you resolved it

[maxb2]

No, we haven't fixed this. We suspect it is a random network dropout.

[TheMBeat]

You can setup the npm Timeouts to Max

      - run: npm config set fetch-retry-mintimeout 20000
      - run: npm config set fetch-retry-maxtimeout 120000
      - run: npm config set fetch-timeout 300000

This works for me.