Container Registry is deprecated. Effective March 18, 2025, Container Registry is shut down and writing images to Container Registry is unavailable. For more information about the Container Registry deprecation and how to migrate to Artifact Registry, see Container Registry deprecation.
Stay organized with collections
Save and categorize content based on your preferences.
Container Registry is deprecated. Effective March 18, 2025,
Container Registry is shut down and writing images to Container Registry is
unavailable.
Container Registry shutdown
The shutdown is scheduled as follows:
Effective March 18, 2025, writing images to Container Registry is
unavailable.
After June 03, 2025, reading images from Container Registry is
unavailable. Existing images in Container Registry are inaccessible.
Effective October 14, 2025, if you have completed the steps to set up
gcr.io repositories in Artifact Registry, then
pushing to gcr.io endpoints stores images in Artifact Registry and all
gcr.io URLs are served from Artifact Registry. Any images
in Container Registry that haven't been copied to Artifact Registry are
unavailable.
Transition to Artifact Registry
Depending on how you configure and use Container Registry, you might
need to perform some configuration steps to prepare a new project to successfully
handle requests to the gcr.io domain. For example, principals that access
the repositories must have an appropriate Artifact Registry role or a role with
equivalent permissions.
We recommend that you transition projects with active Container Registry usage to
Artifact Registry repositories. See Transition from Container Registry
to learn about feature differences and transition options.
Use our transition tooling
Use the following tools to check which projects have Container Registry usage,
copy images from Container Registry to Artifact Registry, and automatically migrate
multiple projects from Container Registry to Artifact Registry.
Use our migration tool to migrate projects from
Container Registry to Artifact Registry, copy images, and select your preferred
transition repository type.
The following restrictions were implemented as part of our phased approach to
discontinuing Container Registry:
Effective March 18, 2025, writing images to Container Registry is
unavailable.
Effective January 8, 2024, in organizations that haven't used
Container Registry before, and in projects that don't belong to organizations,
all new gcr.io repositories are hosted on Artifact Registry by default.
Effective May 15, 2024, Google Cloud projects without previous usage of
Container Registry only support gcr.io repositories hosted in
Artifact Registry.
Effective May 15, 2023, Container Registry is deprecated.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eContainer Registry is being shut down, with writing images unavailable after March 18, 2025, and reading images unavailable after May 20, 2025.\u003c/p\u003e\n"],["\u003cp\u003eAfter July 17, 2025, \u003ccode\u003egcr.io\u003c/code\u003e endpoints will store images in Artifact Registry if the setup is complete, and any images not copied from Container Registry will be inaccessible.\u003c/p\u003e\n"],["\u003cp\u003eTransitioning to Artifact Registry is recommended for active Container Registry users, and it requires certain configuration steps, such as appropriate role assignment.\u003c/p\u003e\n"],["\u003cp\u003eTools are available to check Container Registry usage, copy images, and migrate projects to Artifact Registry.\u003c/p\u003e\n"],["\u003cp\u003eNew \u003ccode\u003egcr.io\u003c/code\u003e repositories in organizations and projects without prior Container Registry use are already hosted on Artifact Registry, as of January 8, 2024, and as of May 15, 2024 projects without previous usage of Container Registry only support \u003ccode\u003egcr.io\u003c/code\u003e repositories hosted in Artifact Registry.\u003c/p\u003e\n"]]],[],null,["# Container Registry deprecation\n\nContainer Registry is deprecated. Effective March 18, 2025, Container Registry is shut down and writing images to Container Registry is unavailable.\n\n\u003cbr /\u003e\n\nContainer Registry shutdown\n---------------------------\n\nThe shutdown is scheduled as follows:\n\n- Effective March 18, 2025, writing images to Container Registry is unavailable.\n- After June 03, 2025, reading images from Container Registry is unavailable. Existing images in Container Registry are inaccessible.\n- Effective October 14, 2025, if you have completed the steps to set up [`gcr.io` repositories](/artifact-registry/docs/transition/gcr-repositories) in Artifact Registry, then pushing to `gcr.io` endpoints stores images in Artifact Registry and all `gcr.io` URLs are served from Artifact Registry. Any images in Container Registry that haven't been copied to Artifact Registry are unavailable.\n\nTransition to Artifact Registry\n-------------------------------\n\nDepending on how you configure and use Container Registry, you might\nneed to perform some configuration steps to prepare a new project to successfully\nhandle requests to the `gcr.io` domain. For example, principals that access\nthe repositories must have an appropriate Artifact Registry role or a role with\nequivalent permissions.\n\nWe recommend that you transition projects with active Container Registry usage to\nArtifact Registry repositories. See [Transition from Container Registry](/artifact-registry/docs/transition/transition-from-gcr)\nto learn about feature differences and transition options.\n\nUse our transition tooling\n--------------------------\n\n| **Warning:** After June 03, 2025, if you haven't transitioned to Artifact Registry, then images in Container Registry are inaccessible.\n\nUse the following tools to check which projects have Container Registry usage,\ncopy images from Container Registry to Artifact Registry, and automatically migrate\nmultiple projects from Container Registry to Artifact Registry.\n\n- [Check Container Registry usage](/artifact-registry/docs/transition/check-gcr-usage).\n- Use our [migration tool](/artifact-registry/docs/transition/auto-migrate-gcr-ar) to migrate projects from Container Registry to Artifact Registry, copy images, and select your preferred transition repository type.\n\nWe will continue to communicate changes to the service in accordance with the\n[Google Cloud terms of service](/terms).\n\nContainer Registry deprecation history\n--------------------------------------\n\nThe following restrictions were implemented as part of our phased approach to\ndiscontinuing Container Registry:\n\n- Effective March 18, 2025, writing images to Container Registry is unavailable.\n- Effective January 8, 2024, in organizations that haven't used Container Registry before, and in projects that don't belong to organizations, all new `gcr.io` repositories are hosted on Artifact Registry by default.\n- Effective May 15, 2024, Google Cloud projects without previous usage of Container Registry only support `gcr.io` repositories hosted in [Artifact Registry](/artifact-registry/docs).\n- Effective May 15, 2023, Container Registry is deprecated."]]
