Railway•13mo ago

nestjs app will not start via Dockerfile + cmd

Project ID: 35c2c647-0f2a-44db-a175-d671a74cb289 Application tries to start and just loops:

+ echo Deploying Prisma migrations...

Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

Starting the application...

+ echo Starting the application...

+ yarn start

Deploying Prisma migrations...

+ echo Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

+ echo Starting the application...

Starting the application...

+ yarn start

Deploying Prisma migrations...

+ echo Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

+ echo Starting the application...

Starting the application...

+ yarn start

+ echo Deploying Prisma migrations...

Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

Starting the application...

+ echo Starting the application...

+ yarn start

Deploying Prisma migrations...

+ echo Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

+ echo Starting the application...

Starting the application...

+ yarn start

Deploying Prisma migrations...

+ echo Deploying Prisma migrations...

+ yarn prisma migrate deploy

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

19 migrations found in prisma/migrations

No pending migrations to apply.

+ echo Starting the application...

Starting the application...

+ yarn start

Solution:

its possible that theres a memory spike that tries to use more than 512mb, you just dont see it on the graph since it doesnt report that fast

Jump to solution

19 Replies

Percy•13mo ago

Project ID: 35c2c647-0f2a-44db-a175-d671a74cb289

Brody•13mo ago

at first glance it looks like your app is silently crashing one reason may be an out of memory crash, what do your memory metrics look like

drüdrüdrüOP•13mo ago

Yeah, I've been trying to get this app up for days 😓 thanks for the quick response

drüdrüdrüOP•13mo ago

Brody•13mo ago

send the dockerfile?

drüdrüdrüOP•13mo ago

I've rewritten it so many times I'll pull it, one second

drüdrüdrüOP•13mo ago

This is the latest iteration

Dockerfile

drüdrüdrüOP•13mo ago

Here is the script to start the app

railway-start.sh

drüdrüdrüOP•13mo ago

I was going to try with Nixpack.. but this seems like a whole other process.

Brody•13mo ago

does this dockerfile work locally?

drüdrüdrüOP•13mo ago

Yes

Solution

Brody•13mo ago

its possible that theres a memory spike that tries to use more than 512mb, you just dont see it on the graph since it doesnt report that fast

Brody•13mo ago

can you try upgrading to the hobby plan?

drüdrüdrüOP•13mo ago

This is local docker stats. You might be right

Brody•13mo ago

yep looks like it needs much more than 512mb at the start

drüdrüdrüOP•13mo ago

Thanks. I'm spinning it up with hobby now to take a look That's frustrating that there's no feedback or anything 🙄 It's up

Brody•13mo ago

well i guess you cant really expect stable results when an app is trying to use more memory than allowed

drüdrüdrüOP•13mo ago

Fair enough. Thanks for your help

Brody•13mo ago

no problem 🙂

Gaming

Programming

nestjs app will not start via Dockerfile + cmd