Squid Posted February 10 Author Share Posted February 10 Today's update should fix (and log what plugin is messing things up) 1 Quote Link to comment
Masterwishx Posted February 10 Share Posted February 10 17 minutes ago, Squid said: Today's update should fix (and log what plugin is messing things up) Also i set delay to "0" , i think it fixed the issue .... Quote Link to comment
Masterwishx Posted February 10 Share Posted February 10 1 hour ago, Squid said: Today's update should fix (and log what plugin is messing things up) maybe its zfsmaster that have version 2024.02.09.62 Quote Link to comment
ANIMATEK Posted February 24 Share Posted February 24 I am having trouble figuring out why my containers are not updating. Unfortunately, it is quite hard to search in this huge thread (or I don't know how). I looked around but I don't even know where the logs for the plug-in are. I am clueless. I attached my config but it is so simple I don't know what can be wrong. I also already reinstalled the plug-in. If I go to the Docker page I might see 1 or 2 that say "apply update". If I click search, almost always something comes up (I have a container that gets a new push everyday at around 8AM). The plug-in seems to not be working at all. Can someone give me hand? Quote Link to comment
Squid Posted February 24 Author Share Posted February 24 The screenshot shows your settings for plugins. Whats the Docker settings on that same page? Quote Link to comment
ANIMATEK Posted February 25 Share Posted February 25 16 hours ago, Squid said: The screenshot shows your settings for plugins. Whats the Docker settings on that same page? I think the theme is putting you off. Those are indeed the settings for Docker (check "Time to wait for graceful stop before killing", which is only in Docker) Quote Link to comment
Squid Posted February 25 Author Share Posted February 25 So you have it checking for an update every minute from 8 minutes after til 15 minutes after every hour of every day? So potentially if the check / installs happen to take longer than 60 seconds you potentially have it running 8 times concurrently Quote Link to comment
ANIMATEK Posted February 25 Share Posted February 25 2 hours ago, Squid said: So you have it checking for an update every minute from 8 minutes after til 15 minutes after every hour of every day? So potentially if the check / installs happen to take longer than 60 seconds you potentially have it running 8 times concurrently Thank you, the cron expression was completely wrong. I want it more like 0 8-15 * * * Quote Link to comment
itimpi Posted February 25 Share Posted February 25 4 hours ago, ANIMATEK said: Thank you, the cron expression was completely wrong. I want it more like 0 8-15 * * * That still seems far more frequently than necessary. I would not check more than once a day, or possibly even less frequently. Quote Link to comment
ANIMATEK Posted February 27 Share Posted February 27 On 2/25/2024 at 11:49 PM, itimpi said: That still seems far more frequently than necessary. I would not check more than once a day, or possibly even less frequently. Yeah that's true, I do get irritated when I see update available though. But in that case I could run it with AppData Backup and call it a day. I will see, thanks for the input. Quote Link to comment
jinra Posted March 14 Share Posted March 14 (edited) I'm wondering if I have something setup incorrectly. I seem to have a similar issue to @ANIMATEK These are my settings, and while my dockers "created" time does change to 6am every morning, it doesn't seem to actually update my containers and I still have "apply update" on most of my apps. It's been this way for quite a while, probably ever since I installed the tool months ago. Edited March 14 by jinra Quote Link to comment
Squid Posted March 15 Author Share Posted March 15 What happens if you manually hit apply update on one of them? Quote Link to comment
wirenut Posted March 15 Share Posted March 15 18 hours ago, Squid said: What happens if you manually hit apply update on one of them? I also have a docker that is persistent with this issue. I have posted in the docker support thread and was assured that the container is fine and this may be an unraid docker engine related problem and to post the issue there. I did this two days ago but have not yet received any feedback. Maybe my post details aren't clear? They are here if you wouldn't mind taking a look: Thanks in advance! Quote Link to comment
Arby Posted March 16 Share Posted March 16 Just wanted to put my +1 for CA Docker Auto Update to include a delay by days like the Plugin one does "Delay in days before updating applications:" Quote Link to comment
Squid Posted March 17 Author Share Posted March 17 10 hours ago, Arby said: Just wanted to put my +1 for CA Docker Auto Update to include a delay by days like the Plugin one does "Delay in days before updating applications:" Basically, in order to determine (without being the owner of the container itself), you have to pull it to be able to grab the date of it. IE: Catch 22. To determine whether its X days old and then update what you've got installed, you have to update what you have installed. Quote Link to comment
jinra Posted March 25 Share Posted March 25 On 3/14/2024 at 6:50 PM, Squid said: What happens if you manually hit apply update on one of them? It updates as expected, I usually have to update my docker containers manually by clicking "update all" from the docker page because of this. Quote Link to comment
oliver Posted April 6 Share Posted April 6 (edited) every time this runs, it fills my log up with these - pr 6 02:00:02 nas Docker Auto Update: Checking for available updates Apr 6 02:00:21 nas Docker Auto Update: Stopping heimdall Apr 6 02:00:29 nas kernel: docker0: port 8(veth383ba24) entered disabled state Apr 6 02:00:29 nas kernel: veth203f1ae: renamed from eth0 Apr 6 02:00:30 nas kernel: docker0: port 8(veth383ba24) entered disabled state Apr 6 02:00:30 nas kernel: device veth383ba24 left promiscuous mode Apr 6 02:00:30 nas kernel: docker0: port 8(veth383ba24) entered disabled state Apr 6 02:00:30 nas Docker Auto Update: Stopping wikijs Apr 6 02:00:36 nas kernel: docker0: port 1(vethc2a901a) entered disabled state Apr 6 02:00:36 nas kernel: veth3b21e64: renamed from eth0 Apr 6 02:00:37 nas kernel: docker0: port 1(vethc2a901a) entered disabled state Apr 6 02:00:37 nas kernel: device vethc2a901a left promiscuous mode Apr 6 02:00:37 nas kernel: docker0: port 1(vethc2a901a) entered disabled state Apr 6 02:00:37 nas Docker Auto Update: Installing Updates for hdd_scrutiny heimdall wikijs homeassistant Apr 6 02:05:52 nas Docker Auto Update: Restarting heimdall Apr 6 02:05:53 nas kernel: docker0: port 1(vethdf9918b) entered blocking state Apr 6 02:05:53 nas kernel: docker0: port 1(vethdf9918b) entered disabled state Apr 6 02:05:53 nas kernel: device vethdf9918b entered promiscuous mode Apr 6 02:05:57 nas kernel: eth0: renamed from veth7dd08c1 Apr 6 02:05:57 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethdf9918b: link becomes ready Apr 6 02:05:57 nas kernel: docker0: port 1(vethdf9918b) entered blocking state Apr 6 02:05:57 nas kernel: docker0: port 1(vethdf9918b) entered forwarding state Apr 6 02:05:58 nas Docker Auto Update: Restarting wikijs Apr 6 02:05:58 nas kernel: docker0: port 8(veth36d8670) entered blocking state Apr 6 02:05:58 nas kernel: docker0: port 8(veth36d8670) entered disabled state Apr 6 02:05:58 nas kernel: device veth36d8670 entered promiscuous mode Apr 6 02:05:58 nas kernel: docker0: port 8(veth36d8670) entered blocking state Apr 6 02:05:58 nas kernel: docker0: port 8(veth36d8670) entered forwarding state Apr 6 02:05:58 nas kernel: docker0: port 8(veth36d8670) entered disabled state Apr 6 02:06:05 nas kernel: eth0: renamed from veth818c2f7 Apr 6 02:06:05 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth36d8670: link becomes ready Apr 6 02:06:05 nas kernel: docker0: port 8(veth36d8670) entered blocking state Apr 6 02:06:05 nas kernel: docker0: port 8(veth36d8670) entered forwarding state Apr 6 02:06:08 nas Docker Auto Update: Community Applications Docker Autoupdate finished i assume this is normal since the containers are restarting? is there a way to suppress these log messages? Edited April 6 by oliver Quote Link to comment
Squid Posted April 7 Author Share Posted April 7 The logging of the startup has nothing to do with the plugin and happen whenever you stop / start a container. IE: no Quote Link to comment
ultimation Posted April 14 Share Posted April 14 Hiya I've been having an issue where my container "Home-Assistant-Core" disappears after update, and I keep having to reinstall it. In notices I get the message "Home-Assistant-Core Automatically Updated" - and in the syslog it seems happy Apr 13 04:00:41 Galatica Docker Auto Update: Stopping Home-Assistant-Core Apr 13 04:01:38 Galatica Docker Auto Update: Installing Updates for Home-Assistant-Core Apr 13 04:12:53 Galatica Docker Auto Update: Restarting Home-Assistant-Core Apr 13 04:12:53 Galatica Docker Auto Update: Community Applications Docker Autoupdate finished Anywhere else I should be looking for information? Thanks Quote Link to comment
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.