25 days ago
Hello!
My Railway service ai-copy-editor-bot cannot access its attached Volume.
Project: determined-beauty
Environment: production
Region: US East (Virginia)
The Volume ai-copy-editor-bot-volume is attached with mount path /data, but the application reports:
SQLite parent directory does not exist: /data
The Volume and service are in the same region. The service has one replica, and the SQLite database URL points to /data/ai_copy_editor.db.
Could you please check why the Volume is not mounted inside the running container?
Thank you!
3 Replies
25 days ago
The volume's mount path is saved as /data followed by a trailing space, so it is mounted at a directory literally named "/data " rather than /data, which is why your app can't find /data. Open the volume's settings, re-enter the mount path as /data with no trailing space, and apply the change so the service redeploys with the volume at the correct path.
Status changed to Awaiting User Response Railway • 25 days ago
Railway
The volume's mount path is saved as `/data` followed by a trailing space, so it is mounted at a directory literally named "/data " rather than `/data`, which is why your app can't find `/data`. Open the volume's settings, re-enter the mount path as `/data` with no trailing space, and apply the change so the service redeploys with the volume at the correct path.
25 days ago
Thank you. I checked the mount path again.
The Railway UI and RAILWAY_VOLUME_MOUNT_PATH both display /data.
However, the application diagnostics show:
- parent_exists=False
- parent_is_dir=False
- parent_is_mount=False
- effective_uid=0
- write_probe=NotADirectoryError
The volume is attached to the correct service and environment, and both are in US East.
Could you please confirm whether the stored mount path contains a trailing space or another hidden character, and advise how to correct it without deleting the existing volume?
The application still cannot access /data.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
Yes, we re-checked it just now: the stored mount path on that volume is still /data followed by a trailing space. The dashboard and the variable don't make the space visible, which is why both look like /data.
You can fix it without deleting the volume by updating only the mount path, either in the volume's settings (clear the Mount path field completely, type /data, then apply the change) or with the CLI: railway volume update --volume ai-copy-editor-bot-volume --mount-path /data. The volume and its data stay the same. The next deployment mounts it at /data.
Status changed to Awaiting User Response Railway • 25 days ago
18 days 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 • 18 days ago