Bug 1648429

Summary: Name resolution fails in containers created by podman version 10.1.3-4.gitee513cc
Product: Red Hat Enterprise Linux 7 Reporter: dagray
Component: podmanAssignee: Brent Baude <bbaude>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.6CC: bbaude, dwalsh, fkluknav, jligon, lsm5, mheon, nofow93638, perfbz, smccarty, umohnani, ypu
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: podman-0.11.1.1-1.git594495d.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-28 08:01:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dagray 2018-11-09 17:17:51 UTC 
DNS fails in podman containers after recent update to podman-0.10.1.3-4.gitee513cc.el7.x86_64. This error does not occur on podman version 0.10.1.3-1. 

Failing versions:
RPM name:
podman-0.10.1.3-4.gitee513cc.el7.x86_64

# podman --version
podman version 0.10.2-dev


Steps to Reproduce:
# podman run -it --rm alpine ping redhat.com

ping: bad address 'redhat.com'

or 

# podman run -it --rm alpine apk update
Comment 2 Matthew Heon 2018-11-09 17:26:04 UTC 
I believe we've landed a fix for this upstream already. It doesn't look like it made it into the most recent 0.11.1 release, but we'll see about getting a build with the fix out quickly.
Comment 5 Joy Pu 2018-11-16 05:08:42 UTC 
*** Bug 1649640 has been marked as a duplicate of this bug. ***
Comment 6 Joy Pu 2018-11-16 07:20:53 UTC 
Test with podman-0.11.1.1-3.git594495d.el7.x86_64. And the version is already updated.
# podman version
Version:       0.11.1.1
Go Version:    go1.10.2
OS/Arch:       linux/amd64

So set this to verified.
Comment 8 errata-xmlrpc 2018-11-28 08:01:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3715
Comment 9 PassionApk 2022-06-20 09:21:52 UTC Comment hidden (spam)
Comment 10 Red Hat Bugzilla 2023-09-15 01:27:52 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days