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.
Any request sent to a Container Registry host in the gcr.io domain has a 2
hour timeout limit.
There is a fixed quota limit on requests to Container Registry hosts.
This limit is per client IP address.
50,000 HTTP requests every 10 minutes
1,000,000 HTTP requests per day
To avoid exceeding these limits, you can:
Increase the number of IP addresses that connect to Container Registry.
Add retries that introduce a delay. For example, you can use
exponential backoff.
If you require more flexibility, consider using
Artifact Registry
to manage your containers instead of Container Registry. Requests limits are
at the project level, and by default there is no per-user request limit. You can
also request a quota increase for Artifact Registry. For more information, see the
Quotas and limits documentation for Artifact Registry.
Cloud Storage quotas and limits
Container Registry uses Cloud Storage for each registry's
underlying storage. Cloud Storage Quotas & Limits apply to
each registry.
Cloud KMS quotas and Container Registry
When you use CMEK in Container Registry,
your projects can consume Cloud KMS cryptographic requests
quotas.
For example, CMEK-encrypted storage buckets
can consume these quotas for each upload or download.
Encryption and decryption operations using CMEK keys affect Cloud KMS
quotas only if you use hardware (Cloud HSM) or external
(Cloud EKM) keys.
Confirm that you have enough quota to enable
application-layer secrets encryption for your applications and workflows.
For more information, see
Cloud KMS quotas.
[[["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-28 UTC."],[[["\u003cp\u003eContainer Registry has a 2-hour timeout limit for any request sent to a host in the \u003ccode\u003egcr.io\u003c/code\u003e domain.\u003c/p\u003e\n"],["\u003cp\u003eThere is a fixed quota limit of 50,000 HTTP requests every 10 minutes and 1,000,000 HTTP requests per day for Container Registry hosts, per client IP address.\u003c/p\u003e\n"],["\u003cp\u003eContainer Registry utilizes Cloud Storage for storage, and therefore Cloud Storage quotas and limits apply to each registry.\u003c/p\u003e\n"],["\u003cp\u003eUsing Customer-Managed Encryption Keys (CMEK) in Container Registry can consume Cloud KMS cryptographic request quotas, particularly when using hardware (Cloud HSM) or external (Cloud EKM) keys.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nThis page describes quotas and limits for Container Registry.\n\nFor more information about quotas, see the [Cloud Quotas documentation](/docs/quotas/overview).\n\nRequest limits\n--------------\n\nAny request sent to a Container Registry host in the `gcr.io` domain has a 2\nhour timeout limit.\n\nThere is a fixed quota limit on requests to Container Registry hosts.\nThis limit is per client IP address.\n\n- 50,000 HTTP requests every 10 minutes\n- 1,000,000 HTTP requests per day\n\nTo avoid exceeding these limits, you can:\n\n- Increase the number of IP addresses that connect to Container Registry.\n- Add retries that introduce a delay. For example, you can use [exponential backoff](/storage/docs/exponential-backoff).\n\nIf you require more flexibility, consider using\n[Artifact Registry](/artifact-registry/docs/transition/transition-from-gcr)\nto manage your containers instead of Container Registry. Requests limits are\nat the project level, and by default there is no per-user request limit. You can\nalso request a quota increase for Artifact Registry. For more information, see the\n[Quotas and limits](/artifact-registry/quotas) documentation for Artifact Registry.\n\nCloud Storage quotas and limits\n-------------------------------\n\nContainer Registry uses Cloud Storage for each registry's\nunderlying storage. [Cloud Storage Quotas \\& Limits](/storage/quotas) apply to\neach registry.\n\n\u003cbr /\u003e\n\n\nCloud KMS quotas and Container Registry\n---------------------------------------\n\n\u003cbr /\u003e\n\nWhen you use CMEK in Container Registry,\nyour projects can consume Cloud KMS cryptographic requests\nquotas.\nFor example, CMEK-encrypted storage buckets\ncan consume these quotas for each upload or download.\n\nEncryption and decryption operations using CMEK keys affect Cloud KMS\nquotas only if you use hardware (Cloud HSM) or external\n(Cloud EKM) keys.\n\n\nConfirm that you have enough quota to enable\napplication-layer secrets encryption for your applications and workflows.\nFor more information, see\n[Cloud KMS quotas](/kms/quotas).\n\nArtifact Analysis quotas\n------------------------\n\nSee [Artifact Analysis quotas and\nlimits](/container-analysis/quotas) for information on scanning usage policies."]]
