Hello there, thank you for maintaining this community forum.
I’m decent at managing Linux servers but I’m a total beginner when it comes to docker.
I’ve tried to install mailcow on my Debian 12 VPS following this tutorial. Everything worked fine up to the point of running docker-compose up -d
The healthcheck for the unbound container fails. When looking at the logs I see:
Setting console permissions...
Receiving anchor key...
[1714591927] libunbound[9:0] error: socketpair: Permission denied
Receiving root hints...
######################################################################## 100.0%
setup in directory /etc/unbound
removing artifacts
Setup success. Certificates created. Enable in unbound.conf file to use
[1714591928] unbound[1:0] warning: unable to initgroups unbound: Permission denied
[1714591928] unbound[1:0] error: Could not open logfile /dev/console: Permission denied
[1714591928] unbound[1:0] notice: init module 0: validator
[1714591928] unbound[1:0] notice: init module 1: iterator
[1714591928] unbound[1:0] error: socketpair: Permission denied
[1714591928] unbound[1:0] fatal error: could not create worker
I’ve tried to add the following caps to the unbound service in the docker-compose.yaml
but without any success.
cap_add:
- NET_ADMIN
- NET_BIND_SERVICE
- SYS_ADMIN
I think it’s related to some network or socket permissions. I know AppArmor is running but there doesn’t seem to be any restrictions applied to docker.
Like I said, being unfamiliar with both unbound and docker makes it hard for me to solve. Any help is appreciated. Thank you.