Hello Railway Support, We need to preserve one verified container image across environment-variable changes on our staging service. Please confirm: 1. Does Railway support a Docker Image source pinned as `ghcr.io/OWNER/IMAGE@sha256: `? If so, what is the supported dashboard or CLI/API configuration? 2. With this digest-pinned source, do deployments triggered by variable changes retain the exact same image without rebuilding or resolving a different image? 3. Which API field identifies the registry image digest actually running? Is `deployment.meta.imageDigest` that digest, or a different Railway identifier? 4. If digest-pinned sources are unsupported, what supported mechanism guarantees the same artifact across variable changes? 5. What authentication and plan requirements apply to private GHCR images? Please provide documentation or supported configuration examples. This is an information request only. Please do not modify, redeploy, or roll back our service. Thank you.

Docker image digest pinning across environment-variable redeploys

dragonglobalai

PROOP

18 days ago

Hello Railway Support,

We need to preserve one verified container image across environment-variable changes on our staging service.

Please confirm:

Does Railway support a Docker Image source pinned as ghcr.io/OWNER/IMAGE@sha256:<digest>? If so, what is the supported dashboard or CLI/API configuration?
With this digest-pinned source, do deployments triggered by variable changes retain the exact same image without rebuilding or resolving a different image?
Which API field identifies the registry image digest actually running? Is deployment.meta.imageDigest that digest, or a different Railway identifier?
If digest-pinned sources are unsupported, what supported mechanism guarantees the same artifact across variable changes?
What authentication and plan requirements apply to private GHCR images?

Please provide documentation or supported configuration examples.

This is an information request only. Please do not modify, redeploy, or roll back our service.

Thank you.

$20 Bounty

2 Replies

Railway

BOT

18 days ago

This is a question the Railway community is better placed to answer than support: people who have already worked this out on their own projects and can tell you what actually worked.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
Keep it private and close the thread - Nothing becomes public and the thread closes.

Status changed to Awaiting User Response Railway • 18 days ago

Railway

BOT

18 days ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • 18 days ago

mayori

MODERATOR

18 days ago

Yes, I'm not sure how to configure it via CLI/API (since i'm mostly deploy via dashboard), But in the dashboard you can just set ghcr.io/NAME/REPO@sha256:DIGEST to pin the source digest
Yes (auto-updates is turned off by default)
deployment.meta.imageDigest, Yes
(sha256 digest-pinned version is supported, so I'll skip this)
You're on Pro Plan so you have access to private image feature, For GHCR, you need to add credentials in the Service Settings and Paste your GitHub Access Token there (require read:packages scope)

Welcome!