[[["易于理解","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\u003eContainer Registry is being deprecated and will be shut down after March 18, 2025, with Artifact Registry becoming the primary service for image storage.\u003c/p\u003e\n"],["\u003cp\u003eAfter May 15, 2024, projects without prior Container Registry usage will have their \u003ccode\u003egcr.io\u003c/code\u003e images hosted in Artifact Registry, in preparation for the complete shutdown.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry offers enhanced features over Container Registry, including repository-level access control, multi-region hosting, virtual and remote repositories, and support for multiple artifact formats.\u003c/p\u003e\n"],["\u003cp\u003eYou can seamlessly transition from Container Registry to Artifact Registry using the automatic migration tool without any downtime or service disruption, by migrating \u003ccode\u003egcr.io\u003c/code\u003e endpoints to \u003ccode\u003egcr.io\u003c/code\u003e repositories.\u003c/p\u003e\n"],["\u003cp\u003eArtifact Registry provides \u003ccode\u003epkg.dev\u003c/code\u003e repositories, offering additional flexibility such as storing data in specific regions, supporting multi-project setups, and allowing greater customization for storing and managing images.\u003c/p\u003e\n"]]],[],null,["# Transition from 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 container image storage and\nmanagement on Google Cloud. Artifact Registry provides the same\ncontainer management features as Container Registry and includes additional\nfeatures and benefits. As a fully-managed service with support for both\ncontainer images and non-container artifacts, Artifact Registry extends\nthe capabilities of Container Registry.\n\nYou can migrate Container Registry endpoints to Artifact Registry\n`gcr.io` repositories without requiring any downtime or service disruption\nusing the [automatic migration tool](/artifact-registry/docs/transition/auto-migrate-gcr-ar).\n\n### Summary of new features\n\nArtifact Registry extends the capabilities of Container Registry with the following\nfeatures:\n\n- Repository-level [access control](/artifact-registry/docs/access-control).\n- Hosting artifacts in [regions](/artifact-registry/docs/repositories/repo-locations) to reduce latency and data transfer costs, and to comply with data residency requirements.\n- Streaming images to [Google Kubernetes Engine](/kubernetes-engine/docs/how-to/image-streaming) and [Dataproc Serverless](/dataproc-serverless/docs/guides/custom-containers#image_streaming) to reduce workload startup times.\n- [Deploying to Cloud Run from source](/run/docs/deploying-source-code).\n- [Audit logging](/artifact-registry/docs/audit-logging) for repository activity.\n- Enforcement of organization policy, including encryption with [customer-managed encryption keys](/artifact-registry/docs/cmek#org-policy) (CMEK) and [location constraints](/artifact-registry/docs/repositories/repo-locations#location-constraints).\n- [Scanning for OS and language package vulnerabilities](/artifact-analysis/docs/container-scanning-overview) in containers.\n- [Virtual repositories](/artifact-registry/docs/repositories/virtual-repo) that aggregate multiple repositories behind a single host.\n- [Remote repositories](/artifact-registry/docs/repositories/remote-repo) that cache artifacts from upstream sources such as Docker Hub or Maven Central.\n\nSee the [feature comparison](#feature-comparison) for more details about these\nfeatures.\n\nExisting Container Registry images maintained by Google\n-------------------------------------------------------\n\nMost Google-owned images previously hosted on Container Registry are now hosted\non Artifact Registry in `gcr.io` repositories. You don't need to change\nthe URLs to pull these images. For example, you can still use the\n[Cloud Build official builder images](https://github.com/GoogleCloudPlatform/cloud-builders).\n\nCached Docker Hub images on `mirror.gcr.io`\n-------------------------------------------\n\nArtifact Registry caches frequently-accessed public Docker Hub images on\n`mirror.gcr.io`. For more information on using `mirror.gcr.io`, see\n[Pull cached Docker Hub images](/artifact-registry/docs/pull-cached-dockerhub-images).\n\nChoose a transition option\n--------------------------\n\nThere are two types of repositories you can use to transition to Artifact Registry:\n\ngcr.io repositories in Artifact Registry\n\n: Repositories that are mapped to Container Registry `gcr.io` hostnames.\n Artifact Registry redirects `gcr.io` requests for your Container Registry hosts to\n corresponding Artifact Registry repositories in the same Google Cloud project.\n\n Use `gcr.io` repositories if:\n\n - You want to minimize the amount of setup and configuration required to transition your existing images and automation to Artifact Registry.\n - You don't need to set up Artifact Registry repositories in a different Google Cloud project or region.\n\n`pkg.dev` repositories in Artifact Registry\n\n: `pkg.dev` Artifact Registry repositories that support all features and\n are fully independent of any existing Container Registry hosts.\n\n Use `pkg.dev` repositories if:\n\n - You have compliance requirements to store data in a specific region. Repositories with `gcr.io` domain support are only available in the same multi-regions as Container Registry hosts: `asia`, `eu`, and `us`.\n - You want to set up your Artifact Registry repositories in a project that is different from the project where you are using Container Registry.\n - You want to redesign how and where you store images. For example:\n\n - Create repositories in the same regions as your other Google Cloud regional resources, including runtimes such as Cloud Run and Google Kubernetes Engine.\n - Set up repositories in regions that are closer to your teams. For example, you can create repositories in Australian regions instead of the `asia` multi-region, or in South American regions instead of the `us` multi-region.\n - Create multiple Docker repositories in the same project and location with different Identity and Access Management policies. For example, you can set up a development repository and production repository in the `us-east1` region with different levels of access for developers.\n - You want to create virtual repositories that act as a single endpoint for\n downloads from multiple upstream `pkg.dev` standard mode repositories.\n\n - You want to use remote repositories to act as proxies for external sources.\n\nStandard, remote, virtual `pkg.dev` and `gcr.io` repositories can co-exist. For\nexample, you can create `gcr.io` repositories in Artifact Registry to\ntransition your existing Container Registry setup and create `pkg.dev`\nrepositories for new work.\n\nUse our transition tooling\n--------------------------\n\nUse the following tools to identify projects that 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 automatic [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- [Copy images](/artifact-registry/docs/docker/copy-from-gcr) from Container Registry to Artifact Registry using the automatic migration tool, gcrane, Docker, or the gcloud CLI.\n\nFeature comparison\n------------------\n\nThe following table summarizes differences between Container Registry and\nArtifact Registry.\n\ngcloud command comparison\n-------------------------\n\nThe following table summarizes Container Registry commands and the equivalent\nArtifact Registry commands in the gcloud CLI. Click a link\nin the table to view reference page for the command.\n\nThe table does not include all available Artifact Registry commands that\nhave no equivalent in Container Registry. See the\n[`gcloud artifacts`](/sdk/gcloud/reference/artifacts)\ndocumentation for the full Artifact Registry command reference."]]
