Description of problem: Running F35 docker container with default settings on RHEL7.9/CentOS7 does not work in the most common use cases. It fails with the following error: curl: (6) getaddrinfo() thread failed to start Version-Release number of selected component (if applicable): glibc-2.34-8.fc35.x86_64 How reproducible: easily with F35 container and RHEL7/CentOS7 host Steps to Reproduce: 1. yum install -y docker 2. service docker start 3. docker pull registry.fedoraproject.org/fedora:35 Actual results: # docker run -ti --rm registry.fedoraproject.org/fedora:35 bash -c 'curl "https://mirrors.fedoraproject.org"' curl: (6) getaddrinfo() thread failed to start Expected results: # docker run -ti --rm registry.fedoraproject.org/fedora:35 bash -c 'curl "https://mirrors.fedoraproject.org"' <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="https://mirrors.fedoraproject.org/publiclist/">here</a>.</p> <hr> <address>Apache Server at mirrors.fedoraproject.org Port 443</address> </body></html> Additional info: * it works fine with podman on RHEL-8 * it also starts to work with "docker run --privileged..." option
This is an issue with the container host. I've linked a few relevant Red Hat Enterprise Linux 7 bugs. Most of them are CLOSED/WONTFIX unfortunately, and dealt with the earlier but similar faccessat2 issue. (In your case, you do not even get so far that the older issue impacts you.) I believe there are third-party container engines that can run Fedora 35 images on Red Hat Enterprise Linux 7.