cal.com icon indicating copy to clipboard operation
cal.com copied to clipboard

failed to solve: process "/bin/sh -c yarn install" did not complete successfully: exit code: 137`

Open techsupportkoeln opened this issue 3 weeks ago • 1 comments

Found a bug? Please fill out the sections below. 👍

Issue Summary

I reinstalled Cal.com with version 5.9.12 and when starting the Docker container I get the following error message:

`461.8 ➤ YN0007: │ prisma@npm:6.16.1 [a80c8] must be built because it never has been before or the last one failed

failed to solve: process "/bin/sh -c yarn install" did not complete successfully: exit code: 137`

Steps to Reproduce

  1. install cal.com docker compose version 5.9.12
  2. start the docker container

Actual Results

The container can't start.

Expected Results

that the container start

Technical details

Ubuntu 24.04 LTS docker compose cal.com v5.9.12

Evidence

techsupportkoeln avatar Dec 10 '25 12:12 techsupportkoeln

CAL-6895

linear[bot] avatar Dec 10 '25 12:12 linear[bot]

strange that nobody else has this problem. I had to delete my old Docker Instanz because it was hacked. Now i try to install a new one with docker compose and stop at this point.

techsupportkoeln avatar Dec 11 '25 16:12 techsupportkoeln

I'm also having issues building the container from scratch

CaliLuke avatar Dec 12 '25 18:12 CaliLuke

After some research, I noticed that I need to allocate more resources to the VM. A minimum of 30 GB of hard drive space and 12 GB of RAM is required. At least for the initial startup.

Now i having the issues later in the building process:

`328.1 328.1 <--- JS stacktrace ---> 328.1 328.1 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 328.1 1: 0xb9bbf0 node::Abort() [/usr/local/bin/node] 328.1 2: 0xaa27ee [/usr/local/bin/node] 328.1 3: 0xd734a0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node] 328.1 4: 0xd73847 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node] 328.1 5: 0xf50c55 [/usr/local/bin/node] 328.1 6: 0xf51b58 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/local/bin/node] 328.1 7: 0xf62053 [/usr/local/bin/node] 328.1 8: 0xf62ec8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node] 328.1 9: 0xf3d81e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node] 328.1 10: 0xf3ebe7 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node] 328.1 11: 0xf1fdea v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node] 328.1 12: 0x12e505f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node] 328.1 13: 0x1711cb9 [/usr/local/bin/node] 342.2 Next.js build worker exited with code: null and signal: SIGABRT

failed to solve: process "/bin/sh -c yarn --cwd apps/web workspace @calcom/web run build" did not complete successfully: exit code: 1`

techsupportkoeln avatar Dec 16 '25 16:12 techsupportkoeln

Version 5.9.14 is now working. But i can't connect my Kalender. It is Step 1 of 5 in the getting-started page. If i klick on "Kalender verbinden" nothing happens.

techsupportkoeln avatar Dec 16 '25 17:12 techsupportkoeln