Skip to content

Docker builds started failing #1761

@joachimvh

Description

@joachimvh

Description

At some point our Docker builds suddenly started failing. This seems to have coincided with when then lts-alpine image changed from Node v18 to v20: https://github.com/nodejs/docker-node/blob/18b91b947173898d92dd736bcb334ab3bc4486c0/versions.json#L59 . This seems to be a known issue: nodejs/docker-node#1798 .

Testing locally the build succeeds for me when using the v18 images, but fails when using v20 with the following error:

473.3 npm ERR! code ECONNRESET
473.3 npm ERR! errno ECONNRESET
473.3 npm ERR! network request to https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
473.3 npm ERR! network This is a problem related to network connectivity.
473.3 npm ERR! network In most cases you are behind a proxy or have bad network settings.
473.3 npm ERR! network 
473.3 npm ERR! network If you are behind a proxy, please make sure that the
473.3 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
473.9 
473.9 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-10-31T13_06_21_050Z-debug-0.log
--------------------
   9 |     
  10 |     # Install and build the Solid community server (prepare script cannot run in wd)
  11 | >>> RUN npm ci --unsafe-perm && npm run build
  12 |     
  13 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c npm ci --unsafe-perm && npm run build" did not complete successfully: exit code: 1

Will switch the Docker image to Node v18 to fix this, but we will need to switch back at some point when this is fixed.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions