Dockerfiledoes not exist
3 months ago
I have a monorepo with the root set to /apps/api. I have a Dockerfile at /apps/api/Dockerfile on master and staging. I've tried using a Dockerfile at /apps/api/Dockerfile and Dockerfile. Both are showing the same "Dockerfile Dockerfile does not exist" error.
16 Replies
3 months ago
It found the Dockerfile when I didn't set the root directory and then set the "Dockerfile Path" to /apps/api/Dockerfile but the build breaks because it didn't set the root. When I set the root, then it can't find the Dockerfile. When I set the root and change the "Dockerfile Path" to Dockerfile it can't find the Dockerfile. I'm so confused :|
3 months ago
I'm finding the interface really buggy, i have 3 services, and it's consistently finding the config files. This seems to be the issue. Sometimes the "Railway Config File" autocompletes, some times it doesn't. The "Dockerfile Path" seems to autocomplete from the root but I need to do it from the relative path I have set on the root. Very confusing.
3 months ago
Now 2 of my services are working but the 3rd is not. I think it's not setting the config files correctly when they are being saved so I just need to keep trying until it does.
3 months ago
Here is the one that is still not working: https://railway.com/project/73b6a61e-1a37-49a7-a7eb-f2133cb748d8/service/71797931-5b17-448e-a25c-e51c291df09d?environmentId=a7557612-9c55-45c7-85c3-a62edbcaddb3
root: /apps/client
dockerfile /apps/client/Dockerfile
railway config /apps/client/railway.toml
Setting railway config is not setting the config like in my other services.
I'm still getting "Dockerfile Dockerfile does not exist"
3 months ago
Hi there,
I'm trying to find out what's going on with your application:
Here's my understanding of what you want:
- Root directory at: /apps/client
- Branch at zlwaterfied/deploy-previews
- Railway config file at: /apps/client/railway.toml
- Dockerfile at: /apps/client/Dockerfile
I see you have the other branches pending the master branch. Unfortunately I cannot view your github to verify that your code is correct or that the Dockerfile is in the correct location. So I see that for the other applications that they are building correctly.
Can you try:
1. Open the current settings page for the client: https://railway.com/project/73b6a61e-1a37-49a7-a7eb-f2133cb748d8/service/71797931-5b17-448e-a25c-e51c291df09d/settings?environmentId=a7557612-9c55-45c7-85c3-a62edbcaddb3
2. Ensure you have the following settings:
- Root directory at: /apps/client
- Branch at master
- Railway config file at: /apps/client/railway.toml
- Dockerfile at: /apps/client/Dockerfile
3. Press CTRL + K on your keyboard and select Deploy Latest Commit
What happens? Do you get an error? If so, what is the error?
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Ok I checked that all the settings are the same as what you have and I deployed last commit. And confirmed there is a Dockerfile at /apps/client/Dockerfile (see image).
I got the same error. Attached a screenshot.
Attachments
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
The crazy part is, it's just a Next.js app. I just deleted the service and recreated it, all i did was set the root. Generally it should recognize it's Next.js and handle it but no I'm still getting a Dockerfile file error even when it's set to Railpack.
3 months ago
Given this other user report I think it might be a bug: https://station.railway.com/questions/i-am-trying-to-build-a-container-with-a-69d6f6aa.
3 months ago
hey There,
i just put up the same issue, I deployed 3 apps with no issues, a mono-repo and folder inside the repo have the DockerFiles, All worked fine then it stopped today about 2 hours ago? i tried to create a new app and i have been fighting this error for ages now. exactly the same issue you are seeing. I even tried to move the Dockerfile of the app that was not building to the root of the repo and i got what you did where it then cannot find the other folders.
Not sure how much this helps!
thanks
3 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Hey there,
We're taking a deeper look at the issue as I believe there's an underlying product issue here and nothing incorrectly configured with your project.
3 months ago
@echohack - any updates?
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Hi there, no updates yet - we will likely address after the holidays, but rest assured this is still an open ticket with our product team. Please let us know if you have any other issues.
Status changed to Awaiting User Response Railway • 3 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago
2 months ago
This wasn't resolved, still getting errors. Can I get an update, this seems like a big issue ...
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Howdy!
We're still looking into this internally. Apologies that it got closed! Will get back to you as soon as possible!
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
🛠️ The ticket Dockerfile build path detection issue has been marked as in progress.
2 months ago
✅ The ticket Dockerfile build path detection issue has been marked as completed.
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved brody • 2 months ago