Prior to placing the issue, please check following: (fill out each checkbox with an X once done)
Description of the bug:
Docker container logs of affected containers:
Reproduction of said bug:
System information:
| Question | Answer |
| --- | --- |
| My operating system | I_DO_REPLY_HERE |
| Is Apparmor, SELinux or similar active? | I_DO_REPLY_HERE |
| Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported | I_DO_REPLY_HERE |
| Server/VM specifications (Memory, CPU Cores) | I_DO_REPLY_HERE |
| Docker Version (docker version) | I_DO_REPLY_HERE |
| Docker-Compose Version (docker-compose version) | I_DO_REPLY_HERE |
| Reverse proxy (custom solution) | I_DO_REPLY_HERE |
git diff origin/master, any other changes to the code? If so, please post them.iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat.docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and post the output.Wat?
Mailcow != Kernel. Not gonna comment further on that.
Wat?Can you help me please
I am sorry but my father will kill me if he knows that
It has nothing to do with mailcow. It's the kernel from your operating system what blows up.
Beside that: You successfully ignored the first three checkboxes.
No I didn鈥檛 ignored it i cant tick the boxes
I am so sorry please help me
Don't feed the troll guys 馃ぃ
Issue not mailcow-related. Locking.
Most helpful comment
It has nothing to do with mailcow. It's the kernel from your operating system what blows up.
Beside that: You successfully ignored the first three checkboxes.