Many consistent "Container failed to start" errors on railway
flatypus
PROOP

2 years ago

(no markdown available for this content)

33 Replies

flatypus
PROOP

2 years ago

d45797ab-711e-43f9-9781-c6320c9554d7



This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response angelo-railway almost 2 years ago


flatypus
PROOP

2 years ago

thx ❤️ angelo


keep in mind, I am not the oncall but this is the best way to get our attention


flatypus
PROOP

2 years ago

yep sg


flatypus
PROOP

2 years ago

i've just been up for twenty four hours, there's a product demo in two hours and things don't work LOL


not good wtf


flatypus
PROOP

2 years ago

we're playing container roulette now

1263319134368825416


which env?


on prod?


flatypus
PROOP

2 years ago

yep


getting: Error: Config file apps/rethink-ingestion/nixpacks.toml does not exist


flatypus
PROOP

2 years ago

oh interesting


you have that in your repo?


flatypus
PROOP

2 years ago

yes


flatypus
PROOP

2 years ago

1263320248573104189


Can you disable the new builder for me?


I have escalated this internally


and again I am sorry, I know you and Alex have been facing the brunt of issues as of late with our platform. We take this seriously.


@flatypus - in your Railway.json, can you make this relative? "nixpacksConfigPath": "apps/rethink-ingestion/nixpacks.toml"


I would do: "nixpacks.toml"


flatypus
PROOP

2 years ago

gotchu, i'm in the middle of setting up our repo on my cofounder's presentation laptop 😂 but we absolutely appreciate you for helping us out immensely


flatypus
PROOP

2 years ago

it seems to have been off

1263322755185770617


flatypus
PROOP

2 years ago

this is the current railway.json, i didn't define the nixpacks.toml, it just got autodetected

1263323012376170526


flatypus
PROOP

2 years ago

i can try adding the "nixpacksConfigPath": "nixpacks.toml" line


flatypus
PROOP

2 years ago

to this

1263323290819100764


yep, do that


flatypus
PROOP

2 years ago

thx


flatypus
PROOP

2 years ago

ayyy, wow! deployment successful

1263324185103695996


fwiw, and I know we have been saying it thorughout the week


this last 72 hour period we have found and scaled every part of the build process, you should have seen the publish step gone WAYYYY faster yea?


flatypus
PROOP

2 years ago

HAHAHAH yepppp you guys have done an amazing job


flatypus
PROOP

2 years ago

(not me struggling for four hours trying to deploy api on fly, and they're absolutely not doing a massive rescale effort too :)


Welcome!

Sign in to your Railway account to join the conversation.

Loading...