Docs

Container Registry

Image push and pull

Pushing images across borders to Volcano Engine CR

This topic describes how to quickly push and pull images in cross-border scenarios.

Scenario introduction

When images are pushed from third-party registries outside the Chinese mainland, such as GitHub, to CR instances in the Chinese mainland, image pulls may be slow. Volcano Engine supports features including service nodes outside the Chinese mainland, such as Johor, and dedicated lines for image synchronization.

Procedure

Step 1: Create instance A in the Asia Pacific (Johor) region

Select the target region in the top navigation bar.

In the left navigation bar, click Instances. Then, in the Instances area on the right page, click Create Registry Instance.

On the Create Registry Instance page, fill in the Purchase Information. For detailed settings and subsequent operations, see Creating Standard Edition instances.

Step 2: (Optional) Create instance B in the target region in the Chinese mainland

tip

If a CR instance already exists in the Chinese mainland, you do not need to create another one.

Refer to Step 1 and create a CR instance in a region in the Chinese mainland, such as China (Beijing).

Step 3: Push GitHub images to instance A

Use the push command on the instance overview page to push GitHub images to instance A in the Asia Pacific (Johor) region. For instructions, see Pushing and pulling artifacts.

Step 4: Synchronize images from instance A to instance B

After the images are pushed, use registry replication and dedicated lines under the same Volcano Engine root user that owns the CR instance. Replicate images from the instance in the Asia Pacific (Johor) region to an instance in the Chinese mainland, such as China (Beijing). This enables fast pulls of images from outside the Chinese mainland. For instructions on cross-region image replication within the same root user, see Synchronizing images within or across regions.

Last updated: 2026.10.19 15:46:51