You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to run the command podman pull, the operation fails with a dial tcp: lookup: Temporary failure in name resolution error, despite successful authentication using podman login. This issue persists even after verifying that the DNS cache is cleared and all required Docker credentials are correct.
Note: Private Registry is in some other Network and accessed via VPN
I am using Podman Desktop v1.14.2 on MacOS 15.1.1 [OS/Arch: darwin]
Steps to reproduce the issue
Observed Behavior:
The podman login command completes successfully, indicating authentication with the Private Registry.
The podman pull command fails with an error message containing "Temporary failure in name resolution".
Describe the results you received
podman login private-registry.local
Authenticating with existing credentials for private-registry.local
Existing credentials are valid. Already logged in to private-registry.local
podman pull private-registry.local/image-repo/test-image:latest
Trying to pull private-registry.local/image-repo/test-image:latest...
Error: initializing source docker://private-registry.local/image-repo/test-image:latest: pinging container registry private-registry.local: Get "https://private-registry.local/v2/": dial tcp: lookup private-registry.local: Temporary failure in name resolution
Describe the results you expected
Expected Behavior:
The podman pull command should successfully retrieve images from a registry without encountering any network-related errors if it was able to authenticate prior.
podman info output
host:
arch: arm64buildahVersion: 1.36.0cgroupControllers:
- cpuset
- cpu
- io
- memory
- pids
- rdma
- misccgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.10-1.fc40.aarch64path: /usr/bin/conmonversion: 'conmon version 2.1.10, commit: 'cpuUtilization:
idlePercent: 99.78systemPercent: 0.09userPercent: 0.13cpus: 6databaseBackend: sqlitedistribution:
distribution: fedoravariant: coreosversion: "40"eventLogger: journaldfreeLocks: 2043hostname: localhost.localdomainidMappings:
gidmap: nulluidmap: nullkernel: 6.8.11-300.fc40.aarch64linkmode: dynamiclogDriver: journaldmemFree: 10300002304memTotal: 15562801152networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.11.0-1.20240628130058229856.main.10.g5ad6420.fc40.aarch64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.12.0-devpackage: netavark-1.11.0-1.20240702123536284903.main.32.g49fb0c2.fc40.aarch64path: /usr/libexec/podman/netavarkversion: netavark 1.12.0-devociRuntime:
name: crunpackage: crun-1.15-1.20240708144150212138.main.51.g6c158dd.fc40.aarch64path: /usr/bin/crunversion: |- crun version UNKNOWN commit: 54f958d21c4e2299eae6b0f4d8b742304540dce6 rundir: /run/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20240624.g1ee2eca-1.fc40.aarch64version: | pasta 0^20240624.g1ee2eca-1.fc40.aarch64-pasta 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: truepath: /run/podman/podman.sockrootlessNetworkCmd: pastasecurity:
apparmorEnabled: falsecapabilities: 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_CHROOTrootless: falseseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: trueserviceIsRemote: trueslirp4netns:
executable: /usr/bin/slirp4netnspackage: slirp4netns-1.2.2-2.fc40.aarch64version: |- slirp4netns version 1.2.2 commit: 0ee2d87523e906518d34a6b423271e4826f71faf libslirp: 4.7.0 SLIRP_CONFIG_VERSION_MAX: 4 libseccomp: 2.5.5swapFree: 0swapTotal: 0uptime: 39h 31m 54.00s (Approximately 1.62 days)variant: v8plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- docker.iostore:
configFile: /usr/share/containers/storage.confcontainerStore:
number: 2paused: 0running: 2stopped: 0graphDriverName: overlaygraphOptions:
overlay.imagestore: /usr/lib/containers/storageoverlay.mountopt: nodev,metacopy=onoverlay.use_composefs: "false"graphRoot: /var/lib/containers/storagegraphRootAllocated: 106769133568graphRootUsed: 31234764800graphStatus:
Backing Filesystem: xfsNative Overlay Diff: "false"Supports d_type: "true"Supports shifting: "true"Supports volatile: "true"Using metacopy: "true"imageCopyTmpDir: /var/tmpimageStore:
number: 34runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.1.2Built: 1720569600BuiltTime: Tue Jul 9 20:00:00 2024GitCommit: ""GoVersion: go1.22.5Os: linuxOsArch: linux/arm64Version: 5.1.2
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Issue Description
When attempting to run the command
podman pull
, the operation fails with adial tcp: lookup: Temporary failure in name resolution
error, despite successful authentication usingpodman login
. This issue persists even after verifying that the DNS cache is cleared and all required Docker credentials are correct.I am using Podman Desktop v1.14.2 on MacOS 15.1.1 [OS/Arch: darwin]
Steps to reproduce the issue
Observed Behavior:
The
podman login
command completes successfully, indicating authentication with the Private Registry.The
podman pull
command fails with an error message containing "Temporary failure in name resolution".Describe the results you received
Describe the results you expected
Expected Behavior:
The
podman pull
command should successfully retrieve images from a registry without encountering any network-related errors if it was able to authenticate prior.podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: