2 months ago
We have an issue affecting our production environment that seems similar to https://station.railway.com/questions/dockerfile-builder-not-being-used-despit-4a1dd640. Our deployment inexplicably stopped using the Dockerfile paths in our environment variables after working fine after we first set it up. Setting explicit build config separately for each service resolved the issue after we experienced a lot of pain. Now after seeing that question above resolved, I tried reverting to the automatically detected environment variable for one of our services, and the build failed because it couldn't find the Dockerfile. Please let us know if we inadvertently broke something or if there is an ongoing issue on your end. The Railway agent said we didn't change anything that would have broken it early this morning.
6 Replies
2 months ago
try setting RAILWAY_DOCKERFILE_PATH on the failing service to the dockerfile’s path relative to that service root, then redeploy...If it still fails, remove any conflicting dockerfile/build settings in railway.toml
2 months ago
RAILWAY_DOCKERFILE_PATH was set long before this issue arose. It has never changed and is still correct. It's the same as staging where we don't have any issues.
We don't have any railway.toml files. Each service has a Cargo.toml or pyproject.toml file.
2 months ago
looks like this might be related to the platform issue from 4a1dd640 that railway recently fixed. since nothing changed on your end and staging works fine, it might be worth reaching out to railway support directly and referencing both threads along with your service id so they can take a closer look at the build logs. keeping the explicit build config as a workaround in the meantime seems like the safest bet
ilyass012
looks like this might be related to the platform issue from 4a1dd640 that railway recently fixed. since nothing changed on your end and staging works fine, it might be worth reaching out to railway support directly and referencing both threads along with your service id so they can take a closer look at the build logs. keeping the explicit build config as a workaround in the meantime seems like the safest bet
2 months ago
Thanks, unfortunately, I don't know how to reach out to them. The private thread feature here on Get Help is highly discouraging when there is no sensitive information involved.
Thanks, unfortunately, I don't know how to reach out to them. The private thread feature here on Get Help is highly discouraging when there is no sensitive information involved.
2 months ago
yeah don't worry, railway staff actively monitors these threads, itsrems already jumped in on the previous issue pretty quickly. just leave it open and they'll likely reach out to you here directly
2 months ago
Switch to US East and it should work