cURL not working inside nextcloud docker container

After the upgrade of the NextCloud app from 23.0.5 to version 25.0.9 all curl commands in the docker container are not working anymore. Behaviour that I saw first was that Nextcloud News are getting no updates anymore and the NextCloud protocol shows warnings like: read error : cURL error 6: getaddrinfo() thread failed to start (see for

I tested curl on the host and it works, but testing it from inside the container via univention-app shell nextcloud gives the same error message.

root@nextc-77545073:/var/www/html# curl
curl: (6) getaddrinfo() thread failed to start

I tested also in other docker containers and it works there as well and so it looks like the problem is really only with the NextCloud docker container/image.

Checking the installed version of curl shows differences between the host and the container:

xxx@yyy:~$ curl --version
curl 7.64.0 (x86_64-pc-linux-gnu) libcurl/7.64.0 OpenSSL/1.1.1n zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Release-Date: 2019-02-06
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

root@nextc-77545073:/# curl --version
curl 7.81.0 (x86_64-pc-linux-gnu) libcurl/7.81.0 OpenSSL/3.0.2 zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 libidn2/2.3.2 libpsl/0.21.0 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.43.0 librtmp/2.3 OpenLDAP/2.5.14
Release-Date: 2022-01-05
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets zstd

Following images are there:

xxx@yyy:~$ docker images
REPOSITORY                                    TAG                 IMAGE ID            CREATED             SIZE             cd546efe7f01        8 days ago          2.79GB       25.0.9-0            8f172f0eeb35        2 weeks ago         1.39GB       23.0.5-0            b1afba394816        14 months ago       1.29GB       3.2.7-ucs.1         ef62ae5a2ef2        20 months ago       1.47GB

I did a lot of research but could not find a way to figure out how to fix this. (mentioned was sometimes SECCOMP, but I don’t know how to use it with univention docker image)

Does anyone have an idea how to solve this or how to dig deeper?


We had the same problem as you on different containers and different servers : Collabora working on one server and doesn’t work on another server (both updated to latest 5.04), same problem with Nextcloud. It seems related to some glibc incompatibility, but we never found why it was working on one node and not on another one. It seems that the updater has done something on some container and nothing on others…

In the end, we get all running fine by uninstalling/reinstalling the application :
univention-app remove nextcloud
univention-app install nextcloud

And all the data was there after uninstall/reinstall! (we took a snapshot before just in case)

Hope it helps!

Thanks for your feedback :slightly_smiling_face:.
I will try it out on the weekend and give an update on it afterwards.


After some tests it looks like this workaround is the solution.

Thank you Nicolas :slightly_smiling_face: