You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue I often see with automated self-updating containers is that many package maintainers don't design proper stateless containers and often an auto-updater like Ouroboros and Watchtower two very unsafe options, in my opinion, have zero awareness of the status of the updated container.
If Diun could possibly check if the container was running and healthy if health-checks are available of course, and then ensure that the replaced updated container reaches a healthy state before considering the upgrade to be complete.
This could be done with a combination of backing up the old container image with one of the functions docker has and then restoring the old image when the newer one turns out faulty.
The text was updated successfully, but these errors were encountered:
Leopere
changed the title
FeatureRequest: In regards to a container has a healthcheck and the update function
FeatureRequest: In regards to a container having a healthcheck and the update function
Jun 10, 2019
Like I said in #1, unlike other tools like WatchTower, Diun is not intended to update containers but only to send notifications when an image is updated on a registry.
On Mon, Jun 10, 2019 at 8:46 AM CrazyMax ***@***.***> wrote:
Like I said in #1 <#1>, unlike
other tools like WatchTower, Diun is not intended to update containers but
only to send notifications when an image is updated on a registry.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=AAIE2VWJEBBXMDZHJWOBCULPZZEJNA5CNFSM4HWQKPO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJYZUA#issuecomment-500403408>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIE2VS3HWHGGR45C5LCQ7LPZZEJNANCNFSM4HWQKPOQ>
.
The issue I often see with automated self-updating containers is that many package maintainers don't design proper stateless containers and often an auto-updater like Ouroboros and Watchtower two very unsafe options, in my opinion, have zero awareness of the status of the updated container.
If Diun could possibly check if the container was running and healthy if health-checks are available of course, and then ensure that the replaced updated container reaches a healthy state before considering the upgrade to be complete.
This could be done with a combination of backing up the old container image with one of the functions docker has and then restoring the old image when the newer one turns out faulty.
The text was updated successfully, but these errors were encountered: