how to troubleshoot the files in your railway build process?
Anonymous
PROOP

8 months ago

Custom Project name(Custom Service name)=>widdyup

Project name(Service name)=>fabulous-contentment

Project id(serivce id)=>d6bfbe54-adbe-4e16-b4ff-badd7d915828

From github repo

Issue(Question):

How to check the files in your railway build process? I build my applicaiton in my local successfully, but after deploy in railway with docker build images ,looks like it lost the some package, but the packages come from pnpm install,I double check it already in package.json.

So how to trouble shoot with your railway build the files?

logs=>https://railway.com/project/d6bfbe54-adbe-4e16-b4ff-badd7d915828/logs?environmentId=fef1c86f-dcac-4d19-9049-c1bc078332e8&filter=%28%40deployment%3Ad0cff8be-bfa6-445a-9169-8b94841c9dc9%29+&start=1752875195645&end=1752875224795

Attachments

railway.png
$10 Bounty

3 Replies

Railway
BOT

8 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

idiegea21
HOBBY

8 months ago

i think your build fails because pnpm isn’t installing everything correctly in Docker causing @nestjs/core to be missing at runtime. It works locally, but the Dockerfile may not copy all needed files or run the install in the right context. i thinkt the below steps should help:

  • Ensure all workspace files (pnpm-lock.yaml, etc.) are copied.

  • Run pnpm install properly in Docker.

  • Move @nestjs/core to dependencies (not just devDependencies).

  • Lastly, review your Dockerfile to ensure it's structured to install everything properly. a small change there can make a big difference in fixing missing packages during deployment.

superslowsloth
HOBBY

8 months ago

add this line in your Dockerfile wink emoji right before the last line

RUN ls -la

Loading...