Bug 2026147 - fedora:35 cannot resolve host name
Summary: fedora:35 cannot resolve host name
Keywords:
Status: CLOSED EOL
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 21:39 UTC by James Szinger
Modified: 2022-12-13 15:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:57:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description James Szinger 2021-11-23 21:39:27 UTC
Description of problem:

I am trying to use podman under CentOS 7 to run a Fedora 35 container.

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

podman-1.6.4-29.el7_9.x86_64 from CentOS Extras

How reproducible:

Always

Steps to Reproduce:

1. podman run -it --rm registry.fedoraproject.org/fedora:35 yum check-update

Actual results:

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]

Expected results:

A list of packages needing updating.

Additional info:

Works with Fedora 34.  It seems that some change in F35 broke host name lookup.

Seems similar to <https://bugzilla.redhat.com/show_bug.cgi?id=2007758>, but that uses systemd-nspawn instead of podman.

Fetching a web page by IP address (`curl http://192.168.1.10/`) works.

Works on a Fedora 34 host.

Comment 1 Christian Horn 2022-02-18 22:17:44 UTC
I see this too, name resolution on Debian here not working for
newer Fedora containers.

Fedora35 hypervisor: all of Fedora34/35/36 containers work
Debian Bullseye hypervisor: Fedora34 works, Fedora35/36 do not work

Output on Bullseye:
# podman run -it registry.fedoraproject.org/fedora:34 bash -c 'curl fluxcoil.net'
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>
# podman run -it registry.fedoraproject.org/fedora:35 bash -c 'curl fluxcoil.net'
curl: (6) getaddrinfo() thread failed to start
# podman run -it registry.fedoraproject.org/fedora:36 bash -c 'curl fluxcoil.net'
curl: (6) getaddrinfo() thread failed to start

Comment 2 Christian Horn 2022-02-18 22:29:04 UTC
Workaround:

# podman run -it  --security-opt=seccomp=unconfined  registry.fedoraproject.org/fedora:36 bash -c 'curl fluxcoil.net'
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>

Comment 3 Ben Cotton 2022-11-29 17:22:56 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:57:36 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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