Right way of upgrading Docker AIO?

[yossis1]

I’m currently running Nextcloud 28.0.3 \ Nextcloud AIO v8.0.0 and trying to figure out the right way to upgrade.
to my understanding, there are two possibilities:
A. pull an updated image from docker hub and run it
B. using the AIO interface auto update

To my understanding I have to upgrade one major release at a time (starting with the last release of 28).

my questions:

1. Which of options A or B is correct? are both valid ways to upgrade?
2. In the case of upgrading with method A, I should pull old images to make sure that I don’t jump versions, how do I do that?
3. In the case of upgrading with method B, will the auto updater not jump versions? should I just let it do its thing or is there something I need to do due to my old version?

[sven1234]

“The right way” is to let AIO upgrade itself. Yet that bases on the assumption that it does so continuously. How come yours got stuck at 8.0?

[vawaver]

Check my post here - it could help.

Nextcloud AIO v10.1.1 - Apache Will Not Start

I have updated my Nextcloud AIO to v.10.1.1 few minutes ago and let me share my experience how to solve some troubles. Here’s how I typically update my Nextcloud AIO setup, along with some tips to handle potential issues during the process. Stopping and Recreating Containers: I start by using the local Nextcloud AIO interface to stop all containers. Then, I log into Portainer and delete all stopped containers except for the mastercontainer. After deleting the containers, I allow the system …

[szaimen]

Hi, here is the official documentation on the topic: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

[yossis1]

I don’t know? does it auto updates? I just didn’t touch mine for awhile.

regarding the two other comments:
I read both the official documentation and the thread attached before posting my questions.
both do not give me an answer whether it is safe to update while not being on the one to last release.
I guess that using the AIO interface for upgrades is the right way instead of manually messing with containers,
but, the behavior of the updater isn’t clear to me, I can assume that it will do 28.0.3>to whichever is last 28> then last 29> last 30> latest 31.
I don’t want to assume tho so my question is: is that what it’ll do?

[szaimen]

The easiest was is to enable daily backups with container updates now via the aio interface which will take care of updating all the components regularly and should bring you back up-to-date in a few days.

[yossis1]

OK, with the help of the commenters here I figured it all out and I’m writing for other people who might wonder about this in the future:

1. regarding auto updates which the commenters mentioned: I read that the AIO system will auto update only if you set a backup location in the AIO interface. I didn’t and that’s why mine is outdated. The backup job also triggers an update job.
2. when upgrading with the AIO interface, which is the right why to upgrade, it will indeed upgrade one version at a time.
   My AIO jumped from 8.0.0 to 11 something but Nextcloud itself only went from 28 to 29.
   now, on 29, it claims that its running the latest version which is false but my guess is that an update check hasn’t been triggered yet and theres no manual option.

Thanks everyone!