Container Registry
Container Registry
Container Registry
Document
Container Registry (CR)
What's new
Overview
Billing
Billing item
Getting started
User guide
User authorization
Authorization management
Robot account management
Instance management
Namespace management
OCI artifact repository management
OCI artifact management
Version management
Tag immutability rule management
Tag retention rules management
Access configuration
Access control
Distribution acceleration
P2P acceleration
Image lazy loading
Registry replication
Audit log management
Alerts and notifications
Best practices
Image push and pull
Image migration and synchronization
DevOps delivery
FAQ
Authorization
VPC
Image push and pull
Limits
Registry replication
P2P acceleration
Access control
API
Calling Method
Instance Management
Namespace Management
OCI Artifact Repository Management
OCI Artifact Version Management
Domain Management
Access Endpoint Management
Temporary Access Key
Robot Account Management
General Data Structure
Artifact repository AR
What's new
Product overview
Getting started
User guide
Instance management
Repository Management
Access control
Permanent access credentials
Temporary access credentials
Maven package management
Generic package management
PyPI package management
NPM package management
Uploading packages
Downloading packages
AI package management
Permission management
API Reference
Repository Management
Package management
Version Management
File Management
Temporary Key Management
General Data Structure
- Documentation
Container RegistryContainer Registry (CR)FAQImage push and pullWhat do I do if the number of image tags exceeds the limit?
Copy page
Download PDFImage push and pull
What do I do if the number of image tags exceeds the limit?
Copy pageDownload PDFWhat do I do if the number of image tags exceeds the limit?
Issue description
When the number of existing image tags in an OCI artifact repository exceeds the limit, images with new tags cannot be pushed.
tip
The maximum number of image tags supported by each OCI artifact repository varies by instance edition. For more information, see Limits.
Description
Each OCI artifact repository in CR can store only a limited number of image tags. After this limit is exceeded, images with new tags cannot be pushed. Too many image tags increase both image maintenance efforts and storage costs.
Solution
We recommend that you use tag retention rules to clean up image tags automatically. This helps maintain sufficient image tag quota and prevent image push failures. For detailed instructions, see the following topics:
Last updated: 2026.10.19 15:46:49
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
