Auto Updates -> Poll For Updates: downloads the image instead of just notifying #1158

New Issue

2026-03-22T17:12:31-05:00

GiteaMirror commented

2026-03-22 17:12:31 -05:00

Originally created by @wouldntyouknow on GitHub (May 9, 2025).

Hi!
Don't know if this a bug or it's intended (but then it's kind of confusing), but if I enable "Poll For Updates" - while other update related features remain disabled - new versions of the container images within the stack are automatically downloaded (can be seen under Server resources -> Images). It even states "Check for updates to the image on an interval." which implies only checking, but no downloading.
I really love the subtle up arrow in the stack list indicating the possibility of a container update but I did not expect to actually download the new image - I would expect that with the next update related option "Auto Updates" being enabled.
It's pretty much the industry standard to have at least 2 update related options, one being checking for updates and the other is downloading them too. I understand for deployment here we have a third "layer" as well which is great.
If this is not a bug, would it be possible to change the update behavior of "Poll for updates" or add additional update related "layer" so the first option could only relate to checking and notifying via the up arrow in the stack list, without downloading anything?

Originally created by @wouldntyouknow on GitHub (May 9, 2025). Hi! Don't know if this a bug or it's intended (but then it's kind of confusing), but if I enable "Poll For Updates" - while other update related features remain disabled - new versions of the container images within the stack are automatically downloaded (can be seen under Server resources -> Images). It even states "Check for updates to the image on an interval." which implies only checking, but no downloading. I really love the subtle up arrow in the stack list indicating the possibility of a container update but I did not expect to actually download the new image - I would expect that with the next update related option "Auto Updates" being enabled. It's pretty much the industry standard to have at least 2 update related options, one being checking for updates and the other is downloading them too. I understand for deployment here we have a third "layer" as well which is great. If this is not a bug, would it be possible to change the update behavior of "Poll for updates" or add additional update related "layer" so the first option could only relate to checking and notifying via the up arrow in the stack list, without downloading anything?

GiteaMirror closed this issue

2026-03-22 17:12:31 -05:00

GiteaMirror commented

2026-03-22 17:12:33 -05:00

@hrabbach commented on GitHub (May 14, 2025):

Thanks, I'm glad I'm not the only one seeing this - in my case, the incessant pulling of new images actually caused problems with the DockerHub ratelimiting, even though I assumed I was only doing version checks and nothing more.

@hrabbach commented on GitHub (May 14, 2025): Thanks, I'm glad I'm not the only one seeing this - in my case, the incessant pulling of new images actually caused problems with the DockerHub ratelimiting, even though I assumed I was only doing version checks and nothing more.

GiteaMirror commented

2026-03-22 17:12:33 -05:00

@mbecker20 commented on GitHub (Aug 28, 2025):

Yes this is how auto update works, and now no longer occurs with such frequency in the background. The auto update process should be triggered using Procedure scheduled daily or weekly: https://komo.do/docs/resources/auto-update

@mbecker20 commented on GitHub (Aug 28, 2025): Yes this is how auto update works, and now no longer occurs with such frequency in the background. The auto update process should be triggered using Procedure scheduled daily or weekly: https://komo.do/docs/resources/auto-update