Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-21619

docker manifest.json properties are not propergated to cache repo on replication

    XMLWordPrintable

    Details

    • Severity:
      Medium
    • Requirement Status:

      UNCOVERED

      Description

      When you replicate a docker repository from one artifactory to another, the properties of the manifest.json only consist of

      artifactory.internal.etag 505cd6039b5dcf1b2889132adc294f26ea9f58eb

      Only after the first pull of the image from the artifactory the properties are created and then it looks like:

      docker.manifest  1.0.4-1
      docker.manifest.digest sha256:7266a62b05b9c1c801427da7f729df617e72f26f5860ed47b60e0ff17075b081
      docker.manifest.type application/vnd.docker.distribution.manifest.v2+json
      docker.repoName test-repo/test-image
      sha256 7266a62b05b9c1c801427da7f729df617e72f26f5860ed47b60e0ff17075b081
      artifactory.internal.etag 505cd6039b5dcf1b2889132adc294f26ea9f58eb

      This is a problem, when you for example take a backup from the repository on the caching artifactory. The images are useless then, because you get "missing signature key" errors, because of missing properties.

      We, for example, use one plugin https://github.com/jfrog/artifactory-user-plugins/tree/master/storage/remoteBackup

      But at the moment, that means that the backup does not work for images that were not pulled. And that means nearly all, if you have a active replication cron running.

        Attachments

          Issue Links

            Forms

              Activity

                  People

                  Assignee:
                  Unassigned
                  Reporter:
                  dwerdermann Daniel Werdermann
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      PagerDuty