Container Registry quotas and limits
Warning
Starting October 13, 2026, Yandex Container Registry will be unavailable to new users.
The existing users can create resources until November 10, 2026. Afterwards, Yandex Container Registry will go read-only and cease to operate on December 14, 2026. For more information on how it will be handled, see this article on Yandex Container Registry sunset.
Yandex Container Registry has the following limits:
- Quotas are organizational constraints that can be changed by contacting technical support.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
If you need more resources, you can increase your quotas in one of the following ways:
- Make a request to increase your quotas.
- Contact support and specify which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.
You can manage your quotas with Cloud Quota Manager.
Quotas
|
Type of limit |
Value |
|
Maximum number of registries per cloud |
10 |
|
Number of concurrent Docker image scans running in a single cloud |
10 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size of a single layer of a Docker image | 150 GB |
| Maximum number of layers in a Docker image being scanned | 127 |
| Maximum number of Docker images in a single repository that can be checked by a trial run of the Docker image lifecycle policy | 50 000 |
| Maximum size of a Docker image to scan | 4 GB |
| Maximum number of Docker images to scan per request | 10 000 |