#Redeploy failing of n8n (based on https://github.com/railwayapp-templates/n8n) since Nixpacks update
16 messages · Page 1 of 1 (latest)
18020b26-b8bb-4387-864e-2517adf251df
I mean you got the answer at the very top of the logs
I mean there's no option to change the builder is there
if you wanna build with a dockerfile use a builder that will build with a dockerfile, nixpacks does not take in a dockerfile
whenever you have seen railway's build logs say "using detected dockerfile" nixpacks was never used for the build
So i've just deployed a fresh project based on Railway's own n8n template https://github.com/railwayapp-templates/n8n - same as used in the original project I mentioned.
It built correctly and automatically detected Dockerfile as the Builder.
The original project (mentioned above) based on the same template now shows up Nixpacks as the builder.
I have changed nothing since January. The only thing that's changed are updates on Railways side. How can the builder for the original project be changed back to Dockerfile from Nixpacks?
Original project (won't build) based on Railway's n8n template
redeploy it
New build for a new project based on Railway's n8n template
I've already tried that. That's where the error message "dockerfilePath is only supported for the Dockerfile builder" came from.
Again, I have no option to change the choice of builder.
delete service and deploy again
I did that and now build are completely crashing.
error logs please?
"
UserSettings were generated and saved to: /home/node/.n8n/config
Migrations in progress, please do NOT stop the process.
Stopping n8n...
Last session crashed
Migrations in progress, please do NOT stop the process.
Stopping n8n...
Last session crashed
Migrations in progress, please do NOT stop the process.
"
This is now coming back after redeploys