a year ago
Hi guys, I'm trying (and failing) to deploy a service on railway. I notice the last successful deploy had completely different looking build logs. A failing deploy ID is: 6b8b1080-e3d3-4c71-afc7-ed7403c5f758, with a successful one being: ca8feb3c-166f-40db-b799-155d6ee71790. I note that the logs of the successful deploy start with: "Using Detected Dockerfile". I don't see that in the broken deploy logs… Any help would be appreciated
29 Replies
I'm not sure if this is relevant - but if I google some of the logs of the successful deploy, I see they are emitted by a tool called "BuildKit". The failing logs seem to come from a tool called "Kaniko" - they both seem to do similar stuff. Have I accidentally the build process over to using this "Kaniko" tool instead?
I shouldn't need to define the railway dockerfile path envvar according to the docs
My build configuration for failing deploys is still this:
[build]
builder = "DOCKERFILE"
dockerfilePath = "Dockerfile"
buildEnvironment = "V2"
a year ago
disable the new builder in your service settings -- the new builder is kainko, the old builder is buildkit -- the new builder is not recommended to be used for reasons that you just experienced
sorry Brody, I can't seem to find an option to do this - this is the only stuff I see under "build" for the service settings:

my repo doesn't have a railway.toml file - i note I can set the build version there - presumably to V1?
a year ago
oops, my bad, you should be able to disable it by removing the build environment line from your railway.toml file
but we don't have a railway toml file? presumably i'll need to make one if i need to override what is now default behaviour?
a year ago
no, you shouldn't need to, I'll take a look at the service when I'm at my laptop shortly
so much nicer than dicking around in AWS, setting up VPS's security groups etc.
a year ago
thank you! that's our goal! replace DevOps
Sorry to bother brother, but wanted to check if you'd had a chance to have a peek at my service?
a year ago
so sorry, got busy with monday morning stuff!
a year ago
i kicked off a new deploy, and it is using buildkit now, but your app starts and crashes without printing anything

hmmm - I suppose this is an improvement from before. Prior to this it never found the built artifacts (dist/server.mjs). It doesn't seem to be complaining about that now which is good I guess
a year ago
i think ive done about all i can here, at this point its now an application issue, but let me know if you need any more platform help!
a year ago
cheers!
a year ago
Admins can just do these kinds of things 😎
No clue why you never had the option to change it back though, sorry
a year ago
!s
Status changed to Solved brody • about 1 year ago