TL;DR Upgrade path for Nextcloud and MariaDB container versions to get to :latest?
Hi all, I’ve got a question I just want a little more clarification on, mostly concerning container tags.
I have a LSIO Nextcloud container that uses a LSIO MariaDB backend. I take weekly tar backups of the Docker volume mounts (/config inside the containers) of this and other containers. I thought everything was going on great, but then “something went terribly wrong”.
I accidentally removed the wrong directory, unrecoverably. When I went to restore from backups, I found that the most recent one was 2022-03-30, six months ago! I restored that data, but the combination of the new container version (using :latest) and older volume mount caused internal Nextcloud errors that I didn’t find any easy way of rectifying.
I decided to try pulling the container tags that were published six months ago from LSIO’s Docker Hub (kudos for keeping those around, btw) for both MariaDB and Nextcloud.
What would be the best sequence to pull new images and step through the upgrades? Or what should I be looking for in the Dockerfiles as clues to which ones are needed in the upgrade path?
From StackOverflow, I found a way to list all the tags in Dockerhub for each registry (http s://stackoverflow.com/questions/28320134/how-can-i-list-all-tags-for-a-docker-image-on-a-remote-registry).
23.0.3-ls177 <------ Current version, working app
23.0.3-php8 <------- I can skip PHP8, since I’m pretty sure I’ve been on v7 this whole time
10.5.13 <--------- Current image for working container
Thank you for any help you can provide.