Cloud Container Registry
A secure hosting and efficient distribution platform for cloud-native artifacts like Container Image and Helm Chart
Why Choose CCR?
The Cloud Container Registry (CCR) is a secure hosting and efficient distribution platform for cloud-native artifacts like Container Image, Helm Charts, and other OCI-compliant artifacts. CCR supports creating exclusive managed services in multiple regions with various security safeguards. It enables synchronization of cloud-native artifacts like Container Image and seamlessly integrates with services such as Cloud Container Engine (CCE), helping enterprises enhance the delivery efficiency for cloud-native container applications
Network Access Control
Provides the allow list access configuration for private and public network to ensure data access security.
Multi-Region Distribution
Supports data synchronization between global multi-region instances, achieving single-point push and multi-region automatic synchronization and distribution.
Nearby Upload & Download
Automatically select the data center with the lowest latency for uploads and downloads to achieve faster speeds and reduced request delays.
Product Advantages
Simple and Easy to Use
Quickly creates an image registry without the need for self-building and O&M, providing stable and fast image push and pull services across various regions.
Secure & Controllable
User data is encrypted and stored in their own BOS Bucket. It also supports Image Scan, internal/external network access control, and fine-grained permissions to ensure business security.
Diverse Artifact Management
Supports the management of multi-architecture (Linux, Windows, ARM, etc.) Container Image, Helm Chart V2/V3, and other OCI-compliant cloud-native artifacts to enrich usage scenarios.
Seamless Integration with Cloud Products
Integrates with products like Cloud Container Engine (CCE), accelerating cloud-native artifact delivery efficiency.
Frequently Asked Questions
01
Why can't a Personal Edition account log in to a mirror repository created by an Enterprise Edition instance?
02
Why can't images be pushed to an Enterprise Edition instance's mirror repository using a Classic Network?
03
When multiple retention policies exist in a mirror repository, what mechanism determines which policy takes effect?
04
Is there a fee for personal use of the Container Image Service?
05
Does the Enterprise Edition of the Container Image Service support uploading multi-CPU architecture images?