Note: It is both a show & tell and a discussion. (sorry for bad flair)
Few months ago I built a docker registry ui. I am now migrating it to Golang. I’ve started my Golang journey 5 years ago, but didn’t dive further. (Side note: I managed to scrape around 10K image tags under 13 sec. Thanks Golang)
Anyway I am back to using Golang, and now that I am building an OSS tool, I thought while I was at it, why not extract one part of it into a package.
Here is the package:
https://github.com/eznix86/registry-client
Basically for my own use case for the Docker Registry UI, I needed to have a…
Note: It is both a show & tell and a discussion. (sorry for bad flair)
Few months ago I built a docker registry ui. I am now migrating it to Golang. I’ve started my Golang journey 5 years ago, but didn’t dive further. (Side note: I managed to scrape around 10K image tags under 13 sec. Thanks Golang)
Anyway I am back to using Golang, and now that I am building an OSS tool, I thought while I was at it, why not extract one part of it into a package.
Here is the package:
https://github.com/eznix86/registry-client
Basically for my own use case for the Docker Registry UI, I needed to have a simple library to get what I need. I could have use podman or docker code, but... if I am building my own UI why not just code my own library.
The idea behind this library is to support multiple docker registry behind a simple API (for my use case).
Right now It supports Docker Registry v2/v3, Github Packages. I plan to add AWS ECR, Google Artifact Registry, Azure Container Registry, Docker Hub, Zot Registry and Gitea. So I could benefit me and maybe other people!
Let me know what you think. I am open for criticism.