Error after running or pulling through Nexus docker proxy

Sonatype Nexus Repository
1

1 was installed and configured docker proxy on Nexus host with ip 192.168.0.1
2 on host 192.168.0.2 was installed podman through the Nexus proxy with this config in /etc/containers/registries.conf:
[[registry]]
location=“192.168.0.1:8085”
insecure=true
While installing podman through nexus proxy there wasn’t any error, but when I run

podman run -it hello-world
Output:
“Resolved “hello-world” as an alias (/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull Docker…
Error: initializing source docker://hello-world: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”

In docker proxy configuration, below all are enabled:
1.Create an HTTP connector at specified port. Normally used if the server is behind a secure proxy.->8085
2.Allow anonymous docker pull ( Docker Bearer Token Realm required )
3.Allow clients to use the V1 API to interact with this repository
4.Remote storage: → https://registry-1.docker.io
5.Use Docker Hub
6.Allow Nexus Repository Manager to download and cache foreign layers
7.Blob store → default and all other parametres left as was, just docker bearer token realm switched to active
OS is Ubuntu 22.04 and just first host has an internet connection

2

podman info
host:
arch: amd64
buildahVersion: 1.23.1
cgroupControllers:

  • cpuset
  • cpu
  • io
  • memory
  • hugetlb
  • pids
  • rdma
  • misc
    cgroupManager: systemd
    cgroupVersion: v2
    conmon:
    package: ‘conmon: /usr/bin/conmon’
    path: /usr/bin/conmon
    version: ‘conmon version 2.0.25, commit: unknown’
    cpus: 2
    distribution:
    codename: jammy
    distribution: ubuntu
    version: “22.04”
    eventLogger: journald
    hostname: futureot-ds102p
    idMappings:
    gidmap: null
    uidmap: null
    kernel: 5.15.0-87-generic
    linkmode: dynamic
    logDriver: journald
    memFree: 3128795136
    memTotal: 4102029312
    ociRuntime:
    name: crun
    package: ‘crun: /usr/bin/crun’
    path: /usr/bin/crun
    version: |-
    crun version 0.17
    commit: 0e9229ae34caaebcb86f1fde18de3acaf18c6d9a
    spec: 1.0.0
    +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
    os: linux
    remoteSocket:
    exists: true
    path: /run/podman/podman.sock
    security:
    apparmorEnabled: true
    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: false
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
    serviceIsRemote: false
    slirp4netns:
    executable: /usr/bin/slirp4netns
    package: ‘slirp4netns: /usr/bin/slirp4netns’
    version: |-
    slirp4netns version 1.0.1
    commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
    libslirp: 4.6.1
    swapFree: 0
    swapTotal: 0
    uptime: 15h 16m 8.48s (Approximately 0.62 days)
    plugins:
    log:
  • k8s-file
  • none
  • journald
    network:
  • bridge
  • macvlan
    volume:
  • local
    registries:
    192.168.99.98:8085:
    Blocked: false
    Insecure: true
    Location: 192.168.99.98:8085
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: 192.168.99.98:8085
    store:
    configFile: /etc/containers/storage.conf
    containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
    graphDriverName: overlay
    graphOptions: {}
    graphRoot: /var/lib/containers/storage
    graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: “true”
    Supports d_type: “true”
    Using metacopy: “false”
    imageStore:
    number: 0
    runRoot: /run/containers/storage
    volumePath: /var/lib/containers/storage/volumes
    version:
    APIVersion: 3.4.4
    Built: 0
    BuiltTime: Thu Jan 1 00:00:00 1970
    GitCommit: “”
    GoVersion: go1.18.1
    OsArch: linux/amd64
    Version: 3.4.4
3

You need to use fully qualified image names that specify the registry, i.e. localhost:1234/hello-world

4

Thank u my friend. But now I got a new error:

podman run 192.168.99.98:8082/hello-world
Trying to pull 192.168.99.98:8082/hello-world:latest…
WARN[0000] Failed, retrying in 1s … (1/3). Error: initializing source docker://192.168.99.98:8082/hello-world:latest: pinging container registry 192.168.99.98:8082: Get “https://192.168.99.98:8082/v2/”: dial tcp 192.168.99.98:8082: connect: connection refused
WARN[0001] Failed, retrying in 1s … (2/3). Error: initializing source docker://192.168.99.98:8082/hello-world:latest: pinging container registry 192.168.99.98:8082: Get “https://192.168.99.98:8082/v2/”: dial tcp 192.168.99.98:8082: connect: connection refused
WARN[0002] Failed, retrying in 1s … (3/3). Error: initializing source docker://192.168.99.98:8082/hello-world:latest: pinging container registry 192.168.99.98:8082: Get “https://192.168.99.98:8082/v2/”: dial tcp 192.168.99.98:8082: connect: connection refused
Error: initializing source docker://192.168.99.98:8082/hello-world:latest: pinging container registry 192.168.99.98:8082: Get “https://192.168.99.98:8082/v2/”: dial tcp 192.168.99.98:8082: connect: connection refused