Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Pull Docker Images from Remote Connector

    Scheduled Pinned Locked Moved Support
    proget
    3 Posts 3 Posters 39 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      jrottmann_7642
      last edited by

      Whenever trying to pull an image for windows container from a remote connector we get a not found error. When there are images that have tags for windows and linux containers then proget finds it, but as soon as you click on a tag linking to the windows image a not found error occurs.

      You can find a screenshot attached to Support-Ticket EDO-5213 here.

      This is the error in the admin log:

      Message: An error occurred in the web application: Could not find specified image.
      Details: URL: https://proget/docker-images/details?feedId=11&repositoryName=library%2Fhello-seattle&imageDigest=nanoserver-1803
      Referrer: https://proget/feeds/general-test/library%2Fhello-seattle
      User: Admin
      User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36
      Stack trace: at Inedo.ProGet.WebApplication.Pages.Docker.Images.DockerImageDetailsPage.<InitializeAsync>d__15.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.Web.PageFree.SimplePageBase.<ProcessRequestAsync>d__46.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
      at Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest(IAsyncResult result)
      at System.Web.HttpApplication.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar)
      at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

      Product: ProGet
      Version: 5.1.7

      1 Reply Last reply Reply Quote 0
      • benB Offline
        ben inedo-engineer
        last edited by

        Hello Jan,

        I've filed PG-1350 to improve the error message when no connector successfully returns a manifest.

        1 Reply Last reply Reply Quote 0
        • I Offline
          inedo_6390
          last edited by

          Hello,

          Just following up: The root cause of Windows images from connectors not working is that ProGet was not telling the connector that it supported v2 manifests, and the v1 manifests generated for Windows images by Docker Hub are broken.

          This is PG-1351.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation