SteffnVo When updating to “07/2025”, the following appears: "WARN[0000] mount of type volume should not define bind option [+] Running ⅛ …." This is new. However, I do not have a bind option in either my compose-override.yml or compose.yml, nor have I changed anything there. Do I need to know or change anything here? However, Mailcow does start.
pschiffe I’ve also noticed this now. Not sure if it’s b/c the new docker version or something with the docker compose file.
pschiffe The error I see is different from the one in the linked issue, also, I’m using Fedora without AppArmor (but SELinux is enabled in enforcing mode)
esackbauer Have you checked the SELinux specifics? https://docs.mailcow.email/getstarted/install/?h=selinux#check-selinux-specifics And Fedora is not a supported distribution.
DocFraggle Well, I just checked my console logs from the update (did it on 16.07.), I got the same log message. WARN[0000] mount of type `volume` should not define `bind` option Everything is working, though… Debian 12, no SELinux
pschiffe SELinux is properly configured and I’m running multiple Mailcow instances for years now. This issue: "WARN[0000] mount of type volume should not define bind option appeared only recently, after updating docker from v27 to v28 (and after updating mailcow). Cannot tell exactly when it started.
esackbauer You should then open an issue on Github, or switch to a supported distro. That an unsupported distro will work with any new versions is neither guaranteed nor tested. Especially when SELinux is used.