a month ago
I have a successful Dockerfile deployment uploaded through the CLI on Hobby. The deployment was stopped after a finite command, and canRollback is true.
I changed the service startCommand, then called deploymentRedeploy(id, usePreviousImageTag: true). The new deployment retained the same provider imageDigest, but its serviceManifest and runtime used the original startCommand. I stopped and removed that diagnostic deployment and restored the service settings.
- Is there a supported API operation that applies a new startCommand/environment configuration to the retained source-built image without triggering a source rebuild? If so, which operation and parameters should be used?
- For security scanning, is there a supported way on Hobby to export or inspect the exact Railway-built image? BuildKit's exported OCI manifest digest differs from deployment.meta.imageDigest. How can the image's config/layer correspondence be verified?
I want to retain private source/images and stay on Hobby. This is a platform deployment question; no application debugging or account access is requested.
1 Replies
a month ago
The CLI railway redeploy picks up updated service configuration (start command, environment variables) but triggers a fresh build from the same source, so it does not skip the rebuild. The API's deploymentRedeploy with usePreviousImageTag: true retains the image but, as you found, also retains the original deployment's configuration. There is no supported operation that applies new service-level configuration to a previously built image without a source rebuild.
For inspecting the built image, we don't provide access to pull or export Railway-built container images. You can examine the running container's filesystem via the service's Console tab in the dashboard, railway ssh, or SCP/SFTP against ssh.railway.com, but there is no way to export the full OCI image for offline scanning.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago