Stay organized with collections
Save and categorize content based on your preferences.
When you are ready to stop using Container Registry, delete the remaining
images by deleting the storage buckets for Container Registry.
When redirection is enabled, commands to delete images in gcr.io paths
delete images in the corresponding Artifact Registry gcr.io repository,
but they don't delete images stored on Container Registry hosts.
To safely remove all Container Registry images, delete the Cloud Storage
buckets for each Container Registry hostname.
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\u003eTo completely stop using Container Registry, you must delete the Cloud Storage buckets associated with it, as commands in \u003ccode\u003egcr.io\u003c/code\u003e paths will not delete the images stored there.\u003c/p\u003e\n"],["\u003cp\u003eDeleting a Container Registry bucket will permanently remove all images within it, and recovery may not be possible depending on the bucket's settings and how long it has been deleted.\u003c/p\u003e\n"],["\u003cp\u003eTo delete Container Registry buckets, you can use the Google Cloud console or the \u003ccode\u003egcloud storage rm\u003c/code\u003e command with the \u003ccode\u003e--recursive\u003c/code\u003e flag, but avoid using the \u003ccode\u003egcloud CLI\u003c/code\u003e to bulk delete a large number of images.\u003c/p\u003e\n"],["\u003cp\u003eBefore deleting the Cloud Storage buckets, it is recommended to transition to Artifact Registry.\u003c/p\u003e\n"],["\u003cp\u003eDisabling the Container Registry API can impact other services in the same Google Cloud project that are dependent on it, even if you aren't using Container Registry with them.\u003c/p\u003e\n"]]],[],null,[]]
