this is a little bit of a longer answer.
well I did some looking around and came up with the following
VPS: 5.10.0-26-amd64 #1 SMP Debian (bullseye) 5.10.197-1 (2023-09-29) x86_64 GNU/Linux
Docker version 24.0.7
Docker Compose version v2.18.1
that VPS I am using only to run mailcow-dockerize
I changed the setting of “… enable_ipv6: true …” to false (in the docker-compose.yml file around line 615).
At this point watchdog shows me that postfix and dovecot are healthy, actually everything is healthy, except when I look with docker containter ps (kinda of see more details below)
Current issue is also the container for unbound
“… mailcow/unbound:1.18 ”/docker-entrypoint.…“ (unhealthy) …”
after running docker container logs (ID unbound) I checked the firewall making sure the port 53 is not blocked / denied, rebootet the server (for $h!t and giggles) and when it was back online postfix and dovecot crapped out on me. and it makes sense because they cannot resolve DNS names (duh unbound not healthy).
Now did some “hammer” tooling and ran.
docker-compose kill
docker-compose up -d
NOTE: all containers have been created but not all have started like postfix, watchdog, acme, netfilter, clamd. and unbound caused an error.
ok so killing seems at bit harsh. so lets be gentle and do
docker-compose stop
docker-compose up -d
ah wonderful it shows all good and unbound heathly
… hmm wait in docker container ps it shows container unbound unhealthy (WTF). But let me check, well watchdog shows everything healthy and all my mailboxes can be opened. So I guess after some much time x the $h!t will hit the fan again.