exist2resist 2 Posted November 3, 2020 Share Posted November 3, 2020 Auto Update doesn't spin up new instances of a few containers I have after an update attempt. The image is updated, but then they just disappear and aren't spun back up again. I can bring them back up manually by using the User Templates section in the Templates drop down. So not quite sure why Auto Update wouldn't spin them up again even though the template still exists for the containers. If I update the containers manually it works just fine. Also note worthy these are my own unraid templates, https://github.com/Exist2Resist/docker-templates/tree/master/exist2resist The containers that don't spin back up are Collabora, and Gitlab-CE after updates, all the other ones update fine. Quote Link to post
eagle470 5 Posted November 5, 2020 Share Posted November 5, 2020 So this is an interesting post regarding auto updates for docker with the new paid limits on Docker Pulls. What is doing to be done by both this app and UnRAID to address this? Quote Link to post
Squid 2894 Posted November 6, 2020 Author Share Posted November 6, 2020 20 hours ago, eagle470 said: So this is an interesting post regarding auto updates for docker with the new paid limits on Docker Pulls. What is doing to be done by both this app and UnRAID to address this? Every check for an update to a container counts as a pull. Every update performed counts as a pull. To hit the 100 / 6 hours, you would have to have 50 containers all showing an update and all of them you decide to update. Unlikely to happen (but still possible). Unraid itself has a maximum check rate of 4 times / day (every 6 hours), and this plugin (unless you configure it with a custom cron expression) has a maximum check rate of every 24 hours. Of course (as has been noted previously in this thread), there is zero reason to enable Unraid checking for updates (Settings - notification settings) if you are using this plugin. Quote Link to post
muwahhid 7 Posted December 6, 2020 Share Posted December 6, 2020 I have a Compose of 18 Mailcow containers. So, in the yml file, all the latest versions, but the plugin shows that you need an update. How to get rid of it? I've tried to disable the update check in the plug-in settings, but not all containers come out there. Quote Link to post
uiuc_josh 0 Posted December 23, 2020 Share Posted December 23, 2020 Haha, thanks Squid. Now what excuse am I supposed to use to be on the computer on the weekend? Thanks again, J Quote Link to post
tjb_altf4 89 Posted December 24, 2020 Share Posted December 24, 2020 Sorry if it has already been raised as a request, but could CA Auto Update be updated to replicate (or trigger) the network rebuild functionality as added to Unraid as per this thread? On 2/14/2020 at 3:47 PM, bonienl said: When you go to the Docker page and update the "vpn" container, it will automatically update all other containers which depend on it. On 2/15/2020 at 8:02 AM, bonienl said: No, it doesn’t work together with the CA auto updater Quote Link to post
231 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.