Yarn Build Failure

[justinb-dfw]

Branches tested:

• release-v5.2.0
• main

Not building when I run DOCKER_BUILDKIT=0 docker-compose up -d

➤ YN0013: │ object.entries@npm:1.1.6 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.assign@npm:4.1.4 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.assign@npm:4.1.5 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.entries@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.entries@npm:1.1.6 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.entries@npm:1.1.7 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.assign@npm:4.1.5 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.entries@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ object.entries@npm:1.1.6 can't be found in the cache and will be fetched from the remote registry [+] Running 0/1ect.entries@npm:1.1.7 can't be found in the cache and will be fetched from the remote registry ⠇ Service calcom Building 92.8s The command '/bin/sh -c yarn install' returned a non-zero code: 137

[ivancarlosti]

It's the same issue reported #426 and #423

[kevinkupski]

Are you sure? I also get this when I apply #429.

[krumware]

I've seen this with older yarn versions and projects with a significant number of package dependencies. Since you are building the image, can you please see if updating the base images in the Dockerfile to node:22 (from node:18) has a positive impact on this?

[dcharles525]

Hey @justinb-dfw did using node 20 or 22 solve this problem for you?