This is related to https://github.com/mailcow/mailcow-dockerized/issues/5970 and https://community.mailcow.email/d/2126-backup-restore/2
It adds `docker compose create` to the script which gets executed directly after the sync of the mailcow-dockerized directory. This way the Docker daemon on the remote side creates everything and we get rid of the warning "volume "XYZ" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume"
This is helpful if you use the create-cold-standby.sh script to migrate your mailcow installation to another server and don't want to get those warnings after migration.
Co-authored-by: Niklas Meyer <niklas.meyer@servercow.de>
* Change default HTTP_BIND, HTTPS_BIND
https://github.com/mailcow/mailcow-dockerized/issues/4315#issuecomment-1083034329
* [Compose] Removed Colon after fallback IP in docker-compose.yml
* [Compose] Remove bind options from volumes (#4577)
(cherry picked from commit 4d53216c05)
* Migration (partially) of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* [ClamAV] Fixed ClamAV start before unbound
* Migration of update.sh + cold-standby.sh to composev2
* Formulation and values adjusted (IPv4 bind in generate-config.sh)
Co-authored-by: Amin Vakil <info@aminvakil.com>
Co-authored-by: qupfer <github@qupfer.de>
Co-authored-by: FreddleSpl0it <patschul@posteo.de>
DerLinkman