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

Replicating a Docker repository between 4.X and 5.X causes manifest.json to be corrupted

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Docker
    • Labels:
      None

      Description

      A client was pushing Docker images from an older Artifactory 4.12.2 instance to a new 5.1.2 instance using push replication. They noticed that all the manifest.json files from the older Artifactory instance could not be downloaded by their docker client from the 5.1.2 instance.

      This is because the manifest.json file used two schema in its metadata:

      {{2017-03-20 09:21:39,967 Content-Type: application/docker.distribution.manifest.v1
      2017-03-20 09:21:39,967 Content-Length: 502
      2017-03-20 09:21:39,967 Date: Mon, 20 Mar 2017 13:21:39 GMT
      {
      "schemaVersion": 2,}}

      During the replication process the Docker file's Content-Type changes from a V2 manifest to a V1 manifest.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              patrickr Patrick Russell
              Votes:
              8 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: