4 months ago
I have two environments each with two services, each deployed from Docker images published to GHCR. In my staging environment, the tag is set to main; in my production environment it is set to latest. Auto update is set to any time.
Three of these services work as expected (although the update detection interval is a bit slower than you’d really want for CD), but one (latest tag) constantly detects updates to the image and redeploys the same image. I have tried disconnecting from the image, with and without the latest tag, and the issue persists. I built the production environment by copying from the staging environment. I have not tried deleting and recreating the service. If I disable the auto-update functionality, the 'update available' notification persists.
I suspect the solution I go with will be hitting the CLI from GitHub Actions, due to the requirement to redeploy as soon as a build has completed. But nonetheless I think this may be a bug in your auto update detection logic.
Many thanks!
Attachments
4 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
Hi there,
Could you please share a link to the registry where the image is so we can investigate?
Best,
The Railway Team
Status changed to Awaiting User Response Railway • 4 months ago
4 months 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 • 4 months ago
3 months ago
Sorry for not coming back to you on this. Just to close things off: I ended up abandoning the auto-update logic in favour of running railway redeploy from GitHub Actions. This is much better as I have control over when the deployment happens.
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved tttc6 • 3 months ago