Many consistent "Container failed to start" errors on railway

No description
27 Replies
Percy
Percy4mo ago
Project ID: d45797ab-711e-43f9-9781-c6320c9554d7
flatypus
flatypus4mo ago
d45797ab-711e-43f9-9781-c6320c9554d7
angelo
angelo4mo ago
!t
Duchess
Duchess4mo ago
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.
You're seeing this because this thread has been automatically linked to the Help Station thread.
flatypus
flatypus4mo ago
thx ❤️ angelo
angelo
angelo4mo ago
keep in mind, I am not the oncall but this is the best way to get our attention
flatypus
flatypus4mo ago
yep sg i've just been up for twenty four hours, there's a product demo in two hours and things don't work LOL
angelo
angelo4mo ago
not good wtf
flatypus
flatypus4mo ago
we're playing container roulette now
No description
angelo
angelo4mo ago
which env? on prod?
flatypus
flatypus4mo ago
yep
angelo
angelo4mo ago
getting: Error: Config file apps/rethink-ingestion/nixpacks.toml does not exist
flatypus
flatypus4mo ago
oh interesting
angelo
angelo4mo ago
you have that in your repo?
flatypus
flatypus4mo ago
yes
flatypus
flatypus4mo ago
No description
angelo
angelo4mo ago
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
flatypus4mo 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
flatypus4mo ago
it seems to have been off
No description
flatypus
flatypus4mo ago
this is the current railway.json, i didn't define the nixpacks.toml, it just got autodetected
No description
flatypus
flatypus4mo ago
i can try adding the "nixpacksConfigPath": "nixpacks.toml" line
flatypus
flatypus4mo ago
to this
No description
angelo
angelo4mo ago
yep, do that
flatypus
flatypus4mo ago
thx
flatypus
flatypus4mo ago
ayyy, wow! deployment successful
No description
angelo
angelo4mo ago
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
flatypus4mo ago
HAHAHAH yepppp you guys have done an amazing job (not me struggling for four hours trying to deploy api on fly, and they're absolutely not doing a massive rescale effort too :)
Want results from more Discord servers?
Add your server