dockerfilePath is only supported for the Dockerfile builder
Hi I am unable to redeploy a project using Nixpacks. It states in the Documentation under Builds that "we will also build using a Dockerfile if found at the project root", but it doesn't. I am also unable to change the builder on my project like shown in the image attached. Any help is appreciated!
Solution:Jump to solution
Yeah there is a strange setting on the deployment related to the dockerfile path. Can you please try creating a new service and deploying the same code.
37 Replies
Project ID:
N/Ado you have a dockerfile at the root of your project?
Yes, the project is a direct fork of https://github.com/railwayapp-templates/listmonk
can you send the fork
Yes, it's located here https://github.com/frankievalentine/listmonk
make it public?
Done
can you show me a few screenshots of your listmonk service settings
Yeah sure, what are you looking for a screenshot of specifically?
Build commands?
the attached repo, branch, etc etc
Sure, here is the Service and Build sections
interesting
and what do your build logs say?
Just the title of this help post "dockerfilePath is only supported for the Dockerfile builder"
screenshot please
yeah that's not supposed to happen
I know I told Percy the project id was N/A but would you mind sending your project id
Yeah sure, I tried using CMD + K to look that up, but nothing came up for project id
it's definitely in there, it's also in the url
1006629907067064482
Looks like
that's absolutely not it
I don't know what that is
uh that's discord, we want the railway project id
1f777c81-a2df-44ac-a6ea-a4a357a75838
Thread has been flagged to Railway team by @Brody.
Taking a look at this now. Did you have a environment variable set to specify the location of the dockerfile?
Hi, the Dockerfile is in the root of the project. In the docs it states "We will also build using a Dockerfile if found at the project root." Can you please clarify if this is incorrect? Thanks for your help!
that's correct, but have you set any environment variables that have anything to do with a dockerfile?
Solution
Yeah there is a strange setting on the deployment related to the dockerfile path. Can you please try creating a new service and deploying the same code.
No env vars have been set that have anything to do with a dockerfile, I'll try deploying a new service
Deploying a new service works just fine, the build setting changed to Dockerfile from Nixpacks
awesome, problem solved
A better solution would have been to be able to manually change the Builder like shown in the attached image of this help post, imo. I would have been curious to see if the build would have succeeded that way rather than delete my entire project. Luckily, it hadn't been configured.
Thanks for your help and time though jr and Brody
woah no one said to delete your entire project??
Maybe I'm confused as to the flow or route I should have taken then. To deploy a new Listmonk "service" or "template" I was prompted to have a new project. Should I have removed the service leaving the DB? Then deploy a new project and connect the old DB to the new project? Can you explain what create a new service means?
delete the service, add an empty service, add the database variables, add your repo
Ah I see, I'm thinking strictly of using the template not an empty service, that makes sense
That still doesn't explain why I wouldn't be able to change the Builder manually though or if that would have solved it
jr said there was a setting on the deployment causing it to default to nixpacks
I did see him mention that, but no setting was configured for the deployment other than a custom subdomain. He must have saw something I didn't. All good. Thanks!