Migrating to the Container registry from the Docker registry

Docker images previously stored in the Docker registry are being automatically migrated to the container registry.

Paquetes de GitHub is available with GitHub Free, GitHub Pro, GitHub Free for organizations, GitHub Team, GitHub Enterprise Cloud, Servidor de GitHub Enterprise 2.22, and GitHub One.

Paquetes de GitHub no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Paquetes de GitHub se encuentra disponible con GitHub Free, GitHub Pro, GitHub Free para organizaciones, GitHub Team, GitHub Enterprise Cloud, y GitHub One. Para obtener más información, consulta la sección "Productos de GitHub".

En este artículo

GitHub's Docker registry has been replaced by the container registry. If you've stored Docker images in the Docker registry, they will be automatically moved to the container registry. You don't need to do anything. Any scripts or GitHub Actions workflows that use the namespace for the Docker registry (docker.pkg.github.com) will continue to work after the migration to the container registry (ghcr.io).

Migration is being done gradually, rather than all at once. If your images haven't yet been moved over, hold tight, we'll get to them sometime soon.

How can you tell if your images have been migrated?

After your Docker images have been migrated to the container registry you will see the following changes on the details page for a package:

  • The icon is now the container registry logo, previously it was a Docker logo.
  • The domain in the pull URL is now ghcr.io, previously it was docker.pkg.github.com.

container registry details page

Key differences between the container registry and the Docker registry

The container registry is optimized to support some of the unique needs of containers.

With the container registry you can:

  • Store container images within your organization and user account, or connect them to a repository.
  • Choose whether to inherit permissions from a repository, or set granular permissions independently of a repository.
  • Access public container images anonymously.

API queries for details of Docker images

After migration you'll no longer be able to use the GraphQL API to query for packages of PackageType "DOCKER". Instead, you can use the REST API to query for packages with the package_type "container". For more information, see the REST API article "Packages."


For more information about billing for the container registry, see "About billing for Paquetes de GitHub."

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.