[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eContainer Registry is being shut down on March 18, 2025, and users must migrate to Artifact Registry to continue using container image storage.\u003c/p\u003e\n"],["\u003cp\u003eAfter March 18, 2025, writing images to Container Registry will be unavailable, and reading images will be unavailable after May 20, 2025.\u003c/p\u003e\n"],["\u003cp\u003eTo identify whether your Google Cloud environment uses Container Registry, you can utilize the Container Registry usage tool provided.\u003c/p\u003e\n"],["\u003cp\u003eAn automatic migration tool is available to help users transition from Container Registry to either \u003ccode\u003egcr.io\u003c/code\u003e or \u003ccode\u003epkg.dev\u003c/code\u003e Artifact Registry repositories, including the option to copy all existing container images.\u003c/p\u003e\n"],["\u003cp\u003eAfter validating all services are migrated and desired images are copied to Artifact Registry, users can proceed to clean up and delete Container Registry storage buckets.\u003c/p\u003e\n"]]],[],null,["# Prepare for Container Registry shutdown\n\nDetermine how you want to prepare for the shutdown of Container Registry.\n\nContainer Registry is deprecated. Effective March 18, 2025, Container Registry\nis shut down and writing images to Container Registry is unavailable.\n\n`gcr.io` URLs hosted on Artifact Registry, including Google-owned images\nwith `gcr.io` URLs, are not affected by the Container Registry shutdown.\n\nFor more details about the Container Registry deprecation and how to migrate to\nArtifact Registry, see\n[Container Registry deprecation](/container-registry/docs/deprecations/container-registry-deprecation).\n\nArtifact Registry is the recommended service for\ncontainer image storage and management on Google Cloud. Artifact Registry\nprovides the same container management features as Container Registry and it\nincludes additional features and benefits.\n\nWhat do I have to do?\n---------------------\n\nIf you have container images in Container Registry that you want to keep using,\nor you use a service that depends on Container Registry, such as App Engine,\nthen you must upgrade to use Artifact Registry repositories.\n\nWhat happens after March 18, 2025\n---------------------------------\n\nThe Container Registry shutdown has three stages:\n\n- Effective March 18, 2025, writing images to Container Registry is unavailable.\n- Effective June 03, 2025, reading images in Container Registry is unavailable.\n- Effective October 14, 2025, if you have completed the steps to set up\n [`gcr.io` repositories](/artifact-registry/docs/transition/gcr-repositories) in Artifact Registry, then\n pushing to `gcr.io` endpoints stores images in Artifact Registry and all\n `gcr.io` URLs are served from Artifact Registry. Any images\n in Container Registry that haven't been copied to Artifact Registry are\n unavailable.\n\n The [automatic migration tool](/artifact-registry/docs/transition/auto-migrate-gcr-ar) will still be available for\n migration after October 14, 2025.\n\nIdentify Container Registry usage and choose a transition option\n----------------------------------------------------------------\n\n1. Identify Container Registry usage within your Google Cloud project, folder,\n or organization. You can use our\n [Container Registry usage tool](/artifact-registry/docs/transition/check-gcr-usage) to determine if you are using\n Container Registry.\n\n2. If you have container images in Container Registry that you want to keep\n using, then determine which [transition option](/artifact-registry/docs/transition/transition-from-gcr#transition-options) you\n want to follow.\n\n3. If you don't need any of the images stored in Container Registry, then you\n can set up Artifact Registry `pkg.dev` repositories or Artifact Registry `gcr.io`\n repositories.\n\n To learn about the differences between Container Registry and\n Artifact Registry review the following:\n - [Changes for Docker](/artifact-registry/docs/transition/changes-docker)\n - [Changes for building and deploying in Google Cloud](/artifact-registry/docs/transition/changes-gcp)\n - [Migrate automatically to Artifact Registry](/artifact-registry/docs/transition/auto-migrate-gcr-ar)\n - [Artifact Registry overview](/artifact-registry/docs/overview)\n\nUse our transition tooling\n--------------------------\n\nUse the automatic migration tool to transition from Container Registry to\n`gcr.io` repositories hosted on Artifact Registry or to `pkg.dev` Artifact Registry\nrepositories.\n\nYou can migrate Container Registry endpoints to Artifact Registry\n`gcr.io` repositories without requiring any downtime or service disruption.\n\nThe automatic migration tool can perform the following actions depending on\nthe transition path you choose:\n\n- Create `gcr.io` repositories or `pkg.dev` repositories in Artifact Registry for each of your listed `gcr.io` projects in the corresponding region.\n- Suggest an IAM policy for each repository and apply the policy or skip application depending on user preference.\n- Redirect all traffic from `gcr.io` endpoints to Artifact Registry.\n- Copy all container images stored in Container Registry to your Artifact Registry `gcr.io` repositories or `pkg.dev` repositories, even if you have already enabled redirection.\n\nFor instructions on how to use the automatic migration tool, see\n[Automatically migrate from Container Registry to Artifact Registry](/artifact-registry/docs/transition/auto-migrate-gcr-ar).\n\nValidate your automation and integrations\n-----------------------------------------\n\nVerify that existing automation and integration with\nservices such as Cloud Build, Google Kubernetes Engine, Cloud Run functions, or any\nthird-party tooling you use to push or pull from your repository work as\nexpected.\n\nClean up Container Registry images\n----------------------------------\n\nWhen redirection is enabled, commands to delete images in `gcr.io` paths\ndelete images in the corresponding Artifact Registry `gcr.io` repository,\nbut they don't delete images stored on Container Registry hosts.\n\nAfter you have validated that all projects work with the transition option\nyou've chosen, and all images you want to keep have been copied to\nArtifact Registry, you can delete the Container Registry storage buckets. For\ninstructions on how to delete Cloud Storage buckets, see\n[Clean up images in Container Registry](/artifact-registry/docs/transition/clean-up-images-gcr)."]]