Curl 8.5.0 bug in Alpine 3.19

[leosamuele221]

Steps to reproduce

1. Install nextcloud with latest label
2. Install "Memories" app and Memories external container

Expected behavior

Normal work of memories transcoder

Actual behavior

Nextcloud container can't connect to memories transcoder container

Host OS

CentOS 9

Nextcloud AIO version

Nextcloud AIO v8.0.0

Current channel

Latest

Possible solution

Downgrade to Alpine 3.18
Upgrade to Alpine 3.20 (as soon as available)
Install curl 8.6.0 (see below)

Other valuable info

The problem is curl 8.5.0 that is affected by curl/curl#12558. This bug is actually solved in curl 8.6.0 so you just need to update curl.

Curl 8.6.0 isn't available from alpine package manager (in Alpine 3.19 the only version available is 8.5.0 https://pkgs.alpinelinux.org/packages?name=curl&branch=v3.19&repo=main)
The only way to install curl 8.6.0 is to build it from source

To install from source follow this steps:

1. enter in nextcloud-aio-nextcloud container
   docker exec -it nextcloud-aio-nextcloud bash

2. remove curl 8.5.0
   apk del curl

3. download curl 8.6.0 (you can do it in any folder you want, personally I did it in "/home/test")
   wget https://github.com/curl/curl/releases/download/curl-8_6_0/curl-8.6.0.tar.gz

4. unpack it
   tar -xf curl-8.6.0.tar.gz

5. move to it
   cd curl-8.6.0

6. install dependecies
   apk add openssl-dev g++ make autoconf libpsl-dev

7. configure
   ./configure --with-openssl

8. make and install
   make && make install

With curl 8.6.0 the problem is solved!

If you want more info on how to build curl here is the docs https://github.com/curl/curl/blob/master/docs/INSTALL.md#unix

[Zoey2936]

https://gitlab.alpinelinux.org/alpine/aports/-/issues/15690 can you try running apk upgrade --no-cache -a inside the nextcloud container and then retry with the preinstalled curl?

[leosamuele221]

Tried with no luck

(I did cd home to make sure I had reset the container)

[Zoey2936]

can you check if my prebuilt static curl binaries work? https://github.com/ZoeyVid/curl-quic/releases/latest

[leosamuele221]

For some reason it works from CLI

But not from nextcloud

I also tried to execute it as www-data and it worked (obviously I change curl exec to 777) from CLI but not from nextcloud

I did multiple reboots before trying

[Zoey2936]

yes, because nextcloud trys to use libcurl

[Zoey2936]

can you try apk add curl libcurl --repository http://dl-cdn.alpinelinux.org/alpine/edge/main inside the nextcloud container and retry?

[leosamuele221]

Still nothing...

[leosamuele221]

The problem is in c-ares 1.24.0 c-ares/c-ares#683 fixed with c-ares/c-ares#685, and released in c-ares 1.26.0.

curl 8.6.0 from edge repository uses c-ares 1.24.0 so the problem still persist.
When you build curl from source even if it's 8.6.0 it doesn't use c-ares, nor your build of curl uses c-ares @Zoey2936 that's why it worked

[leosamuele221]

I did apk add curl libcurl --repository http://dl-cdn.alpinelinux.org/alpine/edge/main and apk upgrade c-ares installing c-ares 1.27.0. But still doesn't work.
Now i'm confused

[leosamuele221]

I made a script to automate build https://gist.github.com/leosamuele221/aed36a3b9135032b6a8ffe7274e58ce7

[Zoey2936]

can you report this here: https://gitlab.alpinelinux.org/alpine/aports/-/issues

[leosamuele221]

Yes i can, I'll do it as soon as possible.
But until the problem isn't solved somebody should add a good build of curl in the nextcloud-aio-nextcloud container as a patch

One option is to run this script https://gist.github.com/leosamuele221/aed36a3b9135032b6a8ffe7274e58ce7 when creating nextcloud container (maybe in the Dockerfile) so it builds a working curl

Another better option is to build a working curl and download it from github when creating the container

[szaimen]

Hi, can you update to v8.1.0 beta and check if that improves things?

[leosamuele221]

Hi, yes i updated it to 8.1.0
The problem is still there
Obv is a curl problem, not a concern of nextcloud.

[leosamuele221]

Problem is still here, even after updating to Alpine 3.19

[szaimen]

can you report this here: https://gitlab.alpinelinux.org/alpine/aports/-/issues

Have you done so?

[szaimen]

Actually, I just tested and it works on my test instance:

[leosamuele221]

do curl -V

[szaimen]

[phroggar]

I'm coming here periodically, because we have noticed a similar issue in our setup.

I just want to share a solution which was working for us:

Specify a hostname for the container you are unable to resolve internally: e.g. setting "--hostname=mycontainer.domain.local"

You might need to take all containers down and restart them, to have them pickup the change in the local network.

This is not brilliant and i wish things would be resolved on the CURL or C-ARES side of things - but i just upgraded to Alpine 3.20 (curl 8.7.1 (aarch64-alpine-linux-musl) libcurl/8.7.1 ... c-ares/1.28.1) and i still see the problematic behaviour (everything (ping, wget, etc.) is resolving fine, but curl is not able to resolve if the hostname is missing)

[szaimen]

All right, that is annoying. Can someone please log an issue upstream?