Adding a volume to a node service fails to startup service

cgatian

HOBBYOP

18 days ago

I created a volume for my node service and specified the path as "app/storage". When my backend redeploys, the container starts up but then immediately stops and is left in a loop trying to deploy.

If I remove the volume, the application starts.

This is a NestJS app, so there should be some logging if it were a service startup failure.

I confirmed I don't have any code that needs this path on startup.

Anything worth trying would help, thank you.

Attachments

logs.PNG

$10 Bounty

4 Replies

Status changed to Open Railway • 18 days ago

0x5b62656e5d

MODERATOR

18 days ago

Try adding a custom start command that uses node to start your application instead of a package manager like npm or pnpm.

https://docs.railway.com/deployments/troubleshooting/nodejs-sigterm-handling

cgatian

HOBBYOP

18 days ago

Tried changing the startup scripts. Doesnt look like that did anything. I removed my predeploy step, and that removed it from the Deploy logs. Now it just sits in the creating containers state.