Uploaded image for project: 'Container Tools'
  1. Container Tools
  2. RUN-2511

podman artifact pull: --retry-delay values are ignored

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • rhel-9.6
    • None
    • 1
    • False
    • None
    • False
    • RUN 267

      Yuhui Jiang from QE reports that the value for --retry-delay on podman artifact pull is ignored.  The retries are in fact done but the interval is always the default value (1 sec).

      [root@kvm-01-guest14 ~]# podman artifact pull  --retry 2 --retry-delay 30 -q 127.0.0.1/testimage
WARN[0000] Failed, retrying in 1s ... (1/2). Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused
WARN[0001] Failed, retrying in 1s ... (2/2). Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused
Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused

       

              bbaude@redhat.com Brent Baude
              yujiang16 Yuhui Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: