Introducing GitHub Container Registry

Hi Friends, I hope everyone is having a great day. Here to share some news:

Since releasing GitHub Packages last year, hundreds of millions of packages have been downloaded from GitHub, with Docker as the second most popular ecosystem in Packages behind npm. Our users are leaning increasingly towards containers, Kubernetes, and other cloud-native technologies to manage their entire application lifecycle – not just through development, release, and deployment, but for production operations as well.

While GitHub Packages already gives teams greater traceability of their software supply chain, today we’re adding new capabilities to improve the experience and performance it provides for developers with, to learn more check out: GitHub Container Registry .

Share your feedback

We’re looking forward to hearing from you on how we can make GitHub Packages and GitHub Container Registry even better – you can reach us on our community forums, or provide feedback directly to the product teams.


Great news! I already have a first problem with it :slightly_smiling_face: Any suggestions would be much appreciated.

1 Like

I notice that while Google Cloud is consolidating their package registries into one (they’re merging Google Container Registry into their new Artifact Registry), GitHub is moving in the opposite direction, splitting Docker images out of GitHub Packages into GitHub Container Registry. I wonder what reasons there would be for either approach.


Thanks for creating a separate topic with your concern @christian-korneck! I see you are being assisted. Your feedback is very much appreciated.

1 Like