a month ago
You reached the start of the range
Apr 12, 2026, 3:16 PM
[Region: us-west1]
=========================
Using Detected Dockerfile
=========================
context: 9zx4-JEWI
internal
load build definition from Dockerfile
0ms
internal
load metadata for docker.io/library/node:20-slim
421ms
auth
library/node:pull token for registry-1.docker.io
0ms
internal
load .dockerignore
0ms
deps
FROM docker.io/library/node:20-slim@sha256:f93745c153377ee2fbbdd6e24efcd03cd2e86d6ab1d8aa9916a3790c40313a55 cached
5ms
internal
load build context
0ms
deps
RUN apt-get update && apt-get install -y openssl && rm -rf /var/lib/apt/lists/*
3s
Processing triggers for libc-bin (2.36-9+deb12u13) ...
deps
WORKDIR /app
15ms
deps
COPY package*.json ./
63ms
deps
RUN npm install --ignore-scripts
16s
npm notice
builder
COPY --from=deps /app/node_modules ./node_modules
1s
builder
COPY . .
1s
builder
RUN node node_modules/.bin/prisma generate && node --max-old-space-size=3072 node_modules/.bin/next build
2s
Prisma schema loaded from prisma/schema.prisma
Generated Prisma Client (v5.22.0) to ./node_modules/@prisma/client in 82ms
Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)
Tip: Want to turn off tips and other hints? https://pris.ly/tip-4-nohints
▲ Next.js 14.2.35
- Experiments (use with caution):
· cpus
Creating an optimized production build ...
Next.js build worker exited with code: null and signal: SIGBUS
Dockerfile:24
-------------------
23 |
24 | >>> RUN node node_modules/.bin/prisma generate && \
25 | >>> node --max-old-space-size=3072 node_modules/.bin/next build
26 |
-------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c node node_modules/.bin/prisma generate && node --max-old-space-size=3072 node_modules/.bin/next build" did not complete successfully:
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your build is exiting with a SIGBUS signal during the Next.js compilation step, which indicates the build process ran out of memory. Builds have access to 8 GB of memory. Your Dockerfile sets --max-old-space-size=3072 for the main Node process, but Next.js spawns additional worker processes during compilation, and the Docker build layer itself also consumes memory, so the total can exceed 8 GB. Reducing the --max-old-space-size value or optimizing your Next.js build (e.g., reducing page count or large dependencies) would help keep total build memory within limits.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago