Seeing a bunch of build error even when rolling back to commits where builds used to works
Project ID: b08731c2-2a20-4ba4-b7b2-a97b42af589f
In our build logs for the backend for both our staging and prod we're facing this error even though we've rolled back to commits which used to build out well.
To be more precise here are the logs. Would appreciate some guidance as to how to resolve this.
18 Replies
Project ID:
b08731c2-2a20-4ba4-b7b2-a97b42af589f,91e262ef-85b0-4b77-b60c-089a327c9b02,91e262ef-85b0-4b77-b60c-089a327c9b02
add a railway.toml file to your project with this in it
may I ask why this is needed? I don't think this was needed before and things were ok prior to this
also it still failed
nixpacks was updated and brought unintentional breaking changes, that file with that config reverts you back to a version that likely worked for you
I see, but that config still failed, is the recommendation to just keep downgrading the nixpacksVersion
what version of nixpacks has worked in the past
the latest one that worked was this
then try that version please
unfortunately it still did not work
https://bookmarklets.up.railway.app/log-downloader/
full logs please
cool tool! thanks for sharing and helping us take a look
it says its using 1.17.0 still
can you show me how you have done the railway.toml file?
just that
one thing i realized though is that we have this file in the backend directory of our monorepo
I wonder if it has to be at the root
let me give that a shot
what directory is the service set to?
yup it is set to the root
trying it now
yeah needs to be in the root, or whatever the root is set to in the service settings
that fixed it, thanks so much for your help!