Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-4866

Unable to pull images from private registry using crictl

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 4.11
    • Windows Containers
    • None
    • Low
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:
      From rhn-support-anowak
      the customer tagged pre-pulled the pause image and tagged them with the proper value in the golden VM image, the node becomes ready, but spinning up pods on the node with a image from the internal registry does not work with WMCO 6.x.
      Please see the error below

      administrator@XXXX C:\k>crictl.exe pull docker.XXXX.apps.XXXX.net/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2022
      E1017 12:56:06.497299    6872 remote_image.go:242] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"docker.XXXX.apps.XXXX.net/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2022\": failed to copy: httpReadSeeker: failed open: failed to do request: Get \"https://mcr.microsoft.com/v2/windows/servercore/blobs/sha256:97f65a0ec59e643faf84024aa713a9be059322380315fda829756bbbd96d6258\": dial tcp: lookup mcr.microsoft.com: no such host" image="docker.XXXX.apps.XXXX.net/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2022"
      time="2022-10-17T12:56:06-04:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"docker.XXXX.apps.XXXX.net/dotnet/framework/samples:aspnetapp-windowsservercore-ltsc2022\": failed to copy: httpReadSeeker: failed open: failed to do request: Get \"https://mcr.microsoft.com/v2/windows/servercore/blobs/sha256:97f65a0ec59e643faf84024aa713a9be059322380315fda829756bbbd96d6258\": dial tcp: lookup mcr.microsoft.com: no such host"
      

      same image I can pull using docker and WMCO5.1

      Version-Release number of selected component (if applicable):

      6.0.0
      

      How reproducible:

      Always
      

      Steps to Reproduce:

      1. Push an image to a private registry
      2. Trying pulling the image using crictl in a Windows node
      

      Actual results:

      Described above
      

      Expected results:

      Image should be pulled
      

      Additional info:

      
      

            team-winc Team WinC
            paravindh Aravindh Puthiyaparambil
            Aharon Rasouli Aharon Rasouli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: