Unable to pull image with podman

gabrielpantiru commented 7 months ago

Issue Description

I am unable to pull any image from podman, the output of the command "podman pull redis --log-level trace" is:

time="2024-02-27T06:51:22+02:00" level=info msg="C:\\Program Files\\RedHat\\Podman\\podman.exe filtering at log level trace"
time="2024-02-27T06:51:22+02:00" level=debug msg="Called pull.PersistentPreRunE(C:\\Program Files\\RedHat\\Podman\\podman.exe pull redis --log-level trace)"
time="2024-02-27T06:51:22+02:00" level=debug msg="SSH Ident Key \"C:\\\\Users\\\\gabriel.pantiru\\\\.ssh\\\\podman-machine-default\" SHA256:hEhhzkik4M6aRA74NLUNV390d/3G8dhGF6D5SVEE5cA ssh-ed25519"
time="2024-02-27T06:51:22+02:00" level=debug msg="DoRequest Method: GET URI: http://d/v4.9.2/libpod/_ping"
time="2024-02-27T06:51:22+02:00" level=debug msg="Loading registries configuration \"/etc/containers/registries.conf\""
time="2024-02-27T06:51:22+02:00" level=debug msg="Found credentials for docker.io in credential helper containers-auth.json in file C:\\Users\\gabriel.pantiru\\.config\\containers\\auth.json"
time="2024-02-27T06:51:22+02:00" level=debug msg="DoRequest Method: POST URI: http://d/v4.9.2/libpod/images/pull"
Resolving "redis" using unqualified-search registries (/etc/containers/registries.conf.d/999-podman-machine.conf)
Trying to pull docker.io/library/redis:latest...
Error: initializing source docker://redis:latest: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
time="2024-02-27T06:51:42+02:00" level=debug msg="Shutting down engines"

On docker pulling any images works fine with the same configuration.

Steps to reproduce the issue

Start podman
Run Command podman pull redis --log-level trace

Describe the results you received

Unable to pull podman image because of "Error: initializing source docker://redis:latest: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution"

Describe the results you expected

Image is pulled successfully and I should be able to create a container out of it with Podman.

podman info output

_ podman info
host:
arch: amd64
buildahVersion: 1.33.3
cgroupControllers: []
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: conmon-2.1.8-2.fc39.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.8, commit: '
cpuUtilization:
idlePercent: 99.92
systemPercent: 0.05
userPercent: 0.03
cpus: 8
databaseBackend: sqlite
distribution:
distribution: fedora
variant: container
version: "39"
eventLogger: journald
freeLocks: 2048
hostname: BUK30LAP4000893
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 524288
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 524288
size: 65536
kernel: 5.10.16.3-microsoft-standard-WSL2
linkmode: dynamic
logDriver: journald
memFree: 25862807552
memTotal: 26661605376
networkBackend: netavark
networkBackendInfo:
backend: netavark
dns:
package: aardvark-dns-1.10.0-1.fc39.x86_64
path: /usr/libexec/podman/aardvark-dns
version: aardvark-dns 1.10.0
package: netavark-1.10.3-1.fc39.x86_64
path: /usr/libexec/podman/netavark
version: netavark 1.10.3
ociRuntime:
name: crun
package: crun-1.14.3-1.fc39.x86_64
path: /usr/bin/crun
version: |-
crun version 1.14.3
commit: 1961d211ba98f532ea52d2e80f4c20359f241a98
rundir: /run/user/1000/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
os: linux
pasta:
executable: /usr/bin/pasta
package: passt-0^20231230.gf091893-1.fc39.x86_64
version: |
pasta 0^20231230.gf091893-1.fc39.x86_64
Copyright Red Hat
GNU General Public License, version 2 or later
https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.2-1.fc39.x86_64
version: |-
slirp4netns version 1.2.2
commit: 0ee2d87523e906518d34a6b423271e4826f71faf
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.5.3
swapFree: 7516192768
swapTotal: 7516192768
uptime: 11h 55m 2.00s (Approximately 0.46 days)
variant: ""
plugins:
authorization: null
log:

k8s-file
none
passthrough
journald
network:
bridge
macvlan
ipvlan
volume:
local
registries:
search:
docker.io
store:
configFile: /home/user/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /home/user/.local/share/containers/storage
graphRootAllocated: 269490393088
graphRootUsed: 637480960
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Supports shifting: "true"
Supports volatile: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /run/user/1000/containers
transientStore: false
volumePath: /home/user/.local/share/containers/storage/volumes
version:
APIVersion: 4.9.0
Built: 1706090847
BuiltTime: Wed Jan 24 12:07:27 2024
GitCommit: ""
GoVersion: go1.21.6
Os: linux
OsArch: linux/amd64
Version: 4.9.0_

Podman in a container

No

Privileged Or Rootless

Privileged

Upstream Latest Release

Yes

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

vrothberg commented 7 months ago

Thanks for reaching out. Are you behind a proxy? The error suggests a DNS issue which is commonly caused by proxies.

gabrielpantiru commented 7 months ago

Thanks for reaching out. Are you behind a proxy? The error suggests a DNS issue which is commonly caused by proxies.

Hello, unfortunately I am not connected to any proxy at the moment of trying the command

vrothberg commented 7 months ago

Thanks! Is the issue persistent or was it a transient network error?

gabrielpantiru commented 7 months ago

Yes, I tried again and the issue is still persisting

github-actions[bot] commented 6 months ago

A friendly reminder that this issue had no activity for 30 days.

thirteenthree commented 3 days ago

it really terrible

containers / podman