Exception: Updates between multiple major versions and downgrades are unsupported. Error maybe in Database

wwe · November 18, 2023, 8:24pm

this topic has bee discussed often in the past please use search.

here are two reference I found useful in the past

github.com/nextcloud/docker

Adding feasibility check for updates before replacing the nextcloud files

opened 12:33PM - 23 Jan 19 UTC

closed 08:20PM - 09 Jul 23 UTC

SnowMB

enhancement image

I'm creating this issue to collect all the other issues related to broken update…s that try to skip a major release. Nextcloud does not support skipping a major release while updating. So going from `13->15` will not work without including version 14: `13->14->15.` The problem is, that the entrypoint script correctly detects that the image version is greater, but does not check if the upgrade is feasible. So it overwrites the Nextcloud files (including `version.php`) and does not fail until running the occ upgrade command `run_as 'php /var/www/html/occ upgrade'`. Upgrading fails and the container exits, but the user can't go back to his initial state because the Nextcloud source files are already replaced. He also can't trigger a proper update from `13->14` because the upgrade detection is broken (`version.php` now falsely claims version 15). #597 in my opinion does not enough, but is a good start to at least document that Nextcloud might break when updating. However a check should be introduced to protect the Nextcloud install in that case. I think it is no problem, that running the new containers fails, but the Nextcloud instance should be unharmed. related issues: #616 #605 #585 #722