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.
This page describes the steps to disable Container Registry.
Disabling the service
Disabling the Container Registry API does not delete container images
stored in Cloud Storage buckets for registry hosts. You will continue to incur
Cloud Storage storage and network egress charges
for stored images.
If you are no longer using Container Registry and do not need the retain
the images, delete the storage buckets.
Disable the API
To disable the API from the Google Cloud console:
console
Go to the API Overview
page for Container Registry.
Select the project where the API is enabled.
Click Manage.
Click Disable API.
gcloud
Run the following command to disable the API for your current project:
To confirm deletion, enter the bucket name and then click Delete.
gcloud
If you want to bulk delete a hundred thousand or more images in a bucket,
avoid using the gcloud CLI since the deletion process takes a long
time to complete. Use the Google Cloud console to perform the operation
instead. For more information, see
deleting Cloud Storage objects in bulk.
To delete a bucket, use the gcloud storage rm
command with the --recursive flag.
gcloudstoragermgs://BUCKET-NAME--recursive
Replace BUCKET-NAME with the Container Registry storage
bucket name. In the bucket names, PROJECT-ID is your
Google Cloud
project ID.
If other Google Cloud services are running in the same Google Cloud
project, leave the Container Registry API enabled. If you try to
disable the Container Registry API.
Container Registry displays a warning if other services with a configured
dependency are enabled in the project. Disabling the Container Registry API
automatically disables any services in the same project with a configured
dependency, even if you are not currently using Container Registry with those
services.
[[["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\u003eDisabling the Container Registry API does not delete container images, and you will continue to incur storage and network charges for stored images.\u003c/p\u003e\n"],["\u003cp\u003eTo disable the API, you can use either the Google Cloud console by navigating to the API Overview page and clicking "Disable API", or use the \u003ccode\u003egcloud services disable containerregistry.googleapis.com\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIf you no longer need stored images, you should delete the associated Cloud Storage buckets, understanding that doing so permanently deletes all images within them.\u003c/p\u003e\n"],["\u003cp\u003eDeleting storage buckets can be done through the Google Cloud console or via the \u003ccode\u003egcloud storage rm gs://<var>BUCKET-NAME</var> --recursive\u003c/code\u003e command, replacing \u003ccode\u003e<var>BUCKET-NAME</var>\u003c/code\u003e with the corresponding bucket name.\u003c/p\u003e\n"],["\u003cp\u003eIf other services are running on the same project, disabling the Container Registry API will result in other services with configured dependencies being disabled as well, even if you are not currently using Container Registry with those services.\u003c/p\u003e\n"]]],[],null,["# Disable the service\n\nThis page describes the steps to disable Container Registry.\n\nDisabling the service\n---------------------\n\nDisabling the Container Registry API does not delete container images\nstored in Cloud Storage buckets for registry hosts. You will continue to incur\nCloud Storage [storage and network egress charges](/container-registry/pricing)\nfor stored images.\n\nIf you are no longer using Container Registry and do not need the retain\nthe images, [delete the storage buckets](#delete-bucket).\n\n### Disable the API\n\nTo disable the API from the Google Cloud console: \n\n### console\n\n1. Go to the [API Overview](https://console.cloud.google.com/apis/library/containerregistry.googleapis.com) page for Container Registry.\n2. Select the project where the API is enabled.\n3. Click **Manage**.\n4. Click **Disable API**.\n\n### gcloud\n\nRun the following command to disable the API for your current project: \n\n gcloud services disable containerregistry.googleapis.com\n\n### Delete storage buckets\n\nDelete the storage buckets for Container Registry if you are no longer using\nContainer Registry\n| **Warning:** Deleting a bucket deletes all images in the bucket. You might not be able to recover images from a deleted bucket, depending on the [bucket's settings](/storage/docs/soft-delete) and the length of time since the bucket was deleted.\n\nTo delete each Container Registry storage bucket: \n\n### Console\n\n1. [Go to the Cloud Storage page in the Google Cloud console](https://console.cloud.google.com/storage).\n2. Select the storage bucket to delete. In the bucket names,\n \u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e is your Google Cloud\n [project ID](/resource-manager/docs/creating-managing-projects#identifying_projects).\n\n - gcr.io: `artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n - asia.gcr.io: `asia.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n - eu.gcr.io: `eu.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n - us.gcr.io: `us.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n3. Click **Delete**. A confirmation dialog box appears.\n\n4. To confirm deletion, enter the bucket name and then click **Delete**.\n\n### gcloud\n\nIf you want to bulk delete a hundred thousand or more images in a bucket,\navoid using the gcloud CLI since the deletion process takes a long\ntime to complete. Use the Google Cloud console to perform the operation\ninstead. For more information, see\n[deleting Cloud Storage objects in bulk](/storage/docs/deleting-objects#delete-objects-in-bulk).\n\nTo delete a bucket, use the [`gcloud storage rm`](/sdk/gcloud/reference/storage/rm)\ncommand with the `--recursive` flag. \n\n gcloud storage rm gs://\u003cvar translate=\"no\"\u003eBUCKET-NAME\u003c/var\u003e --recursive\n\nReplace \u003cvar translate=\"no\"\u003eBUCKET-NAME\u003c/var\u003e with the Container Registry storage\nbucket name. In the bucket names, \u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e is your\nGoogle Cloud\n[project ID](/resource-manager/docs/creating-managing-projects#identifying_projects).\n\n- gcr.io: `artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n- asia.gcr.io: `asia.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n- eu.gcr.io: `eu.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n- us.gcr.io: `us.artifacts.`\u003cvar translate=\"no\"\u003ePROJECT-ID\u003c/var\u003e`.appspot.com`\n\nThe response looks like the following example: \n\n Removing gs://artifacts.my-project.appspot.com/...\n\nIf other Google Cloud services are running in the same Google Cloud\nproject, leave the Container Registry API enabled. If you try to\n[disable the Container Registry API](/container-registry/docs/enable-service#disable).\nContainer Registry displays a warning if other services with a configured\ndependency are enabled in the project. Disabling the Container Registry API\nautomatically disables any services in the same project with a configured\ndependency, even if you are not currently using Container Registry with those\nservices.\n\nWhat's next\n-----------\n\n- Configure [access permissions](/container-registry/docs/access-control)"]]
