a day ago
We need to run isolated local compatibility checks on the original runtime image produced by a build within Railway, without rebuilding it or modifying the existing deployment.
We have the image digest recorded in the deployment metadata, but we have not found a complete pullable image reference or a documented export method.
Does Railway allow the account owner to pull this original image or export it as an OCI artifact? If so, please specify the official way to obtain an image reference tied to the deployment digest and platform, determine the transfer size and required disk space, and identify the access or plan requirements.
We are not requesting a rebuild, a copy of the live container filesystem, or any volume data. If the original image cannot be retrieved through the account, please clarify that and the limits of availability.
If deployment identifiers are needed to investigate, please indicate an appropriate private channel for providing them. This is an information request only; we are not requesting changes to the service or its settings.
1 Replies
a day ago
We don't provide access to build artifacts. There's no self-serve way to pull a deployment's built image or export it as an OCI artifact, and it isn't something we retrieve by hand, so deployment identifiers or a digest won't change that. That's also why we can't give you a pullable reference, transfer size, or plan tier for it.
The one path that exists is the running container. You can open a shell from the service's Console tab, browse and download files from the Files panel next to it, or use railway ssh. Ordinary scp and sftp clients also work against ssh.railway.com once an SSH key is registered on your account (railway ssh keys add). The service's domain is the username, and scp -r copies whole directories.
Keep in mind that this gives you what is on the container's disk now, not the image as a layered artifact. A multi-stage build only leaves the final stage behind.
Status changed to Awaiting User Response Railway • 1 day ago