Please paste the output of this command in your mailcow directory:
ls -la data/conf/unbound/
EnglishCould not open /etc/unbound/unbound.conf: Permission denied
Have something to say?
Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!
➜ mailcow-dockerized ls -la data/conf/unbound/
total 4
drwxr-xr-x. 1 root root 24 Sep 7 14:04 .
drwxr-xr-x. 1 root root 106 Sep 7 14:04 ..
-rw-r–r–. 1 root root 1300 Sep 7 14:04 unbound.conf
Hmm, and from inside the container?
docker compose exec unbound-mailcow /bin/bash
d929ea48adfb:/# ls -la /etc/unbound/Error response from daemon: Container 7c69eb45dde3a74a486c2f9b26e9c30b0f41595e60f53da512c574bc0a8c3ed9 is restarting, wait until the container is running
What about a complete restart?
docker compose down
docker compose up -d(just in case: as root, no sudo!)
[+] Running 20/20
Network mailcowdockerized_mailcow-network Created 0.4s
Container mailcowdockerized-netfilter-mailcow-1 Started 1.0s
✘ Container mailcowdockerized-unbound-mailcow-1 Error 10.8s
Container mailcowdockerized-dockerapi-mailcow-1 Started 1.3s
Container mailcowdockerized-sogo-mailcow-1 Started 1.3s
Container mailcowdockerized-olefy-mailcow-1 Started 1.2s
Container mailcowdockerized-memcached-mailcow-1 Started 1.3s
Container mailcowdockerized-clamd-mailcow-1 Created 0.1s
Container mailcowdockerized-redis-mailcow-1 Started 1.3s
Container mailcowdockerized-mysql-mailcow-1 Started 1.5s
Container mailcowdockerized-solr-mailcow-1 Started 1.3s
Container mailcowdockerized-dovecot-mailcow-1 Started 2.4s
Container mailcowdockerized-php-fpm-mailcow-1 Started 1.5s
Container mailcowdockerized-postfix-mailcow-1 Created 0.1s
Container mailcowdockerized-rspamd-mailcow-1 Created 0.2s
Container mailcowdockerized-ofelia-mailcow-1 Started 2.7s
Container mailcowdockerized-nginx-mailcow-1 Started 2.1s
Container mailcowdockerized-acme-mailcow-1 Created 0.0s
Container mailcowdockerized-watchdog-mailcow-1 Created 0.0s
Container mailcowdockerized-ipv6nat-mailcow-1 Created 0.1s
dependency failed to start: container mailcowdockerized-unbound-mailcow-1 is unhealthy- Edited
Check that umask is 0022, and that you are running all mailcow commands as root (not as sudo!),
Try to rerun update.sh as root, if you haven’t already.
I did everything in root
[root@vps-be7b2586 mailcow-dockerized]# umask
0022
[root@vps-be7b2586 mailcow-dockerized]# ./update.sh
Detecting if your IP is listed on Spamhaus Bad ASN List...
Your server's public IP uses an AS that is blocked by Spamhaus to use their DNS public blocklists for Postfix.
mailcow did not detected a value for the variable SPAMHAUS_DQS_KEY inside mailcow.conf!
To use the Spamhaus DNS Blocklists again, you will need to create a FREE account for their Data Query Service (DQS) at: https://www.spamhaus.com/free-trial/sign-up-for-a-free-data-query-service-account
Once done, enter your DQS API key in mailcow.conf and mailcow will do the rest for you!
Checking internet connection... OK
Detecting which build your mailcow runs on...
You are receiving stable updates (master).
To change that run the update.sh Script one time with the --nightly parameter to switch to nightly builds.
Checking for newer update script...
Updated 0 paths from 900d0e7c
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Native IPv6 implementation available.
This will enable experimental features in the Docker daemon and configure Docker to do the IPv6 NATing instead of ipv6nat-mailcow.
!!! This step is recommended !!!
mailcow will try to roll back the changes if starting Docker fails after modifying the daemon.json configuration file.
Should we try to enable the native IPv6 implementation in Docker now (recommended)? [y/N] y
Warning: You seem to have modified the /etc/docker/daemon.json configuration by yourself and not fully/correctly activated the native IPv6 NAT implementation.
You will need to merge your existing configuration manually or fix/delete the existing daemon.json configuration before trying the update process again.
Please merge the following content and restart the Docker daemon:
{"ipv6":true,"fixed-cidr-v6":"fd00:dead:beef:c0::/80","experimental":true,"ip6tables":true}
Validating docker-compose stack configuration...
Checking for conflicting bridges...
Saving diff to update_diffs/diff_before_update_2024-11-11-18-30-55...
Prefetching images...
1.23: Pulling from mailcow/unbound
Digest: sha256:161135ce3a3165430455e6191a5f88d9d9faab9f0c6b49689e0cd84f4fe98882
Status: Image is up to date for mailcow/unbound:1.23
docker.io/mailcow/unbound:1.23
10.5: Pulling from library/mariadb
Digest: sha256:575327d46f436430330e363aa151d34e730fa5e94d85e5effa87cc960714d1b7
Status: Image is up to date for mariadb:10.5
docker.io/library/mariadb:10.5
7-alpine: Pulling from library/redis
Digest: sha256:de13e74e14b98eb96bdf886791ae47686c3c5d29f9d5f85ea55206843e3fce26
Status: Image is up to date for redis:7-alpine
docker.io/library/redis:7-alpine
1.66: Pulling from mailcow/clamd
Digest: sha256:39165e03bda2be5b2ae6a7809e1ef556413274077b53f61d0eae3f7690ff06d2
Status: Image is up to date for mailcow/clamd:1.66
docker.io/mailcow/clamd:1.66
1.98: Pulling from mailcow/rspamd
Digest: sha256:5d4a987ca6b5c8c1490292674210e80dc43b809604c55cecb1c9f383f9ab95e3
Status: Image is up to date for mailcow/rspamd:1.98
docker.io/mailcow/rspamd:1.98
1.91: Pulling from mailcow/phpfpm
Digest: sha256:ed0b144cb7cf5f8753519fadb785466e9bb02d891a121a7afeea2f26de5766b0
Status: Image is up to date for mailcow/phpfpm:1.91
docker.io/mailcow/phpfpm:1.91
1.127: Pulling from mailcow/sogo
Digest: sha256:5a131262872d59b2b1a84ccc33776c530e2360c1d3cb9eaff51c4215c629e391
Status: Image is up to date for mailcow/sogo:1.127
docker.io/mailcow/sogo:1.127
2.2: Pulling from mailcow/dovecot
Digest: sha256:139ddc64f8440902c6b94cd0a2d6afa3ba0cb5620d2d4e7d1befab1c2bf8e1bd
Status: Image is up to date for mailcow/dovecot:2.2
docker.io/mailcow/dovecot:2.2
1.77: Pulling from mailcow/postfix
Digest: sha256:6a11ac78bc3efb87e1a3e9457158a5eddd55078dae6e86e4de64d9619665fc93
Status: Image is up to date for mailcow/postfix:1.77
docker.io/mailcow/postfix:1.77
alpine: Pulling from library/memcached
Digest: sha256:04f3154ecbd772e567cf3349c0d7181499e118f61b771e427002a628f5623552
Status: Image is up to date for memcached:alpine
docker.io/library/memcached:alpine
mainline-alpine: Pulling from library/nginx
Digest: sha256:2140dad235c130ac861018a4e13a6bc8aea3a35f3a40e20c1b060d51a7efd250
Status: Image is up to date for nginx:mainline-alpine
docker.io/library/nginx:mainline-alpine
1.90: Pulling from mailcow/acme
Digest: sha256:ef179d719dd752c89948a619a6f71e9b7cae54b53f237d7285ca1f64daa01e39
Status: Image is up to date for mailcow/acme:1.90
docker.io/mailcow/acme:1.90
1.59: Pulling from mailcow/netfilter
Digest: sha256:f2b5a92a2d8eef1011e239b6ead4f6379b1e4d196e9c5c55470514b5a07b7eaa
Status: Image is up to date for mailcow/netfilter:1.59
docker.io/mailcow/netfilter:1.59
2.05: Pulling from mailcow/watchdog
Digest: sha256:f045e502a97db78691fe817476e713b0655c0a941ab0b0f042dcfde4b666a360
Status: Image is up to date for mailcow/watchdog:2.05
docker.io/mailcow/watchdog:2.05
2.09: Pulling from mailcow/dockerapi
Digest: sha256:6ba2c0b2fc71683136558a58818b29b6164958ad5ca74855aaf577f0c7877baf
Status: Image is up to date for mailcow/dockerapi:2.09
docker.io/mailcow/dockerapi:2.09
1.8.3: Pulling from mailcow/solr
Digest: sha256:102ba2b9dafaf9fd3b6454d1b9f6cac8fd31c2ce1c584c5102075d8f0af6f16d
Status: Image is up to date for mailcow/solr:1.8.3
docker.io/mailcow/solr:1.8.3
1.13: Pulling from mailcow/olefy
Digest: sha256:7af3077336fa79978dfffef76af1eee37a4befe7df4c6fdd6aed7753e86b466b
Status: Image is up to date for mailcow/olefy:1.13
docker.io/mailcow/olefy:1.13
latest: Pulling from mcuadros/ofelia
Digest: sha256:5dbbf5378f65a43c49859bc6342cbec4a13fabd0474ad7398d6d906181fb7529
Status: Image is up to date for mcuadros/ofelia:latest
docker.io/mcuadros/ofelia:latest
Using default tag: latest
latest: Pulling from robbertkl/ipv6nat
Digest: sha256:0cf4971efbe9df3c39f6b11666bece782891856598c6d3649e900afc88f76c00
Status: Image is up to date for robbertkl/ipv6nat:latest
docker.io/robbertkl/ipv6nat:latest
Stopping mailcow...
[+] Running 20/20
Container mailcowdockerized-ofelia-mailcow-1 Removed 10.3s
Container mailcowdockerized-ipv6nat-mailcow-1 Removed 0.0s
Container mailcowdockerized-olefy-mailcow-1 Removed 10.3s
Container mailcowdockerized-memcached-mailcow-1 Removed 0.8s
Container mailcowdockerized-dockerapi-mailcow-1 Removed 0.6s
Container mailcowdockerized-solr-mailcow-1 Removed 0.8s
Container mailcowdockerized-rspamd-mailcow-1 Removed 0.0s
Container mailcowdockerized-watchdog-mailcow-1 Removed 0.0s
Container mailcowdockerized-clamd-mailcow-1 Removed 0.0s
Container mailcowdockerized-postfix-mailcow-1 Removed 0.0s
Container mailcowdockerized-acme-mailcow-1 Removed 0.0s
Container mailcowdockerized-nginx-mailcow-1 Removed 0.0s
Container mailcowdockerized-php-fpm-mailcow-1 Removed 10.3s
Container mailcowdockerized-dovecot-mailcow-1 Removed 10.8s
Container mailcowdockerized-sogo-mailcow-1 Removed 2.3s
Container mailcowdockerized-redis-mailcow-1 Removed 0.4s
Container mailcowdockerized-mysql-mailcow-1 Removed 0.0s
Container mailcowdockerized-unbound-mailcow-1 Removed 0.0s
Container mailcowdockerized-netfilter-mailcow-1 Removed 0.2s
Network mailcowdockerized_mailcow-network Removed 0.3s
Checking for remaining containers...
Committing current status...
Fetching updated code from remote...
Merging local with remote code (recursive, strategy: "theirs", options: "patience"...
Already up to date.
Fetching new images, if any...
[+] Pulling 19/19
postfix-mailcow Pulled 1.3s
ofelia-mailcow Pulled 1.3s
memcached-mailcow Pulled 1.3s
acme-mailcow Pulled 1.3s
redis-mailcow Pulled 1.3s
olefy-mailcow Pulled 1.3s
netfilter-mailcow Pulled 1.3s
ipv6nat-mailcow Pulled 1.2s
clamd-mailcow Pulled 1.2s
php-fpm-mailcow Pulled 1.2s
mysql-mailcow Pulled 1.3s
rspamd-mailcow Pulled 1.3s
unbound-mailcow Pulled 1.3s
solr-mailcow Pulled 1.2s
sogo-mailcow Pulled 1.2s
nginx-mailcow Pulled 1.2s
dovecot-mailcow Pulled 1.2s
watchdog-mailcow Pulled 1.3s
dockerapi-mailcow Pulled 1.3s
cp: not replacing 'data/assets/ssl/cert.pem'
cp: not replacing 'data/assets/ssl/dhparams.pem'
cp: not replacing 'data/assets/ssl/key.pem'
Checking IPv6 settings...
Starting mailcow...
[+] Running 20/20
Network mailcowdockerized_mailcow-network Created 0.5s
Container mailcowdockerized-netfilter-mailcow-1 Started 1.0s
Container mailcowdockerized-olefy-mailcow-1 Started 1.3s
Container mailcowdockerized-dockerapi-mailcow-1 Started 1.1s
Container mailcowdockerized-memcached-mailcow-1 Started 1.2s
✘ Container mailcowdockerized-unbound-mailcow-1 Error 10.9s
Container mailcowdockerized-sogo-mailcow-1 Started 1.2s
Container mailcowdockerized-solr-mailcow-1 Started 1.3s
Container mailcowdockerized-mysql-mailcow-1 Started 1.4s
Container mailcowdockerized-clamd-mailcow-1 Created 0.1s
Container mailcowdockerized-redis-mailcow-1 Started 1.2s
Container mailcowdockerized-postfix-mailcow-1 Created 0.1s
Container mailcowdockerized-dovecot-mailcow-1 Started 2.4s
Container mailcowdockerized-php-fpm-mailcow-1 Started 1.4s
Container mailcowdockerized-nginx-mailcow-1 Started 2.1s
Container mailcowdockerized-ofelia-mailcow-1 Started 2.7s
Container mailcowdockerized-rspamd-mailcow-1 Created 0.1s
Container mailcowdockerized-acme-mailcow-1 Created 0.0s
Container mailcowdockerized-watchdog-mailcow-1 Created 0.0s
Container mailcowdockerized-ipv6nat-mailcow-1 Created 0.0s
dependency failed to start: container mailcowdockerized-unbound-mailcow-1 is unhealthy
Collecting garbage...Did you see this?
Warning: You seem to have modified the /etc/docker/daemon.json configuration by yourself and not fully/correctly activated the native IPv6 NAT implementation.
You will need to merge your existing configuration manually or fix/delete the existing daemon.json configuration before trying the update process again.
Please merge the following content and restart the Docker daemon:
{"ipv6":true,"fixed-cidr-v6":"fd00:dead:beef:c0::/80","experimental":true,"ip6tables":true}Yes, I had tried to merge and test, but I have the same problem.
Culottes
-rw-r–r–. 1 root root 1300 Sep 7 14:04 unbound.conf
I just saw the dot (.) at the end of the permissions. Do you have selinux enabled? If that’s the case, did you check the requirements?
Install mailcow - mailcow: dockerized documentation docs.mailcow.email
- Edited
I just encountered the very same problem upgrading one of my instances (another, similarly configured, didn’t encounter the same problem). After rebooting the server (not sure if that was necessary) and doing (as root, not via sudo) the docker compose down && docker compose up -d it worked again! Thanks - this saved my bacon.
Ok, but do you use selinux?
No, I do not. I do, however, have an NGINX reverse proxy running on the Docker host, unlike my other instances.
Hmm, the dot indicates that there is an active selinux context present for this file… a reboot may have reloaded it
- Edited
Note that I’m not @Culottes, although I experienced the same problem after attempting an upgrade from 2024-08.4 (was it .4? The latest minor release in any case).
Yes, I use SE Linux, but I’ve followed the documentation.
➜ ~ rpm -qa | grep container-selinux
container-selinux-2.233.0-1.fc40.noarch
➜ ~ sudo docker info 2> /dev/null | grep selinux
selinux
➜ ~ cat /etc/docker/daemon.json
{
"selinux-enabled": true,
"ipv6": true,
"fixed-cidr-v6": "fd00:dead:beef:c0::/80",
"experimental": true,
"ip6tables": true
}But above all, for months it worked normally, and then all of a sudden this bug happened.
I tried to reboot my VPS, but it didn’t change anything unfortunately.
- Edited
lightweight Note that I’m not
@Culottes
Ah sorry, overlooked that 
[unknown] I tried to reboot my VPS, but it didn’t change anything unfortunately.
OK, you definitely have to debug around selinux in this case…. that’s one of the reasons why I don’t use selinux myself, it’s just a PITA…
No one is typing