From 3856d119449b91a80e5ff86325dd88549c77031a Mon Sep 17 00:00:00 2001 From: Randall Stillwell Date: Tue, 28 Apr 2026 13:33:46 -0500 Subject: [PATCH] docker: raise web build V8 heap to 5 GB to match 8 GB host CT 107 bumped to 8 GB RAM. Capping the heap below the available memory makes V8 GC-thrash near the limit and contributes to oom-kills. Set --max-old-space-size to 5120 MB (~60% of host) so the compile has real headroom while leaving room for kernel + dockerd + buildkit + tsup workers. Made-with: Cursor --- docker/Dockerfile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docker/Dockerfile b/docker/Dockerfile index ceb15ca..1c36aa3 100644 --- a/docker/Dockerfile +++ b/docker/Dockerfile @@ -52,10 +52,10 @@ COPY docker/next.config.docker.ts ./apps/web/next.config.ts ENV NEXT_TELEMETRY_DISABLED=1 ENV NODE_ENV=production # Give the Next.js webpack compile enough V8 heap headroom on the Coolify host. -# Sized to ~70% of the 4 GB host RAM so kernel + dockerd + concurrent runtime -# COPYs from collab/mcp still have breathing room. Below ~2 GB, the compile -# spirals into GC churn and gets oom-killed (exit 255 with no Docker error). -ENV NODE_OPTIONS=--max-old-space-size=2560 +# Sized to ~60% of an 8 GB host so kernel + dockerd + buildkit + concurrent +# tsup workers still have breathing room. Below ~3 GB the compile spirals +# into GC churn and gets oom-killed (exit 255 with no Docker error). +ENV NODE_OPTIONS=--max-old-space-size=5120 RUN pnpm exec turbo build --filter=@tasks/web