Steps to reproduce the issue:
Be in a network that prohibits external DNS queries, disable external DNS communication or just use some only-locally available hostname in step 3.
Setup local DNS server/forwarder (e.g. systemd-resolved) so that the local address is in /etc/resolv.conf
Start any container (without --network host) and try to resolve a hostname (e.g. podman run --rm -it fedora curl -v ifconfig.me)
Describe the results you received:
curl: (6) Could not resolve host: ifconfig.me
Describe the results you expected:
No error (some IP address)
Additional information you deem important (e.g. issue happens only occasionally):
The contents of /etc/resolv.conf are:
Which would normally work (although I might not want to send my DNS requests somewhere else because I might have services available in a local network), but I am in a network that prohibits external DNS queries, so that doesn’t work.
If I leave just the slirp4netns nameserver there (echo nameserver 10.0.2.3 >/etc/resolv.conf) it works in a VM where I am trying to reproduce this issue. However on my original host, where I discovered this, 10.0.2.3 is still inaccessible (even though the version and the command-line of slirp4netns is identical, apart from the PID argument).
Output of podman version:
RemoteAPI Version: 1
Go Version: go1.12.2
Output of podman info --debug:
git commit: “”
go version: go1.12.2
podman version: 1.3.1
version: ‘conmon version 1.12.0-dev, commit: c9a4c48d1bff85033b7fc9b62d25961dd5048689’
runc version 1.0.0-rc8+dev
uptime: 19m 40.53s
Backing Filesystem: xfs
Native Overlay Diff: “false”
Supports d_type: “true”
Using metacopy: “false”
Additional environment details (AWS, VirtualBox, physical, etc.):
I am trying this in a Fedora 30 VM, clean install, as that is the easiest and cleanest reproducer I can get. I cannot reproduce the issue related to my local environment in there.