Import images from Personal Edition to Enterprise Edition - Container Registry

You can import images from a Personal Edition instance to an Enterprise Edition instance to gain enterprise-grade features such as artifact management, security scanning, and accelerated image pulling.

Usage notes

When you use the image import feature in the public cloud (excluding Alibaba Finance Cloud and Alibaba Gov Cloud), the system automatically creates a service-linked role named AliyunServiceRoleForContainerRegistryConnectCustomerVPC. This role allows Container Registry to use your VPC to import images for high-speed imports.

Note
For more information about the AliyunServiceRoleForContainerRegistryConnectCustomerVPC service-linked role, see Service-linked roles for VPC access.
After you import images from a Personal Edition instance to an Enterprise Edition instance, you must use the Enterprise Edition domain name to access the Enterprise Edition instance. To access the Enterprise Edition instance by using the domain name of a Personal Edition instance, enable the Personal Edition domain name compatibility feature. For more information, see Access an Enterprise Edition instance by using the domain name of a Personal Edition instance.

Import scope

The import process does not affect the normal use of your Enterprise Edition instance or Personal Edition instance.
The import process includes all namespace and repository information, including namespace names, auto-creation properties, default repository types, repository names, and repository types.
You can import the N most recently pushed images from each repository in the Personal Edition instance to the Enterprise Edition instance. You can also filter the images to be imported based on regular expression matching rules.
You can import image build configurations, including the source code information and build rules bound to repositories. The build history is not imported.

Step 1: Bind a VPC

You can skip this step if you have already bound a VPC to your instance in the Container Registry (ACR) console and confirmed that its security group allows both inbound and outbound traffic on TCP port 443. You can also skip this step if you use Alibaba Finance Cloud or Alibaba Gov Cloud.

Create a VPC, a vSwitch, and a security group in the same region as your Enterprise Edition instance. The security group must allow inbound traffic on TCP port 443 from the CIDR block of the VPC. For more information, see Create a VPC, Create a vSwitch, and Create a security group.
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 the Enterprise Edition instance that you want to manage.
In the left-side navigation pane, choose Repository > Access Control.
On the VPC tab, click Add VPC .
In the Add VPC dialog box, select a VPC and a vSwitch, and then click Confirm.

The VPC has been successfully added. You can use the VPC after its status changes from Creating to Running.

Important

The VPC and vSwitch that you bind for the import feature must be in a supported zone. The following table lists the supported zones.

Cloud service	Region	Supported zones
Public cloud	China (Beijing)	cn-beijing-c cn-beijing-d cn-beijing-e cn-beijing-f cn-beijing-i cn-beijing-j cn-beijing-k cn-beijing-g cn-beijing-h
	China (Hangzhou)	cn-hangzhou-e cn-hangzhou-f cn-hangzhou-g cn-hangzhou-h cn-hangzhou-i cn-hangzhou-j cn-hangzhou-k
	China (Shenzhen)	cn-shenzhen-b cn-shenzhen-c cn-shenzhen-d cn-shenzhen-e cn-shenzhen-f
	China (Shanghai)	cn-shanghai-a cn-shanghai-b cn-shanghai-d cn-shanghai-e cn-shanghai-f cn-shanghai-g cn-shanghai-i
	China (Zhangjiakou)	cn-zhangjiakou-a cn-zhangjiakou-b cn-zhangjiakou-c
	China (Hong Kong)	cn-hongkong-b cn-hongkong-c cn-hongkong-d
	Singapore	ap-southeast-1a ap-southeast-1b ap-southeast-1c
	Indonesia (Jakarta)	ap-southeast-5a ap-southeast-5b
	US (Virginia)	us-east-1a us-east-1b
	US (Silicon Valley)	us-west-1a us-west-1b
	UK (London)	eu-west-1a eu-west-1b
	Germany (Frankfurt)	eu-central-1a eu-central-1b
	Japan (Tokyo)	ap-northeast-1a ap-northeast-1b
	China (Chengdu)	cn-chengdu-a cn-chengdu-b
	China (Heyuan)	cn-heyuan-a cn-heyuan-b

Step 2 (Optional): Bind a source code platform

In the Enterprise Edition instance, bind the same source code hosting platform used by the Personal Edition instance. For more information, see Bind a source code hosting platform. Skip this step if you do not need to import image build configurations.

Step 3: Create an import rule

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 the Enterprise Edition instance that you want to manage.
In the left-side navigation pane, choose Instances > Image Import.

On the Image Import page, configure the import rule parameters and click Confirm.

Parameter	Description
VPC	A VPC is used to accelerate the import from a Personal Edition instance. This field shows whether a VPC is bound, with the status being either Bound or Unbound.
Source	The source of the images to import. You can import images from a Personal Edition instance or an OSS bucket to an Enterprise Edition instance. In this topic, select Personal Edition.
Region	Select the region of the Personal Edition instance.
Namespace	The name of the namespace in the Personal Edition instance from which to import images.
Image selection	Controls which images to import. Specify the number of most recently pushed images to import from each repository. The value can range from 0 to 1,000. A value of 0 means no images are imported. Specify a regular expression to filter the most recent N images by tag. By default, all images are selected. For example, `release-v.*` imports only images whose tags are prefixed with `release-v`.
Overwrite image	Specifies whether to overwrite an image in the Enterprise Edition instance if an imported image has the same tag but a different digest. This option is selected by default.

In the Import Rules section, click Trigger Task to start the import.
In the Tips dialog box, click Confirm.

A status of Success in the Results column for the import task indicates that the image was successfully imported from a Personal Edition instance to an Enterprise Edition instance.

Note
If the Results column for an import task displays The verification failed., the task has failed. Hover over The verification failed. to view the reason for the failure.

Related operations

View import details

On the Image Import page, find the import task and click Details in the Actions column. The details page shows the total data size (in GB), current transfer speed (in MBps), total number of images, the total number of imported images per repository, the number of successful and failed imports, and failure reasons.
Update an import rule

On the Image Import page, in the Import Rules section, click Update Rule. In the Update Import Rule dialog box, modify the rule and click Confirm. Then, click Import Again and click Confirm in the Tips dialog box to import images using the new rule.

Container Registry:Import images from Personal Edition to Enterprise Edition