a year ago
Hey everyone,
I’m trying to add a volume to a Docker instance on Railway to enable persistent storage for my agents. However, I’m running into an issue where the “mount path” field rejects every input I try — the letters stay red no matter what path I enter.
I’m using a path like data/, which works fine on other deployments I have running. These other instances are code-identical, and the volume with the same mount path (data/) works there without issues.
Things I’ve tried:
• Tested various mount paths (absolute, relative, different naming schemes)
• Switched instance regions
• Made sure I’m on a Pro plan
• Compared config with my working deploys (no differences)
Still, the field refuses to accept any input. It feels like no value is currently being accepted at all, regardless of what I enter.
Is anyone else experiencing this? Could it be a UI bug or a recent regression?
Appreciate any help or pointers — thanks in advance!
3 Replies
a year ago
Okay so if i create a path with double dash so: //data it does allow it. Then after i can edit this to /data..
I am new to this i guess - so is this normal? Seems weird it only allows //data as AFAIK that is not correct is it? Would still like to know thanks for the help. I am now deploying the volumes with this so lets see if it matters or works.
a year ago
Got this sorted, was not straight forward. In the end after a lot of deployments and retries i got it to work. I am pretty sure there is some buggy things going on especially when trying to configure this on the US West servers. Was unable to deploy on there.
Can't really draft a consise bug report other than knowing that i did the same thing several times and it worked suddenly - so there is something going on. But other than that no more help on this issue it can be closed but yeah if more similar issues come in i reckon its a good idea to look at the volume deployments and if it can be streamlined/made easier.
a month ago
i see no way to add or mount a volume.