anhloc Posted January 6, 2018 Share Posted January 6, 2018 As per title. Possibly have it so that when it does it for docker images, that it turns off running docker images, then updates them all, then restarts them. Quote Link to comment
Squid Posted January 6, 2018 Share Posted January 6, 2018 Valid request, but there's also 2 plugins currently available that do the same thing Advanced Buttons - Does exactly what you ask for CA Auto Update - Updates everything without user intervention on a schedule you decide. Quote Link to comment
bnevets27 Posted February 4, 2018 Share Posted February 4, 2018 Now that Advanced buttons doesn't work with 6.4 this would be a good addition/option for the GUI by default. CA Auto Update is good but I know a lot of users like to update on their own and its nice to be able to do that without clicking update 30 times. Quote Link to comment
Dephcon Posted February 5, 2018 Share Posted February 5, 2018 AB works for me... Quote Link to comment
bnevets27 Posted February 5, 2018 Share Posted February 5, 2018 It works fine for plugins but it will orphan your dockers, or so has been reported. Quote Link to comment
Ziggurat Posted February 15, 2018 Share Posted February 15, 2018 I tried AB and I lost all the docker containers except 2. Thankfully the user templates function worked to restore the containers. Quote Link to comment
bonienl Posted March 9, 2018 Share Posted March 9, 2018 unRAID 6.5.0-rc6 will have the possibility to update all containers, which have a update pending, with a single button. In addition it supports to start and stop all containers with a single button. 2 Quote Link to comment
bnevets27 Posted March 10, 2018 Share Posted March 10, 2018 Awesome! Thanks bonienl! Quote Link to comment
bnevets27 Posted March 20, 2018 Share Posted March 20, 2018 @bonienl I was kind of expecting plugins would have recieved a button to update them all also. Could that be added aswell? Quote Link to comment
Handl3vogn Posted March 24, 2018 Share Posted March 24, 2018 Love this! But one more request. When Unraid found a docker update the "check for updates" button is replaced with "update all docker" Some times there is more updates pending and I cant search for them before I have updated the dockers that already got marked as out of date. Quote Link to comment
Can0n Posted March 29, 2018 Share Posted March 29, 2018 On 1/6/2018 at 4:28 AM, anhloc said: As per title. Possibly have it so that when it does it for docker images, that it turns off running docker images, then updates them all, then restarts them. this has been added to the rc for 6.5.1 Quote Link to comment
mbc0 Posted June 25, 2018 Share Posted June 25, 2018 Should I have an update all dockers button? Quote Link to comment
JonathanM Posted June 25, 2018 Share Posted June 25, 2018 3 hours ago, mbc0 said: Should I have an update all dockers button? Do any of your dockers show update ready? Quote Link to comment
mbc0 Posted June 25, 2018 Share Posted June 25, 2018 1 hour ago, jonathanm said: Do any of your dockers show update ready? Hi yes, they do Quote Link to comment
bnevets27 Posted June 26, 2018 Share Posted June 26, 2018 Try hitting "check for updates" even though you have updates showing. I Just looked now and I had no update all button until I hit check, even though I had updates showing. Is there a way to prevent updating 1 docker, when using the update all button? Quote Link to comment
bonienl Posted June 29, 2018 Share Posted June 29, 2018 On 6/26/2018 at 9:13 PM, bnevets27 said: Is there a way to prevent updating 1 docker, when using the update all button? No, all containers are updated. Instead of using the :latest tag a container can be installed with a specific version (if supported) and prevents updates. Quote Link to comment
NAS Posted June 30, 2018 Share Posted June 30, 2018 The "Update all" in 6.5.3 works well (great work) but it is a bit unintuitive that there are scenarios where the interface is showing some/most/all containers have an update available but the update all button is not there. Quote Link to comment
bnevets27 Posted July 1, 2018 Share Posted July 1, 2018 No, all containers are updated. Instead of using the :latest tag a container can be installed with a specific version (if supported) and prevents updates.Thanks boniel. Funny how obvious something like that is if you are thinking correctly. I've used tags with specific versions before and just never made the connection to use it to prevent updates, which makes a lot of sense. 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.