docker/Dockerfile

@@ -49,6 +49,16 @@ COPY packages/database ./packages/database
 COPY packages/shared ./packages/shared
 COPY docker/next.config.docker.ts ./apps/web/next.config.ts
 
+# Force BuildKit to finish the two tsup builds before starting the heavy
+# Next.js compile. docker-compose's `depends_on` only orders runtime startup,
+# not `docker compose build` — without these COPYs, BuildKit runs all three
+# build stages in parallel and the host OOMs around the 73s mark of the web
+# build (kernel reaps with exit 255 and no Docker error, matching the warning
+# below about heap sizing). The copied files are throwaway markers; the
+# runtime web image never reads /tmp.
+COPY --from=collab-build /app/apps/collab-server/dist/index.mjs /tmp/.collab-built
+COPY --from=mcp-build /app/apps/mcp-server/dist/index.js /tmp/.mcp-built
+
 ENV NEXT_TELEMETRY_DISABLED=1
 ENV NODE_ENV=production
 # Give the Next.js webpack compile enough V8 heap headroom on the Coolify host.

docker/docker-compose.coolify.yml

@@ -22,10 +22,15 @@
 #   The shared `deps` stage is hashed identically across targets, so BuildKit
 #   runs `pnpm install` ONCE.
 #
-#   `web` declares depends_on collab+mcp so Compose builds the lightweight
-#   services first and the heavy `next build` (peak ~2.5 GB heap) gets the host
-#   effectively to itself instead of fighting concurrent runtime-stage COPYs
-#   for memory.
+#   The heavy `next build` for `web` (peak ~3 GB heap with 5 GB headroom)
+#   must not race the two tsup builds for collab+mcp on the 8 GB Coolify
+#   host or the kernel OOM-kills it (exit 255 with no Docker error). Build
+#   ordering is enforced inside docker/Dockerfile: the `web-build` stage
+#   has explicit `COPY --from=collab-build` / `COPY --from=mcp-build` lines
+#   that force BuildKit's DAG to finish those two before starting the web
+#   compile. The `depends_on` below only orders runtime startup, NOT image
+#   builds — that was a misconception from an earlier iteration of this
+#   file.
 
 services:
   web: