mirror of
https://github.com/moghtech/komodo.git
synced 2026-03-09 07:13:36 -05:00
"Update Available" flag missing after running "Global Auto Update" procedure #548
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/komodo#548
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dlhall111 on GitHub (Sep 1, 2025).
I have alerts setup to send a message when either an update is automatically applied or when one is available but not automatically applied and have noticed that, about 50% of the time, those that are not set to automatically apply an update do not get the "Update Available" flag applied even though an alert was generated for an update being available. If I "Pull Images" manually then it will set the "Update Available" flag.
Has this already been reported (didn't see any similar issue filed) or is there something amiss with my configuration perhaps? Since sometimes it does set the flag and I configured "Global Auto Update" per the documentation I'm assuming this may be a bug. Note: As far as I recall I never had this issue for stacks where I had "Poll for Updates" toggled but not "Auto Update" prior to when the switch to "Global Auto Update" was made.
@mbecker20 commented on GitHub (Sep 1, 2025):
The known issue with this is when using images explicitly prefixed with
docker.io/. If this is the case for you, then updating to just released 1.19.2 should fix the issue. Otherwise, could you give some information about which images are not working?@mbecker20 commented on GitHub (Sep 1, 2025):
Oh, hm, I think I do know the issue actually. Komodo will also auto prune images, this must be clearing the images with updates and removes the indicator that that are waiting. You can verify this by disabling auto prune on this server (under server config)
@dlhall111 commented on GitHub (Sep 1, 2025):
@mbecker20 I think you nailed it, I totally forgot about having auto-prune enabled! I'll disable it and monitor for a while and if there are any re-occurrences I'll reopen with more info/logs. Thanks!
@hermetic-charm commented on GitHub (Sep 14, 2025):
I am also having this issue, before I came here figured out pruning was happening somehow because I noticed when the update tag was shown I could see the unused images under the server resources and the tag would stick around for a day. But the next day after the update tag had disappeared, I checked again, and the new images were gone.
I came here because I couldn't figure out where the auto-prune is being set and then found this issue. You mentioned its under server config, but where exactly? I double checked my compose.yaml and my environment file and don't have anything set for pruning. I don't have a config toml defined. I checked the documentation/examples and the only reference in any of the configs I saw was about pruning stats and alerts. Is auto-prune on by default, and if it explicitly needs to be disabled where/how can I do that?
@mbecker20 commented on GitHub (Sep 14, 2025):
@hermetic-charm This is referring to the Server Config in the GUI
@hermetic-charm commented on GitHub (Sep 14, 2025):
Ah perfect! Thank you! I just started using Komodo recently and hadn't found that section in the gui yet. That should do the trick, and I'm scheduling a weekly image prune now with procedures. This should help with gotify yelling at me repeatedly for the same image updates every day until I get to them. Thanks again, really loving komodo :)