ECONNRESET when building MFE images with multiple parallel stages

[mariajgrimaldi]

Description

Currently, to avoid connection errors while building MFE images, we must use a custom build kit configuration file to restrict the number of parallel stages. See these posts for more info on the errors: https://discuss.openedx.org/t/npm-err-code-err-socket-timeout-when-building-mfe-image/10414, overhangio/tutor-mfe#55 (comment). The root cause is still unknown.

How to reproduce

You can try building a new image without the Prepare docker if building MFE step. You'll get a similar error to:

 > [profile-common 3/5] RUN --mount=type=cache,target=/root/.npm,sharing=shared npm clean-install --no-audit --no-fund --registry=https://registry.npmjs.org/:
240.7 npm ERR! code ECONNRESET
240.7 npm ERR! errno ECONNRESET
240.7 npm ERR! network request to https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
240.7 npm ERR! network This is a problem related to network connectivity.
240.7 npm ERR! network In most cases you are behind a proxy or have bad network settings.
240.7 npm ERR! network 
240.7 npm ERR! network If you are behind a proxy, please make sure that the
240.7 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
241.1 
241.1 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-01T01_48_14_723Z-debug-0.log
------
------
 > [course-authoring-common 3/5] RUN --mount=type=cache,target=/root/.npm,sharing=shared npm clean-install --no-audit --no-fund --registry=https://registry.npmjs.org/:
233.5 npm ERR! code ECONNRESET
233.5 npm ERR! errno ECONNRESET
233.6 npm ERR! network request to https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
233.6 npm ERR! network This is a problem related to network connectivity.
233.6 npm ERR! network In most cases you are behind a proxy or have bad network settings.
233.6 npm ERR! network 
233.6 npm ERR! network If you are behind a proxy, please make sure that the
233.6 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
233.8 
233.8 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-01T01_48_18_005Z-debug-0.log
------
Dockerfile:439
--------------------
 437 |     ENV CPPFLAGS=-DPNG_ARM_NEON_OPT=0
 438 |     ENV PACT_SKIP_BINARY_INSTALL=true
 439 | >>> RUN --mount=type=cache,target=/root/.npm,sharing=shared npm clean-install --no-audit --no-fund --registry=$NPM_REGISTRY

[jfavellar90]

This was partially resolved by #12, however, it's worth keeping the research since:

• It does not fail on Picasso V2
• Local builds still require the build-kit parallelism adjustment