Container Registry Enterprise Edition (ACR) hosts and distributes OCI-compliant artifacts such as container images, Helm charts, and operators at scale across regions. Create an Enterprise Edition instance to start using ACR.
Prerequisites
-
ACR has been granted permissions to access your OSS, VPC, and Cloud Monitor resources.
-
OSS is activated. ACR requires OSS.
-
If you need to query real-time data for your instance, activate Cloud Monitor.
ImportantOn the free tier of Cloud Monitor, API calls may be throttled after the free quota is exhausted. Monitoring data may not display correctly on the ACR console but remains accessible on the Cloud Monitor console.
-
Cloud Monitor Free quotas.
-
If the free quota of API calls for metric data query is used up, resolve the issue by referring to How do I fix the issue that the quotas of CloudMonitor are insufficient?
-
-
To access the instance over a VPC, activate VPC.
-
If you need to record console operations, activate ActionTrail.
Procedure
Log on to the Container Registry console.
In the top navigation bar, select a region.
In the left-side navigation pane, click Instances.
-
On the Instances page, click Create ACR EE.
-
On the Container Registry purchase page, configure the instance and click Buy Now.
Parameter
Description
Region
Select the region for the instance.
Instance type
Select an instance type. What is Container Registry ACR.
Instance name
Enter an instance name.
Instance storage
Select Default or Custom.
-
Default: An OSS bucket is automatically created to store container images.
The default bucket naming format is
<ACR instance ID>-registry. -
Custom: Select an existing OSS bucket for image storage.
Select bucket
Select an existing OSS bucket for image storage.
NoteAvailable only when Instance Storage is set to Custom.
Security scan
Select a scan engine for container images:
-
Trivy Scan Engine: Open-source engine. Detects system and application vulnerabilities. Does not support one-click fixes for system vulnerabilities.
-
Security Center Scan Engine: Alibaba Cloud proprietary engine. Detects system and application vulnerabilities, malicious samples, and performs baseline checks. Supports one-click fixes for system vulnerabilities.
Repository quota
Default: 1,000 (Basic), 3,000 (Standard), 5,000 (Premium). You can increase this quota.
Namespace quota
Default: 15 (Basic), 25 (Standard), 50 (Premium). You can increase this quota.
Subscription duration
Select 1, 2, 3, or 6 months, or 1 to 5 years.
NoteAuto-renewal is available.
-
-
On the Confirm Order page, verify the Parameters, review the Terms of Service and Service Level Agreement (SLA), and click Payment.
-
On the Pay page, verify the total cost and complete the payment.
On the Instances page, the new instance shows Starting. After 2 to 3 minutes, the status changes to Running.
Expand the repository quota
If you receive a "Repository quota exceeded" error when you create an image repository, the number of repositories in the instance has reached the quota limit. You can resolve this issue in either of the following ways.
Option 1: Increase the repository quota
-
Log on to the Container Registry console.
-
On the Instances page, find the target Enterprise Edition instance and click Manage.
-
On the Overview page, in the instance information area, click Upgrade next to the instance type.
-
On the buy page, in the Repository quota area, adjust the quota. Each additional 1,000 repositories costs an extra CNY 100 per month.
-
Confirm the configuration and click Buy Now to complete the upgrade.
Option 2: Upgrade the instance type
On the same buy page, select a higher instance type. The default repository quota varies by instance type:
-
Basic: 1,000
-
Standard: 3,000