10 months ago
Project builds find on local machine, Last build was done 2 weeks ago and it worked fine on railway.
No major configuration changes done in the latest build. Here's the log I see
added 419 packages, and audited 420 packages in 13s
156 packages are looking for funding run npm fund for details
2 critical severity vulnerabilities To address issues that do not require
attention, run: npm audit fix To address all issues, run: npm audit fix --force
Run npm audit for details.
[stage-0 6/10] RUN --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-/root/npm,target=/root/.npm npm ci 13 sec
[stage-0 7/10] COPY . /app/.
[stage-0 7/10] COPY . /app/. 118 ms
[stage-0 8/10] RUN --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-next/cache,target=/app/.next/cache --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-tsconfigtsbuildinfo,target=/app/tsconfig.tsbuildinfo npm run build
runc run failed: unable to start container process: error during container init: error mounting "/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/30/fs" to rootfs at "/app/tsconfig.tsbuildinfo": create mountpoint for /app/tsconfig.tsbuildinfo mount: cannot create subdirectories in "/var/lib/buildkit/runc-overlayfs/executor/paqgewytb2x9egc80v6uachau/rootfs/app/tsconfig.tsbuildinfo": not a directory
✕ [stage-0 8/10] RUN --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-next/cache,target=/app/.next/cache --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/a837d4f6-c3c4-4d91-b3e4-14a4d277ba47-tsconfigtsbuildinfo,target=/app/tsconfig.tsbuildinfo npm run build
process "/bin/bash -ol pipefail -c npm run build" did not complete successfully: exit code: 1
2 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 📚 Deploy a Beego App
- 🧵 I have deployed next js, its showing active but its not getting opened via public url
- 🧵 npm run builds fails
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Has tsbuildinfo file on root, deleted that and it worked.
Status changed to Solved ahsanbod • 11 months ago