Hi, same problem here. I think one cause for confusion is the healthcheck script inside the container and docker calling the container “healthy” or not. This is what I get after docker up -d (PS: I use podman with docker-compose standalone inside a VM behind NAT and NAT6, heathcheck.sh runs without any problems.)
✘ Container mailcowdockerized-unbound-mailcow-1 Error 3.1s
dependency failed to start: container mailcowdockerized-unbound-mailcow-1 had unexpected health status ""
If you restart unbound-mailcow manual, postfix will not be running. I played a little bit around and using version 2023-05 had no problems whatsoever. Running docker-compose up unbound-mailcow -d ; docker-compose up -d on version 2023-10a yield this:
✔ Container mailcowdockerized-unbound-mailcow-1 Healthy 0.0s
Without first starting unbound-mailcow in version 2023-10a, I get this:
✘ Container mailcowdockerized-unbound-mailcow-1 Error 3.0s
So my assumption is, that docker at startup checks if unbound-mailcow changes “started” to “healthy” status. If this does not happend within short time at boot, the container is switched from docker to error status even though you can connect to unbound, healthcheck.sh works find and unbound is resolving dns just fine.
I changed back to the latest mailcow and changed in docker-compose.yml the “condition: service_healthy” to “condition: service_started” everywhere I found it and now it runs without any problems. Unbound says at startup:
✔ Container mailcowdockerized-unbound-mailcow-1 Started 3.0s
I hope this helps finding a cure to this problem. thanks