Container Registry:Build images on a Container Registry Enterprise Edition instance

Step 1: Bind your instance to a code hosting platform

Step 2: Create a namespace

Create a namespace to organize your image repositories. Enabling automatic repository creation lets you configure default settings applied to all repositories under this namespace.

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 Enterprise Edition instance for which you want to create a namespace.

5. In the left-side navigation pane, choose Repository > Namespace.

6. On the Namespace page, click Create Namespace.

7. In the Create Namespace sidebar, configure Namespace and set Automatically Create Repository to On or Off. Then click Confirm.

   If you set Automatically Create Repository to On, configure the following parameters:

   Parameter	Description
   Repository Type	Select Public or Private. Public: By default, public images require users to log on to the instance before they can be pulled. To allow anonymous pulls, enable the instance's public anonymous pull setting. Because public repositories can be pulled by unauthorized users, set repositories to Private to protect your data.Private: Users must log on to the instance and have Pull permission authorization before they can pull private images.
   Immutable Image Tags	Select Flexible or Immutable. When set to Immutable, all image tags except latest cannot be overwritten.
   Accelerated Images	When enabled, an accelerated version of each image is automatically generated after the image is pushed. The accelerated image has an _accelerated suffix appended to its tag.

Step 3: Create an image repository

Create an image repository and bind it to a source code repository. All images built from that source code repository are pushed to this image 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 Enterprise Edition instance you want to manage.

5. In the left-side navigation pane, choose Repository > Repositories.

6. On the Repositories page, click Create Repository.

7. In the Repository Info step, configure Namespace, Repository Name, Repository Type, Tags, Accelerated Image, Summary, and Description. Then click Next.

8. In the Code Source step, configure Code Source, Build Settings, and Build Rules, and then click Create Repository.

9. The following table describes the Build Settings parameters:

   Parameter	Description
   Automatically Build Images When Code Changes	When enabled, the build rule is automatically triggered when code is committed to a branch.
   Build With Servers Deployed Outside Chinese Mainland	Enable this if your code source is on GitHub or Bitbucket, or if your Dockerfile downloads dependencies from outside China and the cross-border network connection is unstable. ACR uses an accelerated link to pull external data sources during the build. This option is available only in specific regions. If the option is not displayed when you create an image repository, the current region does not support this feature.
   Build Without Cache	When enabled, ACR pulls the base image from the source each time, ignoring cached layers. This may slow down builds. Disable this option to use cached layers and accelerate builds.

   On the Repositories page, click the created image repository. If Build is displayed in the left-side navigation pane of the repository management page, the image repository is bound to the source code repository.

Step 4: Build an image

Configure build rules to define how and when ACR builds images from your repository, then trigger a build and verify the result.

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 Enterprise Edition instance you want to manage.

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

6. On the Repositories page, find the image repository you created and click Manage in the Actions column.

7. In the left-side navigation pane, click Build. In the Build Rules section, click Add Build Rule. In the Build Information step, configure the following parameters and then click Next.

   Parameter	Description
   Type	The type of the source code repository. Valid values: Branch and Tag.
   Branch/Tag	Select or enter a branch or tag. Regular expressions are supported. For example, if you enter release-(?<imageTag>\w*) , ACR automatically builds an image when source code in the release-v1 branch is updated. For more information on named capturing groups, see Use regular expressions in named capturing groups . Note When you use a regular expression, only ACR can trigger builds. Manual builds are not supported.
   Build Context Directory	The directory containing the Dockerfile, relative to the branch or tag root. For example, if the branch is master and the Dockerfile sits at the branch root, set this to /.
   Dockerfile Filename	The name of the Dockerfile. The default name is Dockerfile.

8. In the Tag step, configure the following parameters, click Save, and then click Next.

   Note

   Click Add Configuration to add image tags. You can add up to three image tags.

   Parameter	Description
   Image Tag	The tag for the built image, for example latest. Named capturing groups are supported. If you defined a named capturing group in Branch/Tag, reference the captured value here.
   Build Time	(Optional) The time (UTC+8) at which source code is pushed. Accepted formats: 20201015 or 202010151613 . Note If you set this parameter, only ACR can trigger builds. Manual builds are not supported.
   Commit ID	(Optional) The number of characters to use from the commit ID of the most recently pushed code. By default, the first six characters are used. Adjust the slider to change the number. Note If you set this parameter, only ACR can trigger builds. Manual builds are not supported.

9. In the Build Configurations step, configure the following parameters and then click Next.

   Parameter	Description
   Build Architecture	Select one or more target architectures. If you select multiple architectures, ACR generates a separate image for each architecture under the same tag.
   Build Parameters	Key-value pairs passed to the build process. Parameter names are case-sensitive. Configure up to 20 build parameters by clicking Add Configuration.

10. Trigger a build using one of the following methods:

    • In the Build Rules section of the Build page, find the build rule and click Build in the Actions column.

    • Push a code commit to the configured branch of the source code repository to trigger the build rule automatically.

11. Monitor the build: In the Build Log section, find the image build task and click Log in the Actions column to view the build log. To stop a running build, click Cancel in the Actions column.

12. Verify the result: In the left-side navigation pane, click Image Tag. If the image you built is listed, the build succeeded.

    In the left-side navigation pane, click Image Tag. If the image that you created is displayed, the image is built.

Examples

The following two examples illustrate common build rule configurations. Example 1 is a simple setup that supports both manual and automatic builds. Example 2 uses a regular expression to create versioned image tags from release branch names, and supports automatic builds only.

What to do next