Deployment Failed on NestJS / Container Restarts
tappoyo
PROOP

a year ago

Project id: 226d017d-497f-4e0a-88fc-b04f499967fb

Hi! I'm getting a container event container died while deploying a NestJS application.

The startup logs from my application are incomplete (screenshot attached). Reading other help threads, could it be possible that I ran out of memory? I updated my plan from trial to Hobby an hour ago. I redeployed the app several times, but the issue persists. Thanks for the help!

9 Replies

brody
EMPLOYEE

a year ago

have you tried switching back to the legacy runtime?


tappoyo
PROOP

a year ago

on it


tappoyo
PROOP

a year ago

with the legacy runtime we get further, even listening to a port, but the container still stops after deployment.

1252333327814234000


brody
EMPLOYEE

a year ago

I wouldn't say you got further, the v2 runtime has a bug right now where some log lines aren't picked up and it looks like that particular log line wasn't picked up on the v2 runtime.

either way, this means it's not an issue with railway but an issue with your application


brody
EMPLOYEE

a year ago

it's trying to allocate more than 8gb of memory for some reason


brody
EMPLOYEE

a year ago

try setting a service variable NODE_OPTIONS=--max-old-space-size=4096


tappoyo
PROOP

a year ago

this worked! thanks for the quick help @Brody


brody
EMPLOYEE

a year ago

no problem!


brody
EMPLOYEE

a year ago

please don't close threads though


Loading...