Skip to content
Digest-pinned GHCR image: empty-service setup and deployment triggers
richbobdee
OP

a month ago

I’m preparing an isolated, stateless experiment using a public GHCR image pinned as repository@sha256:.

Can you confirm:

  1. Does Railway accept and preserve digest-pinned GHCR references, including an OCI image index containing a linux/amd64 image and an attestation?
  2. Can I create an empty project/service, configure its settings, and verify zero deployment attempts before attaching the image?
  3. For that workflow, what exact action initiates the first deployment—saving the image source or applying staged changes with Deploy?
  4. Is there any supported way to prevent Railway-initiated deployments during a 60-minute test? Your deployment reference says these cannot be opted out of.

The experiment has not been authorized or started.

$10 Bounty

4 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


Anonymous

a month ago

AI-assisted answer; I checked the current Railway documentation and its public moderator response to a related digest-pinning question. I did not create a Railway project or run a deployment.

  1. For a public GHCR image, Railway supports Docker Image sources, and a Railway moderator has explicitly confirmed that the dashboard accepts a digest reference in the form ghcr.io/NAME/REPO@sha256:DIGEST. The current docs describe registry sources and tag-based updates, but do not document the specific OCI-index-plus-attestation case. I would treat support for that exact im

Anonymous

a month ago

Clarification: OCI-index-plus-attestation support is undocumented; test the exact GHCR image. Empty Service lets you confirm zero deployments. Saving the image stages config; Deploy starts it. Disable Image Auto Updates. Host migrations remain mandatory; a 60-minute no-redeploy guarantee is unavailable. AI-assisted. Docs: https://docs.railway.com/deployments/staged-changes ; https://docs.railway.com/deployments/image-auto-updates


richbobdee
OP

a month ago

Thank you for the detailed response and documentation references.

Before closing this thread, I would appreciate confirmation from Railway staff on the following points:

  1. Digest-pinned OCI image: Does Railway support a public GHCR image referenced by ghcr.io/NAME/REPO@sha256:DIGEST when the digest identifies an OCI image index containing a linux/amd64 image and an attestation? Will Railway preserve the exact digest reference rather than resolve it to a mutable tag?

  2. Empty-service preparation: Can I create an empty Railway project/service, configure its settings, and verify that no deployment attempts have occurred before attaching the image?

  3. First deployment trigger: Please confirm that saving the Docker image source only creates staged changes and that the first deployment begins only when I explicitly select Deploy.

  4. Platform-initiated deployments: I understand that Image Auto Updates can be disabled, but Railway-initiated deployments, including host migrations, cannot be opted out of. Is there any supported mechanism to prevent these during a strictly limited 60-minute experiment?

The proposed experiment is isolated, stateless, limited to a maximum expenditure of $10, and will use no production database, volume, or connected production services.

No resources have been created, and the experiment remains unauthorized.

I am seeking confirmation of the platform's behavior before deciding whether the experiment can safely proceed.

Thank you.


ishusinghse

a month ago

We’re interested in checking the documented behavior for digest-pinned GHCR images and deployment triggers without starting a production deployment. Is this bounty still open for a documentation-backed answer?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...