[[["易于理解","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-08-18。"],[[["\u003cp\u003eArtifact Registry now supports \u003ccode\u003egcr.io\u003c/code\u003e repositories, allowing Container Registry users to maintain their existing Google Cloud infrastructure and \u003ccode\u003egcr.io\u003c/code\u003e URLs while storing container images in Artifact Registry.\u003c/p\u003e\n"],["\u003cp\u003eNew \u003ccode\u003egcr.io\u003c/code\u003e repositories are hosted on Artifact Registry by default for organizations and projects that haven't used Container Registry before January 8, 2024 and May 15, 2024, respectively.\u003c/p\u003e\n"],["\u003cp\u003eContainer Registry will remain available until March 18, 2025, in projects that either enabled the Container Registry API or pushed an image to a registry host before May 15, 2024.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry's \u003ccode\u003egcr.io\u003c/code\u003e repositories have predefined names and specific multi-regional location mappings that align with Container Registry host locations, and they do not create corresponding Cloud Storage buckets, requiring updates to any existing storage bucket automations.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003egcr.io\u003c/code\u003e repository mapping to Artifact Registry from container registry is limited to the same project only, and \u003ccode\u003epkg.dev\u003c/code\u003e repositories are available for those who need more granular control.\u003c/p\u003e\n"]]],[],null,["# gcr.io repositories\n\nThis document provides an overview of Artifact Registry `gcr.io`\nrepositories. `gcr.io` repositories let Container Registry users maintain\ntheir existing Google Cloud infrastructure by storing container images\nin Artifact Registry and supporting requests to the same `gcr.io` URLs used\nby Container Registry.\n\n`gcr.io` repositories hosted on Artifact Registry are a\n[Generally Available](https://cloud.google.com/products#product-launch-stages)\nfeature, and they will continue to work after the Container Registry deprecation.\n\nTo transition to `gcr.io` repositories on Artifact Registry, follow the\ninstructions in\n[Migrate automatically to Artifact Registry](/artifact-registry/docs/transition/auto-migrate-gcr-ar).\n\nBackground information on Container Registry deprecation\n--------------------------------------------------------\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\n`gcr.io` domain support\n-----------------------\n\nArtifact Registry supports requests to the `gcr.io` domain in `gcr.io`\nrepositories in multi-regional locations corresponding with Container Registry\nhost locations.\n\nStorage bucket configuration\n----------------------------\n\nWhen you create a repository in Artifact Registry, Artifact Registry does not create\ncorresponding Cloud Storage buckets in your project. If you have automation\nfor Container Registry that interacts directly with storage buckets, you must\nupdate it to make corresponding changes to the Artifact Registry repository.\n\nFor example, if you programmatically grant Cloud Storage permissions on\nstorage buckets for Container Registry, you must update that automation to grant\nArtifact Registry permissions on the Artifact Registry repositories that host images for\nthe `gcr.io` domain.\n\nLimitations\n-----------\n\nThe following limitations apply to Artifact Registry `gcr.io` repositories:\n\n- When transitioning from Container Registry, you cannot map a Container Registry\n host to an Artifact Registry repository in a different project.\n\n | **Note:** You can still pull container images in a `gcr.io` repository from other Google Cloud projects.\n- Each Container Registry hostname maps to only one corresponding\n Artifact Registry `gcr.io` repository in the same multi-region.\n\n- Names for `gcr.io` repositories are predefined and you can't modify them.\n\nIf you need more control over the location of your repositories, you can\ntransition to `pkg.dev` repositories in Artifact Registry. Since `pkg.dev`\nrepositories don't have any support for the `gcr.io` domain, this transition\napproach requires more changes to your existing automation and workflows. See\n[Choose a transition option](/artifact-registry/docs/transition/transition-from-gcr#transition-options) to learn about feature differences.\n\nWhat's next\n-----------\n\n- Use the [automatic migration tool](/artifact-registry/docs/transition/auto-migrate-gcr-ar) to transition to `gcr.io` Artifact Registry repositories."]]
