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)User guideInstance managementInstance types
Copy page
Download PDFInstance management
Instance types
Copy pageDownload PDFInstance types
CR provides two main instance types: Standard instances (used for storing and distributing self-owned images) and proxy cache registries (used for proxy-caching external image sources). Each instance type is available in two editions: Standard Edition and Micro Edition, for a total of four instance forms. You can select an appropriate instance type based on your business scale, performance requirements, and usage scenarios.
Instance edition | Positioning | Applicable scenarios |
Instance edition | Positioning | Applicable scenarios |
Standard Edition standard instance | A full-featured image hosting service for enterprise-grade production environments, providing dedicated data storage, dedicated Registry services, and comprehensive security management capabilities. | Medium and large enterprises, multi-team collaboration, large-scale container cluster image distribution, and production environments with high performance and SLA requirements. |
Micro Edition standard instance | A lightweight image hosting service for small and micro enterprises and individual developers. This instance type provides basic image push and pull capabilities. | Individual developers, startup teams, development and testing environments, and cost-sensitive scenarios with a small image scale. |
Standard Edition proxy cache registry | An enterprise-grade external image proxy caching service, providing comprehensive capabilities such as high-bandwidth origin pull, VPC internal network access, and custom domain names. | Scenarios where enterprises frequently pull images from Docker Hub, GHCR, or self-built registries in production environments; Scenarios with high requirements for origin pull bandwidth and cache capacity. |
Micro Edition proxy cache registry | A lightweight external image proxy caching service for small and micro enterprises and individual developers, delivering basic proxy pull capabilities at low cost. | Scenarios where individuals or small teams need to accelerate pulling overseas images, or where access to overseas image sources is limited and usage is low. |
Feature comparison
For specific quota limits of each instance type (such as namespace count, OCI artifact repository count, and concurrent push/pull QPS), see Features.
Instance upgrade path
CR supports upgrading from Micro Edition to Standard Edition to meet your performance expansion needs as business grows.
warning
- Instance upgrade is irreversible. Standard Edition cannot be downgraded to Micro Edition.
- There will be a brief service interruption during the upgrade (usually in minutes). We recommend performing the upgrade during off-peak business hours.
Upgrade path | Data processing | Description |
Upgrade path | Data processing | Description |
Standard instance (Micro Edition) → Standard instance (Standard Edition) | Data is automatically migrated. | After the upgrade, you will gain enterprise-grade capabilities such as dedicated resources, VPC access, and P2P acceleration, and image data will be automatically retained. For details, see Upgrading from Micro Edition instances to Standard Edition instances. |
Proxy cache registry (Micro Edition) → Proxy cache registry (Standard Edition) | Data is automatically migrated. | After the upgrade, you will gain capabilities such as VPC internal network access, custom domain names, dedicated-line pulling, robot account, and log auditing, as well as higher origin pull bandwidth and cache capacity. For details, see Upgrading proxy cache registries from Micro Edition to Standard Edition. |
Last updated: 2026.09.23 14:37:25
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
