Prior to placing the issue, please check following:(fill out each checkbox with an X once done)
[x] I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue.
[x] I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
[x] I have understood that answers are voluntary and community-driven, and not commercial support.
[x] I have verified that my issue has not been already answered in the past. I also checked previous issues.
Summary
The update process hangs at Trying to determine GLIBC version....
I had to abort it and then restart the docker-compose container (docker-compose up -d) to make the mail server run again.
However, the update gets always stuck at the same point and can't be finished currently.
Logs
./update.sh
Checking internet connection... OK
Checking for newer update script...
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Great! Native IPv6 NAT is active.
Validating docker-compose stack configuration...
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Checking for conflicting bridges...
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Saving diff to update_diffs/diff_before_update_2021-09-18-11-13-00...
Prefetching images...
1.14: Pulling from mailcow/unbound
Digest: sha256:72725228ff2f87fb1c84530ff0a147a254c37dd3eaa28ccb2bbed530f9b23355
Status: Image is up to date for mailcow/unbound:1.14
docker.io/mailcow/unbound:1.14
10.5: Pulling from library/mariadb
Digest: sha256:dfcba5641bdbfd7cbf5b07eeed707e6a3672f46823695a0d3aba2e49bbd9b1dd
Status: Image is up to date for mariadb:10.5
docker.io/library/mariadb:10.5
6-alpine: Pulling from library/redis
Digest: sha256:fa785f9bd167b94a6b30210ae32422469f4b0f805f4df12733c2f177f500d1ba
Status: Image is up to date for redis:6-alpine
docker.io/library/redis:6-alpine
1.41: Pulling from mailcow/clamd
Digest: sha256:1dee9b1698e1eb8b7269a9a5053c2d57f1b5e64cf1657e813ee6eea9c375db30
Status: Image is up to date for mailcow/clamd:1.41
docker.io/mailcow/clamd:1.41
1.79: Pulling from mailcow/rspamd
Digest: sha256:aca90127142e7aa0b03b5da40dd3e1fa82cb500bf61288db55e2f067d0e3afa9
Status: Image is up to date for mailcow/rspamd:1.79
docker.io/mailcow/rspamd:1.79
1.76: Pulling from mailcow/phpfpm
Digest: sha256:0d1037833f44959ea7cc76cd76591a86151e4c39a3fa7a81815836d270fe5661
Status: Image is up to date for mailcow/phpfpm:1.76
docker.io/mailcow/phpfpm:1.76
1.101: Pulling from mailcow/sogo
Digest: sha256:b6f83ab276ba47903ece3e618fcab75974cb613cece4306886fd0fb7dc87a0e3
Status: Image is up to date for mailcow/sogo:1.101
docker.io/mailcow/sogo:1.101
1.156: Pulling from mailcow/dovecot
Digest: sha256:9ed3c0340ab240e93f48ac1a24d922135fb05b0934fe203366fba396b933288d
Status: Image is up to date for mailcow/dovecot:1.156
docker.io/mailcow/dovecot:1.156
1.66: Pulling from mailcow/postfix
Digest: sha256:36cd0b95e254ad0d80ca978b8bdba82c0ad9128e79c45ea30030ff32034a5113
Status: Image is up to date for mailcow/postfix:1.66
docker.io/mailcow/postfix:1.66
alpine: Pulling from library/memcached
Digest: sha256:99e30a033ef422d6ad3ebe18c6c1009f20bee2d025fc00569be5dcd81aadc7be
Status: Image is up to date for memcached:alpine
docker.io/library/memcached:alpine
mainline-alpine: Pulling from library/nginx
Digest: sha256:686aac2769fd6e7bab67663fd38750c135b72d993d0bb0a942ab02ef647fc9c3
Status: Image is up to date for nginx:mainline-alpine
docker.io/library/nginx:mainline-alpine
1.80: Pulling from mailcow/acme
Digest: sha256:4a680e7585c15449ad90b3f5eaaf132b9b2f00e1dd5d9228f2354dd4083e3e76
Status: Image is up to date for mailcow/acme:1.80
docker.io/mailcow/acme:1.80
1.44: Pulling from mailcow/netfilter
Digest: sha256:0d1dd04dfb475d35bb6e9a226b8f78e6f6a1d2b49633b3adf3b14dd26c8b12db
Status: Image is up to date for mailcow/netfilter:1.44
docker.io/mailcow/netfilter:1.44
1.94: Pulling from mailcow/watchdog
Digest: sha256:78c526a8882632e3100486a675b42104836d224ce7aab2349e04f7d73f99a479
Status: Image is up to date for mailcow/watchdog:1.94
docker.io/mailcow/watchdog:1.94
1.39: Pulling from mailcow/dockerapi
Digest: sha256:bdbd697ccf0ca22ffbc355484e20d28886160f56f3b882fca991fc730269f7d9
Status: Image is up to date for mailcow/dockerapi:1.39
docker.io/mailcow/dockerapi:1.39
1.7: Pulling from mailcow/solr
Digest: sha256:6efd0038b1dc74d5b8fb8f2ed00336552e34469eaaba410c535b7885f5720d6a
Status: Image is up to date for mailcow/solr:1.7
docker.io/mailcow/solr:1.7
1.8: Pulling from mailcow/olefy
Digest: sha256:ac89ace5f8ed1276ecd651601d999e8abe4e6c407b7015830311fdd51f7a2d7c
Status: Image is up to date for mailcow/olefy:1.8
docker.io/mailcow/olefy:1.8
latest: Pulling from mcuadros/ofelia
Digest: sha256:3c0477ca28375ab62501df86685104c898bb6a2a1eb28fa825b2b9ed87ed23f2
Status: Image is up to date for mcuadros/ofelia:latest
docker.io/mcuadros/ofelia:latest
Stopping mailcow...
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
Removing network mailcowdockerized_mailcow-network
WARNING: Network mailcowdockerized_mailcow-network not found.
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 docker-compose version...
Trying to determine GLIBC version...
Reproduction
I just ran the update script today, I also updated the Ubuntu host packages and rebooted it.
Re-running the update script results in the script getting stuck at the same point.
System information
Question
Answer
My operating system
Ubuntu 18.04.5 LTS
Is Apparmor, SELinux or similar active?
yes (apparmor module is loaded)
Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported
Cloud provider using KVM
Server/VM specifications (Memory, CPU Cores)
8 GB; 2 vCPU cores
Docker Version (docker version)
Docker version 20.10.5, build 55c4c88
Docker-Compose Version (docker-compose version)
1.28.5, build c4eb3a1f
Reverse proxy (custom solution)
No
Output of git diff origin/master, any other changes to the code? If so, please post them.
All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat.
DNS problems? Please run 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.
Prior to placing the issue, please check following: (fill out each checkbox with an
X
once done)Summary
The update process hangs at
Trying to determine GLIBC version...
. I had to abort it and then restart the docker-compose container (docker-compose up -d
) to make the mail server run again. However, the update gets always stuck at the same point and can't be finished currently.Logs
Reproduction
I just ran the update script today, I also updated the Ubuntu host packages and rebooted it. Re-running the update script results in the script getting stuck at the same point.
System information
apparmor module is loaded
)docker version
)Docker version 20.10.5, build 55c4c88
docker-compose version
)1.28.5, build c4eb3a1f
No
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
andip6tables -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.