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

Docker pull from mcr.microsoft.com results in 403

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.15.2
    • Fix Version/s: 3.16.0
    • Component/s: Docker

      Description

      Pulling from 'mcr.microsoft.com' via a proxy repository results in a 403, whilst pulling directly from 'mcr.microsoft.com' does not:

      pull directly:

      docker pull mcr.microsoft.com/powershell:6.1.2-centos-7
      6.1.2-centos-7: Pulling from powershell
      a02a4930cb5d: Already exists 
      4044620d387b: Pull complete
      e2ccf76d7aff: Pull complete
      Digest: sha256:e51d267ccb4caddabe411c194949f390e8762d7e765ceac9bfd8569615a3ad45
      Status: Downloaded newer image for mcr.microsoft.com/powershell:6.1.2-centos-7
      

       

      pulling via proxy repo (remote URL set to: https://mcr.microsoft.com):

      $ docker pull nexus3:8085/powershell:6.1.2-centos-7
      6.1.2-centos-7: Pulling from powershell 
      a02a4930cb5d: Already exists
      4044620d387b: Pulling fs layer 
      e2ccf76d7aff: Pulling fs layer
      error pulling image configuration: unauthorized: access to the requested resource is not authorized
      

      Expected:

      Pulling via proxy repo should behave in the same way as pulling directly from mcr.microsoft.com.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                moncef Moncef Ben-Soula
                Reporter:
                hardeepn Hardeep Nagra
                CC:
                May Large
                Last Updated By:
                Moncef Ben-Soula
                Team:
                NXRM - Cypher
              • Votes:
                2 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: