[Plugin] CA Application Auto Update

[exist2resist 2]

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. 

[eagle470 7]

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? 

[Squid 3153]

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.

[muwahhid 7]

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.

 

[uiuc_josh 0]

Haha, thanks Squid. Now what excuse am I supposed to use to be on the computer on the weekend?

 

Thanks again,

J

[tjb_altf4 118]

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

 

[BitAdept 0]

I've run some one-off containers from the command line that are auto-named by docker. Even after removing the container or using the --rm option they still show up in the notification of auto-updated containers. I've done a little looking but I'm unable to figure out how they're getting included in the notifications. Any idea how I can fix this?

[Strix 0]

Hello, 

 

I've been having an issue where containers are disappearing when auto update updates them.  Oddly enough I didn't have this issue before I reset my entire unraid and started from scratch so I have absolutely no idea what I've done differently here.  After hours of trying to find something on the forums and trying to figure out why it's doing this I just can't seem to find a solution.

 

Looking at the logs, autoupdate doesn't seem to run into any issues, yet the container gets removed the docker tab and the container folder stays in the appdata folder and I have to go back to "previously installed apps" to re-install it again.

 

Quote

Feb 19 04:00:01 Asterix Plugin Auto Update: Checking for available plugin updates
Feb 19 04:00:09 Asterix Plugin Auto Update: Community Applications Plugin Auto Update finished
Feb 19 04:00:56 Asterix kernel: mdcmd (51): spindown 2
Feb 19 04:15:02 Asterix Docker Auto Update: Community Applications Docker Autoupdate running
Feb 19 04:15:02 Asterix Docker Auto Update: Checking for available updates
Feb 19 04:15:29 Asterix Docker Auto Update: Stopping netdata
Feb 19 04:17:01 Asterix Docker Auto Update: Installing Updates for netdata
Feb 19 04:24:52 Asterix Docker Auto Update: Restarting netdata
Feb 19 04:24:52 Asterix Docker Auto Update: Community Applications Docker Autoupdate finished
Feb 19 04:31:59 Asterix root: /etc/libvirt: 920.1 MiB (964808704 bytes) trimmed on /dev/loop3
Feb 19 04:31:59 Asterix root: /var/lib/docker: 8.6 GiB (9174114304 bytes) trimmed on /dev/loop2
Feb 19 04:31:59 Asterix root: /mnt/cache: 387.5 GiB (416058400768 bytes) trimmed on /dev/sdc1
Feb 19 04:40:05 Asterix root: Fix Common Problems Version 2021.02.18
Feb 19 04:40:37 Asterix root: Fix Common Problems: Other Warning: Mover logging is enabled

 

 

 

[DarkKnight 5]

For the second week in a row, the vast majority of my containers that are set to update late Sunday night using this plugin are just missing entirely on Monday morning. What steps can I take to track down why this is happening?

[Shonky 1]

I'm getting a wierd double up Crashplan Docker. It names it "0" too. I definitely don't have two dockers and there's no old containers. Also strangely it's supplying the gotify icon for the image. I do have the gotify docker running too. Any ideas?

 

[ShortBusHero 0]

On 3/1/2021 at 12:21 PM, DarkKnight said:

For the second week in a row, the vast majority of my containers that are set to update late Sunday night using this plugin are just missing entirely on Monday morning. What steps can I take to track down why this is happening?

On 2/19/2021 at 2:51 PM, Strix said:

Hello, 

 

I've been having an issue where containers are disappearing when auto update updates them.  Oddly enough I didn't have this issue before I reset my entire unraid and started from scratch so I have absolutely no idea what I've done differently here.  After hours of trying to find something on the forums and trying to figure out why it's doing this I just can't seem to find a solution.

 

Looking at the logs, autoupdate doesn't seem to run into any issues, yet the container gets removed the docker tab and the container folder stays in the appdata folder and I have to go back to "previously installed apps" to re-install it again.

 

 

 

 

@Squid I've begun noticing this issue as well. Was especially noticeable when SWAG didn't spin back up after updating.

[kennymc.c 3]

I noticed (probably since the 6.9 update) that previously deleted port mappings of docker containers reappear after an update. This causes some containers to no longer start because other containers are already using these ports. Is there any way to prevent this?

[Squid 3153]

5 minutes ago, kennymc.c said:

probably since the 6.9 update

Since forever actually

 

You have to manually edit the applicable file within /config/plugins/dockerMan/templates-user and remove the line <TemplateURL>....</TemplateURL>

[kennymc.c 3]

1 minute ago, Squid said:

Since forever actually

 

You have to manually edit the applicable file within /config/plugins/dockerMan/templates-user and remove the line <TemplateURL>....</TemplateURL>

Thanks, never noticed this before. I probably reinstalled a previously manually configured container with a ca-template version.

[thespooler 3]

"Do not overlap with autoupdate"

 

What does this line mean?  The plugin is called Auto Update, the tabs say Auto Update, so what does autoupdate refer to? Is there some unraid setting I'm not aware of?  If this is suggesting don't configure Plugin and Docker auto update frequency at the same time, does that mean they both can't run daily for example?  Or in fact, they can both be set to Daily, just at different times, in which case, wouldn't the message be more informative if displayed under the scheduled time?  Perhaps "Do no overlap with plugin schedule" would be more clear?

Edited March 26 by thespooler

[Squid 3153]

Must've been in an altered state when I wrote that