Hi all,
I am aware that Mailcow team doesn’t provide and advise to use LXC container to run a mailcow dockerized version.
But in some case (mine for example) is mandatory. The ressource of the hardware that going to run the VPS is not enought for a full KVM machine.
I found this discussion on Github :
mailcow/mailcow-dockerized4215
So I switch the discussion to it’s correct place, here !
Let’s make a summary :
Need to activate nesting and keyctl on the proxmox VM by adding this line to the VMID.conf file :
features: keyctl=1,nesting=1
Need to load overlay and naufs module on proxmox :
echo -e “overlay\naufs” >> /etc/modules-load.d/modules.conf
reboot
Modify permission of the LXC by adding the lines in the VMID.conf :
lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow: a
lxc.cap.drop:
Finally, I still have issue running some dockers.
Pquan answer that’s :
It’s actually quite easy to run docker in an lxc. Just follow the usual proxmox forum guides. Make sure your docker runs (hello-world) in an unprivileged container (it does work). Already done by the previsous steps of this post
For mailcow, all you need to do is disable the extended capabilities in the docker-compose.yml project. they’re not supported (or needed). mailcow works without them anyway, specially if you’re using a “home” sized installation.
What are the extended capabilities ?
Kicou