Deploying with docker gives "Cache mounts MUST be in the format --mount=type=cache,id=<cache-id>"
This works when I deploy these dockerfiles on an ecs container (via ecr)
I don't really need to use Docker on railway, but i would prefer not to remove / rename these dockerfiles, so if possible can you disable autodetecting Docker?
Solution:Jump to solution
You would need to either remove or rename them, or update your dockerfile accordingly
42 Replies
Project ID:
32495aae-4b01-4a90-badf-1d53d394b8cd32495aae-4b01-4a90-badf-1d53d394b8cd
Solution
You would need to either remove or rename them, or update your dockerfile accordingly
do you know why these docker files don't work on railway but they work on ECS?
because the cache mounts must be in the format --mount=type=cache,id=s/<serviceId>
yeah but why?
that's how railway expects them
is this documented somewhere
ok, if i set a railwy config, will that supersede wahtever is automatically selecting this Dockerfile?
there is no way to disable the auto detection of the Dockerfile
they would need to be moved elsewhere, renamed, or removed
yeah, don't really want to change our prod setup just to see if railway works for us :/
you could always create a branch that has the applicable changes on the Dockerfile for testing on Railway
yeah i just think the named Dockerfile would ideally be where our production build lives. Feels like there should be a way to turn this off
do you see anything wrong with this part of the dockerfile vs what railway is expecting?
i am still getting the same error
is that your service id?