On a standard Nextcloud AIO installation, is there a way to hold Nextcloud at version 24 but still be able to install minor version updates?
Reason I ask is as a policy we don’t update to “dot-oh” versions of anything. Usually we wait until at least the 2nd patch. Normally I would just hold off for a bit, but I had a patch (or at least container updates) pending for NC 24 at the time 25 came out. I’d like to I stay up to date on 24, but I think it may go to 25 instead if I try up update.
Another possibility since recently is to use the build time tags which will disable container updates completely. However you will then need to update AIO on your own e.g. by switching the tag regularly as this cannot be done from AIO’s side then anymore.
See e.g. this tag: Docker Hub
Sorry, I think I’ve missunderstood the question. AIO will always use the latest available release that was pushed to docker hub. So whatever is included in the container will get used. However before restarting you can check the changelog and/or indeed the main branch at all-in-one/Dockerfile at main · nextcloud/all-in-one · GitHub
Yes, that should work. However you will obviously need to change the image tag and update the mastercontainer via docker-compose as the mastercontainer will no longer be able to update itself. Also you will miss dependency updates as well when witholding container updates but I suppose this is already known to you.