Update from very old mail cow failing

paulchabot

I am afraid of loosing data. Just tried to update mail cow. It was an old update, but it hasn’t started and wants me to delete the vmail volume, which leads me to believe its a fresh mailcow.

Am I wrong? And if I am right, how do I move everything to the new vol if I delete it.

In love with mailcow but I the last time I updated, this happened, I didn’t seek help and just rebuilt everything.

paulchabot

Also, here is what update.sh is telling me

ERROR: Configuration for volume vmail-vol-1 specifies "type" driver_opt none, but a volume with the same name uses a different "type" driver_opt (None). If you wish to use the new configuration, please remove the existing volume "mailcowdockerized_vmail-vol-1" first: $ docker volume rm mailcowdockerized_vmail-vol-1

paulchabot

I think I might have found my fix.

https://mailcow.github.io/mailcow-dockerized-docs/u_e-dovecot-vmail-volume/

Will reply with more info after these messages.

paulchabot

So that link above was it. My docker-compose.ovveride.yml

’version: ‘2.1’
volumes:
vmail-vol-1:
driver_opts:
type: none
device: /opt/mailcow-fs/vmail/_data
o: bind`