You need to enable JavaScript to run this app.
Container Registry

Container Registry

Copy page
Download PDF
Getting started
Push and pull artifacts
Copy page
Download PDF
Push and pull artifacts
This article describes how to create a Container Registry instance and push and pull container artifacts (images or Helm Chart) using Docker, Nerdctl, or Helm client.​
Background​
The Container Registry supports the following three client tools for pushing and pulling artifacts:​
​
Client​
Purpose​
Docker​
Push and pull container images.​
Nerdctl​
Push and pull container images (containerd native tool).​
Helm​
Push and pull Helm Chart.​
​
Prerequisites​
Account and permissions​
  • Enterprise account real name authentication has been completed. For detailed instructions, see Real name authentication.​
  • The Container Registry Product has been activated. If not activated yet, please log in to the Container Registry Console and follow the system prompts to activate the product.​
  • (Optional) If IAM users need to operate the Container Registry, ensure that Container Registry-related policy and role authorization have been completed. For specific operating instructions, see Authorization management.​
Client environment​
The corresponding client tool has been installed on the business server, and the corresponding image or Chart file is prepared.​
​
Client​
Installation method​
Version requirements​
Docker​
1.19 and above​
Nerdctl​
—​
Helm​
Install Helm 3, and execute export HELM_EXPERIMENTAL_OCI=1 to enable OCI support.​
3.0 and above (not supported: 3.13.0 and 3.13.1)​
​
Networking​
The IAM Public network access switch has been turned on. For detailed instructions, see IAM.​
Step 1: Create a Standard Edition Instance​
  1. Log in to the CR console.​
  1. Select the target region in the top navigation bar.​
  1. After clicking List of instances in the left navigation bar, click Create instance in the List of instances area on the right page.​
  1. On the Create Registry Instance page, fill in the Purchase Information.​
tip​
This step only describes the parameters related to this scenario. For more parameter descriptions, see Create instance.​
  • ​
    Parameter​
    Description​
    Name​
    The name of the Standard Edition instance. Ensure that the instance name is unique within the same region.​
    tip​
    After the Standard Edition instance is created successfully, the instance name cannot be modified.​
    Billing type​
    This example selects Pay-as-you-go.​
    ​
  1. In Specification, click Standard Edition.​
  1. View the instance specification comparison and configuration costs. After confirming that everything is correct, click Confirm Order.​
  1. On the Confirm order page, confirm the order information again, carefully read and check I have read and agree to the "Container Registry Service Terms".​
  1. Click Confirm to submit the order and start creating the Standard Edition instance.​
tip​
You can view the instance creation progress on the Instances page. When Instance status is Running, it indicates that the instance has been created successfully.​
Step 2: Initialize instance​
  1. In the left navigation bar, click Instance list. On the right-side Instance list page, find the target Standard Edition instance, and click Enter instance.​
  1. On the Initialize instance page, configure the instance initialization information.​
tip​
This step only introduces the parameters relevant to this scenario. For more parameter descriptions, please see Initialize instance.​
  1. Configure network information.​
  • ​
    Parameter​
    Description​
    Public NAT for internet endpoint​
    tip​
    Enabling public network access may take 5 to 10 minutes. You can later check the status on the Access control page.​
    Once public access is enabled, clients on the public internet can directly push images to and pull images from the Standard Edition instance.​
    ​
  1. Click Next to set the instance access password.​
  • ​
    Parameter​
    Description​
    Set CR password​
    You can configure a fixed CR password.​
    ​
  1. Click Next to select or create the namespace to which the instance belongs. You can then generate and copy the commands for image login, push, and pull.​
  1. Click Complete to finish instance initialization.​
Step 3: Push and pull artifacts​
In the related code for artifact management actions, the placeholders and corresponding examples are described as follows:​
​
Parameter​
Placeholder​
Sample value​
IAM user​
User name​
v**​
IAM user ID​
User ID​
1007***​
Instance​
Instance​
test1​
Region​
Region Code​
cn-beijing​
Namespace​
Namespace​
space​
OCI artifact repository​
Repository​
  • CR: mysql​
  • Chart repository: redis​
Artifact repository tag​
  • Image tag: Image tag​
  • Chart version: Chart version​
  • image tag: latest​
  • Chart version: 25.3.10​
​
​
Push/Pull images (Docker)
Push/Pull images (Nerdctl)
Push/Pull Helm Chart (Helm versions before 3.7)
Push/Pull Helm Chart (Helm version 3.7 and later)
​
Pushing Images​
  1. Use the command-line tool to execute the following command, and enter the configured password to log in to the CR instance.​
  • ​
    docker login --username=[User name]@[User ID] [Instance]-[Region].cr.volces.com​
    ​
  • Example:​
  • ​
    docker login --username=v**@1007*** test1-cn-beijing.cr.volces.com​
    ​
  1. Execute the following command to tag the local image.​
  • ​
    docker tag [ImageId or Repository] [Instance]-[Region].cr.volces.com/[Namespace]/[Repository]:[Image tag]​
    ​
  • Example:​
  • ​
    docker tag mysql:latest test1-cn-beijing.cr.volces.com/space/mysql:latest​
    ​
  1. Execute the following command to push the image to the CR instance.​
  • ​
    docker push [Instance]-[Region].cr.volces.com/[Namespace]/[Repository]:[Image tag]​
    ​
  • Example:​
  • ​
    docker push test1-cn-beijing.cr.volces.com/space/mysql:latest​
    ​
  • If the system displays information similar to the following, it indicates that you have successfully pushed the image.​
  • ​alt​​
Pulling Images​
tip​
Public images can be pulled anonymously, which means you can directly pull public images without logging in to the Container Registry Instance.​
  1. Use the command-line tool to execute the following command, and enter the configured password to log in to the CR instance.​
  • ​
    docker login --username=[User name]@[User ID] [Instance]-[Region].cr.volces.com​
    ​
  • Example:​
  • ​
    docker login --username=v**@1007*** test1-cn-beijing.cr.volces.com​
    ​
  1. Execute the following command to pull the image.​
  • ​
    docker pull [Instance]-[Region].cr.volces.com/[Namespace]/[Repository]:[Image tag]​
    ​
  • Example:​
  • ​
    docker pull test1-cn-beijing.cr.volces.com/space/mysql:latest​
    ​
  • The system displays similar information as below, indicating that you have successfully pulled the image from the Container Registry.​
  • ​
    Status: Image is up to date for test1-cn-beijing.cr.volces.com/space/mysql:latest​
    ​
​
​
Last updated: 2026.09.23 14:37:20