Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-40812

[skopeo-1.16] Listing tags in JFrog Artifactory may fail - Skopeo RHEL 9.5

    • skopeo-1.16.0-1.el9
    • None
    • Moderate
    • 2
    • sst_container_tools
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • RUN 256, RUN 257
    • None

      From https://github.com/containers/skopeo/issues/2346

      with fix in c/image: https://github.com/containers/image/pull/2440

      Hello team,

      I want to notify I have encountered en error on skopeo v1.15.1 with multiarch images on JFrog Artifactory.

      JFrog Artifactory is an artifact management tool that can be behaved as container image registry.
      However, for multiarch images, it violates some behaviors related to tags.

      For example,

      1. once pushed an multiarch image multi-arch:v1.0.0, which refers sha256:aaaa...aaaa as a amd64, and sha256:bbbb...bbbb as a arm64, to Artifactory,
      2. Artifactory expose sha256:aaaa...aaaa and sha256:bbbb...bbbb as tags, not only multi-arch:v1.0.0,
      3. and sha256:aaaa...aaaa and sha256:bbbb...bbbb are OCI incompliant tags because they contains :,

      So finally we got error on skopeo inspect with time="2024-06-03T09:26:46Z" level=fatal msg="Error determining repository tags: registry returned invalid tag \"sha256:aaaa...aaaa": invalid tag format".

      This is quite heavy impact issue even if the Artifactory violates OCI specifications, we can no longer use skopeo v1.15.1 or later with Artifactory.

      Can you consider that skopeo simply ignores the invalid tags to keep compatibility?
      And we will also contact to JFrog support to improve the behavior above.

              rhn-support-jnovy Jindrich Novy
              tsweeney@redhat.com Tom Sweeney
              Container Runtime Eng Bot Container Runtime Eng Bot
              Yuhui Jiang Yuhui Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: