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.
DocFraggle Afaik this message is displayed if mailcow is restored via backup or cold standby script on a new system
trondandre DocFraggle ok! It has been restored. But is this an Warn message we can ignore without any problem you think? Is it any solutions for this warning?
accolon DocFraggle Afaik this message is displayed if mailcow is restored via backup or cold standby script on a new system I think this is (or better: was) the "WARN[0000] volume “mailcowdockerized_xyz” already exists but was not created by Docker Compose. Use external: true to use an existing volume" message. It only affects manual and older cold standby backups. According to this Github issue, the “mount of type volume…” message has to do with SELinux: mailcow/mailcow-dockerized6670
trondandre accolon Hi, But is this warning a big issues ore can we ignore this you think? It is no solutions to fix this?
accolon trondandre But is this warning a big issues ore can we ignore this you think? It’s just a warning. I’ve been running my mailcow this way for months now without any problems. As far as I understand this, the team had to add SELinux labels to make mailcow work on hosts that have SELinux enabled: mailcow/mailcow-dockerized6510 This causes a warning (which is, to my knowledge, harmless) if you don’t use SELinux.
duli If you don´t use SELinux, have you tried adding { "selinux-enabled": false } to /etc/docker/daemon.json and then systemctl restart docker And see if the warning goes away?