a month ago
Is there a supported platform mechanism to provision an existing Railway persistent volume for a service that must remain non-root UID/GID 10001?
The runtime mount is owned by 0:0 with mode 0755, so the non-root process cannot write. Build-time ownership changes do not apply to the later runtime mount. We need private writable storage for SQLite while preserving the existing volume contents.
The documented RAILWAY_RUN_UID=0 approach does not meet our deployment constraint. We cannot run the application or a startup helper as root, use mode 777, or recreate the volume. The public volume settings we checked do not expose UID/GID, owner or ACL configuration.
Can Railway provision ownership 10001:10001 with private directory permissions, provide an equivalent supported access mechanism, or confirm that this is currently unsupported? Please point to the supported configuration or operator provisioning path.
This is a general platform-capability question. No project, service, volume, deployment, domain, credential or account identifiers are included or attached.
3 Replies
a month ago
This isn't supported today. Volumes are mounted into the container as root, and there's no volume setting, service variable, or staff provisioning path that sets the mount's owner UID/GID, permission mode, or ACLs. The only documented way to get write access to the mount is RAILWAY_RUN_UID=0, which runs the process as root, so it doesn't fit your constraint.
The variable controls which user the process runs as. It doesn't change who owns the volume mount, and we have no option that keeps a 10001:10001 process and also hands it a privately owned, writable mount. See Using Volumes for the documented permissions behavior.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
This isn't supported today. Volumes are mounted into the container as root, and there's no volume setting, service variable, or staff provisioning path that sets the mount's owner UID/GID, permission mode, or ACLs. The only documented way to get write access to the mount is `RAILWAY_RUN_UID=0`, which runs the process as root, so it doesn't fit your constraint. The variable controls which user the process runs as. It doesn't change who owns the volume mount, and we have no option that keeps a 10001:10001 process and also hands it a privately owned, writable mount. See [Using Volumes](https://docs.railway.com/volumes) for the documented permissions behavior.
a month ago
Thanks. Our deployment constraint excludes root for both the application and startup helpers. Could a Railway team member review this platform-capability question and confirm whether supported platform-side provisioning of an existing volume can provide private write access for UID/GID 10001? If no compatible mechanism exists, please confirm that this combination is unsupported. We will keep the application unactivated while this remains unresolved. This is the same general question; no private resource details or attachments are needed.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We can confirm this combination is currently unsupported. Volume mounts are provisioned owned by root with mode 0755, and there is no volume setting, service variable, API field, or operator-side provisioning step that sets a mount's owner UID/GID, permission mode, or ACLs on an existing volume.
RAILWAY_RUN_UID only changes the user the process runs as, not who owns the mount, so there is no supported mechanism today that keeps both the application and any startup helper at 10001:10001 while giving it private write access to the volume.
Status changed to Awaiting User Response sam-a • about 1 month ago
24 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 • 24 days ago