podman: Podman unable to resolve DNS queries(?) — aka pulling images does not work
Is this a BUG REPORT or FEATURE REQUEST?:
[//]: # kind bug
Description
Pulling new images does not work. Podman returns no such host for all of the registries it tries to hit. This issue does not happen with Docker on the same system.
I also tried running with SELinux set to permissive, since I had similar issues once before with Docker. However, there was no change with SELinux set to permissive.
Steps to reproduce the issue:
- podman run --rm -it fedora bash
Describe the results you received:
Trying to pull docker.io/fedora:latest...Failed
Trying to pull registry.fedoraproject.org/fedora:latest...Failed
Trying to pull quay.io/fedora:latest...Failed
Trying to pull registry.access.redhat.com/fedora:latest...Failed
Trying to pull registry.centos.org/fedora:latest...Failed
unable to pull fedora: 5 errors occurred:
* Error determining manifest MIME type for docker://fedora:latest: pinging docker registry returned: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io: no such host
* Error determining manifest MIME type for docker://registry.fedoraproject.org/fedora:latest: pinging docker registry returned: Get https://registry.fedoraproject.org/v2/: dial tcp: lookup registry.fedoraproject.org: no such host
* Error determining manifest MIME type for docker://quay.io/fedora:latest: pinging docker registry returned: Get https://quay.io/v2/: dial tcp: lookup quay.io: no such host
* Error determining manifest MIME type for docker://registry.access.redhat.com/fedora:latest: pinging docker registry returned: Get https://registry.access.redhat.com/v2/: dial tcp: lookup registry.access.redhat.com: no such host
* Error determining manifest MIME type for docker://registry.centos.org/fedora:latest: pinging docker registry returned: Get https://registry.centos.org/v2/: dial tcp: lookup registry.centos.org: no such host
Describe the results you expected:
[root@hostname /] #
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
I’m using the official Fedora package.
podman version 0.10.1.3
Output of podman info:
host:
BuildahVersion: 1.5-dev
Conmon:
package: podman-0.10.1.3-1.gitdb08685.fc28.x86_64
path: /usr/libexec/podman/conmon
version: 'conmon version 1.12.0-dev, commit: 4a03e555ee4105308fa4d814d4ce02a059af0b7f-dirty'
Distribution:
distribution: fedora
version: "28"
MemFree: 10145501184
MemTotal: 16693481472
OCIRuntime:
package: runc-1.0.0-59.dev.gitccb5efd.fc28.x86_64
path: /usr/bin/runc
version: 'runc version spec: 1.0.1-dev'
SwapFree: 8388603904
SwapTotal: 8388603904
arch: amd64
cpus: 4
hostname: fossbook.justinwflory.com
kernel: 4.19.5-200.fc28.x86_64
os: linux
uptime: 3h 57m 47.64s (Approximately 0.12 days)
insecure registries:
registries: []
registries:
registries:
- docker.io
- registry.fedoraproject.org
- quay.io
- registry.access.redhat.com
- registry.centos.org
store:
ContainerStore:
number: 0
GraphDriverName: vfs
GraphOptions: []
GraphRoot: /home/jflory/.local/share/containers/storage
GraphStatus: {}
ImageStore:
number: 0
RunRoot: /run/user/1000/run
Additional environment details (AWS, VirtualBox, physical, etc.):
Bare-metal Fedora 28 Workstation (4.19.5-200.fc28.x86_64).
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 34 (30 by maintainers)
Could have been some network setup problems on this machine?
Alright, you clearly have a valid nameserver, and yet just as clearly the Go code can’t make DNS queries.
@mtrmac It seems like we’re failing in c/image here, but I’m pretty sure none of the image code does things that would affect DNS resolution
@jwflory Anything unusual about your setup? I’m pretty sure this is a Go standard library HTTP request failing, which is very well tested and should be basically foolproof for a simple query like this, so I’m thinking we might be seeing some sort of environment issue.