21 days ago
Hi Railway Team,
We have connected our Railway services to Docker images hosted in GitHub Container Registry (GHCR). The images are private, and we have configured the appropriate GitHub token for authentication.
Yesterday, we pushed updates to the Docker images, but the services did not automatically redeploy. This issue has now occurred twice.
One observation that might help with debugging: we noticed that the Docker image was pulled once, but subsequent pushes did not trigger a redeployment.
Could you please help us understand why the redeployment is not being triggered and whether there is any additional configuration required for private GHCR images?
Thank you for your support.
10 Replies
16 days ago
For instant image deployments, you would need to call the CLI to update the image tag.
railway link —workspace $WORKSPACE_ID —environment $ENVIRONMENT_ID —project $PROJECT_ID
railway env edit —service-config $SERVICE_ID "source.image" nginx:1.29.4If I have setting applied like this, why do I need to call the cli ?
Attachments
ghcr.io//:staging <- This is what I entered as my source image.
Now, Whenever I run my github action cli for staging, It creates a new image and move to the staging tag to that image.
Earlier, it was working fine, the service was getting redeployed automatically… but past two weeks It is not.
I have to login into railway manually, going to the service, click on re-deploy everytime.
16 days ago
Immediately is not immediately unfortunately.
16 days ago
It could be several hours.