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. 

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? 

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.

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.

 

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

 

Thanks again,

J

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

 

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?

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?

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?

 

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.

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?

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>

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.

"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, 20215 yr by thespooler

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

Hello,

 

Sorry if it has been asked but I've discovered an error in my Auto Update Application, at the bottom:

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 100

 

The line is:

  foreach($containers as $container) {

 

Thanks.  I'd guess that you have no docker apps installed at all.

When this app runs, plugins aren't updated and I only get this in my log:

 

May 26 00:00:01 unraiden Plugin Auto Update: Checking for available plugin updates
May 26 00:00:07 unraiden crond[1933]: exit status 255 from user root /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1

 

I'd need to see your diagnostics 

What's the output if you enter this in:

/usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php

echo $?

 

7 minutes ago, Squid said:

What's the output if you enter this in:

/usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php

echo $?

 

bash-5.0# /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php

Warning: date_diff() expects parameter 2 to be DateTimeInterface, bool given in /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php on line 85

Fatal error: Uncaught Error: Call to a member function format() on bool in /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php:86
Stack trace:
#0 {main}
  thrown in /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php on line 86
bash-5.0# echo $?
255

 

I manually updated the My Servers plugin then ran auto update again and now it's working. I guess it doesn't handle version numbers like "2021.05.14.1336".

What are the settings you've got for the plugin updates?

3 minutes ago, Squid said:

What are the settings you've got for the plugin updates?

 

Hi All,

 

I have been struggling to resolve a problem with the Auto Update plugin since upgrading to 6.9.0 2021-02-27 and I'm hoping someone can point me in the right direction.

 

Prior to updating, I had the Auto Update plugin updating my plugins and dockers (except Plex) once per month, however after the update, Plex started shutting down with all of the other dockers, it wasn't updated, it would just shut down.

 

Of couse there has always beena  problem with the Auto Updater not restarting dockers, but thats another issue.  I tried removing the Auto Update plugin, but the dockers would still shut down on the old schedule.  I tried reinstalling, but nothing has changed.

 

Has anyone experienced this?