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!

    Docker Registry API - User Agent String Required?

    Scheduled Pinned Locked Moved Support
    apiproget
    4 Posts 1 Posters 43 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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      I am glad to see in 4.7.9 the catalog endpoint is allowed - however i believe there is a unnecessary restriction in the DockerAbsoluteUrlHandler class in the ProGet.WebApplication.dll - it appears the code requires that the User-Agent starts with "docker" (GetHttpHandler - method)

      This is limiting - for example Octopus does not send this User-Agent when calling docker registry endpoints. I would recommend removing that restriction.

      Product: ProGet
      Version: 4.7.9

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        It's actually the only way to tell whether a request is intended for the Docker API.

        We could make an exception for the catalog endpoint specifically, as nothing else should be using that URL. Would that be sufficient, or would it just cause problems if/when Octopus tries to access some other API endpoint for a Docker feed?

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Dean - that feels like a poor solution for calling an api - i feel like it should function regardless of user agent. I would image that octopus calls other docker registry api commands.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            I agree that it is a poor solution, but we do not have very many good solutions for this. Docker itself does not support prefixing private repositories; everything is assumed to be hosted in the same manner as the public registry (ie, absolute URL path from the server root), and assuming all /v2/ requests are Docker without some other declaration of intent in the request didn't seem good either.

            That said, if there's no collisions with anything else using that URL, we can change the default behavior.

            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