The Container registry stores container images within your organization or personal account, and allows you to associate an image with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. You can also access public container images anonymously. For more information, see "Working with the Container registry."
The Container registry replaces GitHub's Docker registry. If you've stored Docker images in the Docker registry, GitHub will gradually migrate the images to the Container registry. No action is required on your part.
After a Docker image has been migrated to the Container registry, you'll see the following changes to the details for the package.
- The package icon will be the Container registry logo (a icon) instead of the Docker logo.
- The domain in the pull URL will be
Any scripts or GitHub Actions workflows that use the namespace for the Docker registry,
docker.pkg.github.com, will continue to work after migration to the Container registry at
After migration, you'll no longer be able to use the GraphQL API to query for packages with a
PackageType of "DOCKER". Instead, you can use the REST API to query for packages with a
package_type of "container". For more information, see "REST API endpoints for packages."
For more information about billing for the Container registry, see "About billing for GitHub Packages."