is there a way to run update.sh in such a way that it updates the mailcow instance to a specific version instead of the latest ? because right now i’m doing the git checkout on the 2025-02 tag, and running update.sh anyway forces the mailcow instance to get updated to the latest version instead of the 2025-02 one, so we’re back to the original problem: mailcow forcibly deletes all of the mailboxes and other data it contains.
here’s my question: what’s the official way to update from a legacy mailcow instance to a latest one without breaking it ? is it just not supported at all ? or do i need to re-set it up from scratch and importing the data there ? i would think that a mysql dump and import would work but i suppose there must have been breaking database changes which makes that impossible
i tried the backup_and_restore.sh script but it doesn’t work either:
root@mailcow-upgradetests:/mailcow# ./helper-scripts/backup_and_restore.sh backup all
Backup location (absolute path, starting with /): /mailcowbackup
Using 1 Thread(s) for this run.
Notice: You can set the Thread count with the THREADS Variable before you run this script.
Using /mailcowbackup as backup/restore location.
Found project name mailcow
docker: invalid spec: :/vmail:ro,z: empty section between colons.
See 'docker run --help'.
docker: invalid spec: :/crypt:ro,z: empty section between colons.
See 'docker run --help'.
OK
docker: invalid spec: :/redis:ro,z: empty section between colons.
See 'docker run --help'.
docker: invalid spec: :/rspamd:ro,z: empty section between colons.
See 'docker run --help'.
docker: invalid spec: :/postfix:ro,z: empty section between colons.
See 'docker run --help'.
Using SQL image mariadb:10.11, starting...
docker: invalid spec: :/var/lib/mysql/:ro,z: empty section between colons.
See 'docker run --help'.