burkasaurusrex Posted June 7, 2021 Share Posted June 7, 2021 It looks like certain docker containers aren't being added to the "Docker Auto Update Settings" page, particularly containers I've added directly from Docker Hub through Community Applications. Is there a way to manually add them? Thanks! Quote Link to comment
KnifeFed Posted June 9, 2021 Share Posted June 9, 2021 On 5/26/2021 at 4:38 PM, KnifeFed said: 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". Now that there's a new update for the My Servers plugin (version 2021.06.07.1845), Auto Update errors out with the same exit status 255. I manually updated My Servers again and after that it runs fine. Quote Link to comment
burkasaurusrex Posted June 14, 2021 Share Posted June 14, 2021 On 6/7/2021 at 3:56 AM, burkasaurusrex said: It looks like certain docker containers aren't being added to the "Docker Auto Update Settings" page, particularly containers I've added directly from Docker Hub through Community Applications. Is there a way to manually add them? Thanks! Also having an issue where some containers' update path seem to get kind of corrupted? For example, in the auto update app, the repository will be listed as 'library/sha256:...' and on the docker tab, the container says the update is 'not available'? Quote Link to comment
KnifeFed Posted June 23, 2021 Share Posted June 23, 2021 A small feature request: I would love to have the option of using an exclude list rather than the current include list for which Docker containers to update, because I only have one container that I don't want to automatically update and currently I have to enable automatic updates for every new container I install. Quote Link to comment
Crashdogy Posted July 31, 2021 Share Posted July 31, 2021 installed app on the plugins side i get a error Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 100 Quote Link to comment
Squid Posted July 31, 2021 Author Share Posted July 31, 2021 Can't replicate this, but issuing a fix that should remove the error. Quote Link to comment
Thomasvt Posted July 31, 2021 Share Posted July 31, 2021 Found an issue with line 101 while applying settings; Parse error: syntax error, unexpected ';' in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 101 It's because of this line if ( ! is_array($containes) { but it should be if ( ! is_array($containes)) { Missing a ')' Quote Link to comment
Squid Posted July 31, 2021 Author Share Posted July 31, 2021 10 minutes ago, Thomasvt said: Found an issue with line 101 while applying settings; Parse error: syntax error, unexpected ';' in /usr/local/emhttp/plugins/ca.update.applications/include/exec.php on line 101 It's because of this line if ( ! is_array($containes) { but it should be if ( ! is_array($containes)) { Missing a ')' Note to self: Long weekends are NOT the time to be programming fixed (maybe) 1 Quote Link to comment
FDM80 Posted July 31, 2021 Share Posted July 31, 2021 Current message I'm getting when attempting to update. "bad file MD5" Quote Link to comment
Squid Posted July 31, 2021 Author Share Posted July 31, 2021 Missed upping the version. Try again Quote Link to comment
peter76 Posted August 8, 2021 Share Posted August 8, 2021 (edited) I'm having an issue where some Docker Containers are not listed in "Docker Auto Update Settings" - looking at "nextcloud_mariadb" which I had to update manually: => Why is "nextcloud_mariadb" not available in the list of "Docker Auto Update Settings" in the Plugin ?? => For me it seems to be a bug tower-diagnostics-20210808-1427.zip Edited August 8, 2021 by peter76 Quote Link to comment
Squid Posted August 8, 2021 Author Share Posted August 8, 2021 1 hour ago, peter76 said: For me it seems to be a bug Looka like it. I'll check it out. Quote Link to comment
local.bin Posted August 10, 2021 Share Posted August 10, 2021 Missing an LMS docker from the auto update too. Quote Link to comment
Squid Posted August 15, 2021 Author Share Posted August 15, 2021 It looks like the reason for apps being missing is that when you installed them on the template, you never entered in the docker hub URL (or manually removed it) --> CA enforces that this is present. I'm not sure exactly why that test is in there (code went in 6 years ago), but since it appears to still work, I'm going to tentatively remove it. Quote Link to comment
peter76 Posted August 17, 2021 Share Posted August 17, 2021 For me it's workin now - all Dockers are listed. Thank you for fixing! Quote Link to comment
local.bin Posted August 19, 2021 Share Posted August 19, 2021 On 8/15/2021 at 1:44 PM, Squid said: I'm not sure exactly why that test is in there (code went in 6 years ago), but since it appears to still work, I'm going to tentatively remove it. Works for me, dockers have appeared that were previously missing, thanks. Quote Link to comment
Slippin' Jimmy Posted August 22, 2021 Share Posted August 22, 2021 Would it be possible to add an option to Force update all containers, even if there isn't an update? My docker file keeps slowly filling up, and force updating all my dockers resets that. Quote Link to comment
Squid Posted August 22, 2021 Author Share Posted August 22, 2021 You should determine why its slowly filling up (eg: Container Size on the docker tab) and then fix that (eg: limit the logging, etc) Quote Link to comment
jimmy898 Posted August 26, 2021 Share Posted August 26, 2021 Hi guys, it's a nab question but I'm stuck so... how can I change the script permissions (+x) in "/boot/config/plugins/ca.update.applications/scripts/starting/"? chmod it's not working: root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# ls -l total 8 -rw------- 1 root root 748 Aug 19 21:55 zabbix-agent2.sh root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# chmod +x zabbix-agent2.sh root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# ls -l total 8 -rw------- 1 root root 748 Aug 19 21:55 zabbix-agent2.sh thanks! Quote Link to comment
itimpi Posted August 26, 2021 Share Posted August 26, 2021 5 hours ago, jimmy898 said: Hi guys, it's a nab question but I'm stuck so... how can I change the script permissions (+x) in "/boot/config/plugins/ca.update.applications/scripts/starting/"? chmod it's not working: root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# ls -l total 8 -rw------- 1 root root 748 Aug 19 21:55 zabbix-agent2.sh root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# chmod +x zabbix-agent2.sh root@xxxxxx:/boot/config/plugins/ca.update.applications/scripts/starting# ls -l total 8 -rw------- 1 root root 748 Aug 19 21:55 zabbix-agent2.sh thanks! You. can’t for security reasons no files on the /boot are allowed to have execute permissions. there are 2 workarounds that I know off: copy the file elsewhere first and then try and change the permissions. invoke by starting with the relevant shell command (e.g. bash /boot/path_to_script) Quote Link to comment
Squid Posted August 27, 2021 Author Share Posted August 27, 2021 You actually shouldn't need to change the permissions The update script runs the scripts like this /bin/bash /boot/config/plugins/ca.update.applications/scripts/starting/$containerScript This does however require that the script be a valid bash script. For python or something else your starting script then has to call python to execute the script. Quote Link to comment
jimmy898 Posted August 27, 2021 Share Posted August 27, 2021 4 hours ago, Squid said: You actually shouldn't need to change the permissions The update script runs the scripts like this /bin/bash /boot/config/plugins/ca.update.applications/scripts/starting/$containerScript This does however require that the script be a valid bash script. For python or something else your starting script then has to call python to execute the script. Thanks for the hint! Just to be sure: the script should have the very same name of the container right? So if my container name is "zabbix-agent2", the starting script should be "/boot/config/plugins/ca.update.applications/scripts/starting/zabbix-agent2.sh". Right? Quote Link to comment
Squid Posted August 27, 2021 Author Share Posted August 27, 2021 No .sh filename must be the exact name of the container 1 Quote Link to comment
KnifeFed Posted September 5, 2021 Share Posted September 5, 2021 On 5/26/2021 at 1:56 PM, KnifeFed said: 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 On 5/26/2021 at 4:38 PM, KnifeFed said: 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". On 6/9/2021 at 3:21 PM, KnifeFed said: Now that there's a new update for the My Servers plugin (version 2021.06.07.1845), Auto Update errors out with the same exit status 255. I manually updated My Servers again and after that it runs fine. Same thing now that My Servers 2021.08.25.1816 was released. Am I the only one experiencing this problem? Quote Link to comment
Squid Posted September 5, 2021 Author Share Posted September 5, 2021 Next time there's an update to MyServers I'll check it out 1 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.