Build started failing last week, with "Cache mounts MUST be in the format" error
Hi! Railway is super cool - I've been really impressed with it so far.
I've run into an unexpected issue with my Demolition Checker (project id: f5a01099-9a2d-43a6-ae7b-2dd0a293f79e). It is a cron job that runs every morning at 8am (EST). It has been deployed and working fine for the past 2 months with no changes. Last week, every daily run started failing with the
Cache mounts MUST be in the format --mount=type=cache,id=<cache-id> error.
The project is open source and is available here: https://github.com/codefordayton/demolition_checker
I'm not using a cache mount statement in my existing dockerfile. Like I said, this was working just fine for a couple of months, and then started failing. Is there something I need to add to the dockerfile to get it working again?
Thanks!GitHub
GitHub - codefordayton/demolition_checker: Property demolition chec...
Property demolition checker for Preservation Dayton - codefordayton/demolition_checker
5 Replies
Project ID:
f5a01099-9a2d-43a6-ae7b-2dd0a293f79eare you sure that's the repo you are deploying?
Pretty sure.
interesting
not sure what's wrong, will look into this on a work day
No worries. Thanks for taking a look. I’ll keep futzing with it myself. I’ll post here if I figure something out.
I got it to work again, but it is not a satisfying fix. 🙂 I noticed that the commit it was trying to deploy was an older one on the main branch. That commit actually WAS using the cache statement incorrectly. I switched the branch that Railway was using for deployments away from main, did a deployment, and then switched back to main. Now it shows the most recent commit against main and the deployment works.
I'm not sure how or why it got into that state, but it is fixed for now. 🤷♂️