docker HTTP API


Does the GitHub container registry ( support the docker V2 HTTP API’s?

Specifically, does it support listing repositories and tags (

1 Like

I guess the answer is “yes”. I’m assuming this from:

I can list the tags of a repo with skopeo:

docker run --rm list-tags docker://
    "Repository": "",
    "Tags": [

and when I run it with --debug there are clues that it’s indeed using the v2 endpoint:

level=debug msg="GET"

/v2/_catalog support is in our backlog! It hasn’t arrived yet but we know we need it.


Thanks for the confirmation.

For context (and just in case it helps nudge it up the priority list), we make Octopus Deploy, and when integrating with container registries we use the HTTP catalog API to list the available repositories and tags in the UI.

1 Like

Thanks for that context! It does help.

Are there any other features / APIs that would be useful?

I know I am not the OP but here is what the DockerHub API provides now and it would be useful to have parity.

I guess it will be much more easy to publish graphql v4 api to list all repositories in registry related to user or organization than enabling /_catalog api which list basically all images. But both can do the job here.

It would be really useful to modify README and package descriptions through API. Not every package could be linked to single GitHub repository, or the repository might have multiple packages.

Also, if the implementation of repository listing shows last modified time or Manifest hash, that would be neat - based on the list I could see which packages have changed since querying API last time.