Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-11865

add support for docker foreign layer references


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.0, 3.2.0
    • Fix Version/s: None
    • Component/s: Docker



      Make Docker Repository Format support in Nexus 3 support foreign layers as described in that github issue.

      In the description of the docker github problem, it states:

      Additional information you deem important (e.g. issue happens only occasionally):

      Dockerd 1.12 & 1.12.2 also have this issue.

      Further down, a docker support person states:

      looks like that's not an official version of the registry, but a version packaged by Red Hat. Support for foreign layers was added in version 2.5 https://github.com/docker/distribution/releases/tag/v2.5.0, and is needed for Windows based images because the base layers are only allowed to be distributed by Microsoft (for legal reasons). When pushing an image based on those images, only your layers will be pushed to the registry, but the base layer is not pushed (a reference to the foreign location is included in the image's manifest).

      So it is entirely possible this will happen when using any docker client that can push images with foreign layers, including 1.12.* and 1.13.*.

      What matters is the image being pushed and if that image has foreign layers.


          Issue Links



              • Assignee:
                plynch Peter Lynch
                Last Updated By:
                Kelly Robinson
              • Votes:
                17 Vote for this issue
                26 Start watching this issue


                • Created:
                  Date of First Response: