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 _catalog and tags calls do not respect tokens



  • I am having problem with getting the catalog of docker repositories. Here is an example of the call I am trying:

    curl -X GET -u api:mytokenhere  -v https://myproget.company.net/v2/_catalog
    

    This returns only the repositories that are setup to allow anonymous access. The token I am using is setup specifically for one repository. But that one is not in the list.

    To say it another way, I get the exact same results if I run it without a user.

    curl -X GET -v https://myproget.company.net/v2/_catalog
    

    I thought it might be my token user, so I made a new token with full control (over all of Proget) and got the exact same results.

    I then thought to try listing tags, like this:

    curl -u api:mytokenhere https://myproget.company.net/v2/myfeed/prefix/container-here/tags/list
    

    I got this error:

    {"errors":[{"code":"UNAUTHORIZED",
                "message":"Anonymous is not permitted to perform the Feeds_ViewFeed task for the current scope.",
                "detail":[{"Type":"repository","Name":"myfeed/prefix/container-here","Action":"pull"}]}]}
    

    My token is setup with "Feed (use certain feeds)", and then I have selected my feed in the next level down. It has the checkboxes "View/Downlaod" and "Add/Repackage" checked. "Promote" and "Overwrite/Delete" are unchecked.

    How can I get the _catalog and tags call to show me more than just anonymous results?


  • inedo-engineer

    Hi @Stephen-Schaff ,

    The Docker API does not use API keys but a ticket-based system (i.e. docker login). Here is how to use it:
    https://docs.inedo.com/docs/proget/docker/semantic-versioning#example-powershell-script-to-authenticate-to-docker

    We added some kind of support via PG-3206 in ProGet 2025.20, though it was only intended to address self-connectors to Docker registries. I do'nt know how well it will work here.

    Thanks,
    Alana


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation