Container Registry:Create a repository and build images

Before you begin

Verify that the following prerequisites are met:

• A Container Registry Personal Edition instance exists in your target region.

• A namespace is created in that instance. For instructions, see Manage namespaces.

• You have a GitHub, Gitee, or GitLab account with a repository that contains a valid Dockerfile.

• You have sufficient permissions to manage the Container Registry Personal Edition instance.

Step 1: Bind a source code repository

1. Log on to the Container Registry console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, click Instances.

4. On the Instances page, click the Personal Edition instance that you want to manage.

5. In the left-side navigation pane of the instance management page, choose Repository > Code Source.

6. On the Code Source page, find the GitHub row and click Bind Account in the Actions column.

7. In the GitHub dialog box, click Go to the source code repository to bind account.

8. On the GitHub sign-in page, enter your username and password, and then click Sign in.

   You are redirected back to the Container Registry console. A confirmation message appears indicating that the account is bound successfully.

Step 2: Configure repository information

A namespace must exist before you create a repository. If you have not created a namespace, see Manage namespaces.

1. Log on to the Container Registry console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, click Instances.

4. On the Instances page, click the Personal Edition instance that you want to manage.

5. In the left-side navigation pane of the instance management page, choose Repository > Repositories.

6. On the Repositories page, click Create Repository.

7. On the Repository Info step, configure the following fields:

   Field	Description
   Namespace	Select the namespace to which the repository belongs.
   Repository Name	Enter a name for the repository. Use lowercase letters, digits, hyphens (-), and underscores (_).
   Repository Type	Select Private (accessible only to authorized users) or Public (accessible to anyone without authentication).
   Summary	(Optional) Enter a brief description of the repository.

   Note

   You cannot build images based on an on-premises repository.

8. Click Next.

Step 3: Configure code source and build settings

1. On the Code Source step, configure the following sections: Code Source, Build Settings, and Build Rules.

   Under Code Source, select the source code repository platform (for example, GitHub), then select the namespace and repository that contain your Dockerfile.

   Under Build Settings, configure the following options:

   Option	Description
   Automatically Build Images When Code Changes	When enabled, the building rule is automatically triggered when code is committed from a branch. A webhook connects your source code repository to ACR to detect these events.
   Build With Servers Deployed Outside Chinese Mainland	When enabled, the image is built on a server outside the Chinese mainland and then pushed to the repository in the specified region. Enable this option if your source code is hosted outside the Chinese mainland. If your source code and container image repository are both in the Chinese mainland, disable Build With Servers Deployed Outside Chinese Mainland and use a build environment in the Chinese mainland.
   Build Without Cache	When enabled, each build starts from scratch by pulling the base image anew, without using cached layers. This may extend the build duration. Disable Build without Cache to accelerate building.

2. Click Create Repository.

Step 4: Configure build rules

Build rules define which branch or tag triggers a build and where the Dockerfile is located.

1. Log on to the Container Registry console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, click Instances.

4. On the Instances page, click the Personal Edition instance that you want to manage.

5. In the left-side navigation pane of the instance management page, choose Repository > Repositories.

6. On the Repositories page, find the repository that you want to manage and click Manage in the Actions column.

7. In the left-side navigation pane of the repository management page, click Build.

8. In the Build Rules section, click Add Build Rule.

   Note

   To modify an existing build rule, find the rule and click Modify in the Actions column.

9. In the Add Build Rule dialog box, configure the following parameters and click Confirm.

   Parameter	Description
   Type	The trigger source type. Select Branch to trigger builds on commits to a branch, or Tag to trigger builds when a matching tag is pushed.
   Code Branch/Tag	The specific branch name or tag pattern that triggers the build rule.
   Build Context Directory	The subdirectory within the branch or tag that serves as the build context. For example, if the Dockerfile is located directly in the root of the branch, leave this field empty or enter /. If the Dockerfile is in a subdirectory named app, enter app/.
   Dockerfile Filename	The filename of the Dockerfile. The default value is Dockerfile. Change this value only if your Dockerfile uses a non-standard filename.
   Tags	The image tag to apply to the built image. Example: latest. You can use variables such as the branch name or commit SHA for dynamic tagging.

Step 5: Build an image

You can trigger a build manually at any time, regardless of whether the Automatically Build Images When Code Changes toggle is enabled.

1. Log on to the Container Registry console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, click Instances.

4. On the Instances page, click the Personal Edition instance that you want to manage.

5. In the left-side navigation pane of the instance management page, choose Repository > Repositories.

6. On the Repositories page, find the repository that you want to manage and click Manage in the Actions column.

7. In the left-side navigation pane of the repository management page, click Build.

8. In the Build Rules section, find the build rule that you want to use and click Build in the Actions column.

   After the build completes, a build record appears in the list.

   Note

   To view the build log, find the build record and click Log in the Actions column. If a build fails, check the log for errors such as a missing Dockerfile, an inaccessible base image, or a build timeout (Personal Edition timeout is 30 minutes).

9. After the build completes, click Tags in the left-side navigation pane to verify that the image tag was created successfully.

What to do next

After a successful build, you can manage the repository and use the image:

View and use the image

• View image tags: Click Tags in the left-side navigation pane to see all built image tags and their digest values.

• Push and pull images: Push images to and pull images from an image repository of a Container Registry Personal Edition instance.

• Deploy to a cluster: Use the built image to deploy applications on Container Service for Kubernetes (ACK):

  • Create a Deployment

  • Create a StatefulSet

  • Create a Job

Manage the repository

• View build history: In the repository management page, click Build to see all past build records and their status.

• View build logs: Find a build record and click Log in the Actions column to diagnose build issues.

• Modify build rules: In the Build Rules section, find a rule and click Modify in the Actions column to update trigger conditions or Dockerfile settings.

Upgrade for advanced features

• Upgrade to Enterprise Edition: For advanced features such as flexible build configurations, custom parameters, multi-architecture builds, and enhanced security controls, see Use a Container Registry Enterprise Edition instance to build an image.