Bug 2025899 - dnf fails with "getaddrinfo() thread failed to start"
Summary: dnf fails with "getaddrinfo() thread failed to start"
Keywords:
Status: CLOSED DUPLICATE of bug 2009047
Alias: None
Product: Fedora Container Images
Classification: Fedora
Component: fedora-container-image
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Clement Verna
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-23 10:35 UTC by Stephen Kitt
Modified: 2023-02-05 21:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-16 09:37:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stephen Kitt 2021-11-23 10:35:34 UTC
Description of problem:

On RHEL 8.4 (CSB), the following worked with fedora:34 but fails with fedora:35:

$ container=$(buildah from fedora:35)
$ buildah run $container -- dnf -y upgrade --nodocs --setopt=install_weak_deps=False
WARN[0000] error mounting subscriptions, skipping entry in /usr/share/containers/mounts.conf: getting host subscription data: failed to read subscriptions from "/usr/share/rhel/secrets": open /usr/share/rhel/secrets/rhsm/rhsm.conf: permission denied 
Fedora 35 - x86_64                                                                                  0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'fedora':
  - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start]
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start]
error while running runtime: exit status 1
ERRO[0001] exit status 1


Version-Release number of selected component (if applicable): 35


How reproducible: 100%


Steps to Reproduce: see description above

Actual results: see above

Expected results: dnf upgrade runs correctly


This works if the build is run on a Fedora 35 system rather than RHEL 8.4.

Comment 1 E. Castedo Ellerman 2022-01-01 23:17:58 UTC
I see the same problem. If I add '--security-opt seccomp=unconfined' then it works, i.e.:

$ container=$(buildah from --security-opt seccomp=unconfined fedora:35)

Thanks to https://pascalroeleven.nl/2021/09/09/ubuntu-21-10-and-fedora-35-in-docker/.

Comment 2 Brian J. Murrell 2022-02-15 15:57:12 UTC
Any update here?  This happens with docker also.

Comment 3 Derrick Ornelas 2022-03-12 21:08:45 UTC
I'm running into this exact issue on Quay.io trying to build a F35-based image.  

At this point I'm fairly sure this is a duplicate of BZ 2009047.  @clems.verna @tsweeney seems like we could close this one out if you agree.

Comment 4 Tom Sweeney 2022-03-15 18:09:23 UTC
Seems like a dupe to me too, well spotted Derrick.  I'm fine with setting this as a duplicate.

Comment 5 Stephen Kitt 2022-03-16 09:37:31 UTC

*** This bug has been marked as a duplicate of bug 2009047 ***

Comment 6 Tilo 2022-04-08 22:38:21 UTC
@dornelas got this today on quay.io build. Do you know when the build nodes of quay will have this fix?

Comment 7 Tilo 2022-04-29 14:50:18 UTC
fyi here the quay.io JIRA ticket: https://issues.redhat.com/browse/PROJQUAY-3739


Note You need to log in before you can comment on or make changes to this bug.