Container Registry:Use a Dockerfile to build an image for a Java application

Step 1: Bind a source code repository to the Container Registry instance

Log on to the Container Registry console and authorize Container Registry to access the source code repository. In this example, Container Registry is authorized to access source code repositories on GitHub.

1. Log on to the Container Registry console.

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

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

4. In the left-side navigation pane of the management page of the Container Registry Personal Edition instance, choose Repository > Code Source.

5. In the Actions column corresponding to GitHub, click Bind Account. In the GitHub dialog box, click Go to the source code repository to bind account. On the page that appears, enter your username and password to log on to GitHub.

6. On the authorization page, click Authorize AliyunDeveloper. If the account is bound, a message appears to indicate that your account is bound to GitHub. Go to the Code Source page. Check whether the status of the GitHub service appears as Bound.

Step 2: Create an image repository

1. Log on to the Container Registry console.

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

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

4. In the left-side navigation pane of the management page of the Container Registry Personal Edition instance, choose Repository > Repositories. On the Repositories page, click Create Repository.

5. Configure parameters of the image repository.

   Parameter	Description	Example
   Region	The region in which the image repository resides.	China (Hangzhou)
   Namespace	The namespace to which the image repository belongs. An image repository belongs to only one namespace, but a namespace can contain multiple image repositories.	test23432
   Repository Name	The name of the image repository.	test
   Repository Type	The type of the image repository. Valid values: Public and Private. You can push images to an image repository only after you log on to the image repository, regardless of the repository type. Public repositories are available for public use. To prevent data loss, we recommend that you select Private. Public: You can pull images from the image repository without the need to log on to the image repository. Private: You can pull images from the image repository only after you log on to the image repository on the Docker client.	Private
   Summary	The brief description of the image repository.	-
   Description	The detailed description of the image repository. Markdown format is supported.	Use the created Dockerfile and the image building feature of Container Registry to build, package, and run the image.

6. Click Next. In the Code Source step, specify the code source and configure building settings.

   Parameter	Description
   Code Source	On the GitHub tab of the Code Source section, click Bind Account and then bind the source code repository that you bound in "Step 2: Authorize Container Registry to access the source code repository".
   Build Settings	In this example, select Automatically Build Images When Code Changes and Build With Servers Deployed Outside Chinese Mainland. Automatically Build Images When Code Changes: The building rule is automatically triggered when code is committed from a branch. Build With Servers Deployed Outside Chinese Mainland: Images are built in a data center outside the Chinese mainland and then pushed to an image repository in the specified region. Build Without Cache: The system pulls the base image each time an image is to be built. This may slow down the building process.

7. Click Create Repository.

   After the image repository is created, you are redirected to the details page of the image repository. You can view the basic information of the image repository on the details page.

8. In the left-side navigation pane of the details page of the image repository, click the icon next to the repository name. On the Repositories page, you can view the image repository that you created. If Normal is displayed in the Status column of the image repository, the image repository is created.

Step 3: Build an image

1. In the left-side navigation pane, choose Repository > Repositories. On the Repositories page, find the image repository. Click the repository name or click Manage in the Actions column to go to the details page of the repository.

2. In the left-side navigation pane, click Build. On the page that appears, click Add Build Rule in the Build Rules section.

3. In the Add Build Rule dialog box, set the parameters as required.

   Parameter	Description	Example
   Type	The type of the content that is pushed to the source code repository to trigger the building rule. Valid values: Branch and Tag.	Branch
   Branch/Tag	The code branch or tag that triggers the building rule.	master
   Build Context Directory	The directory of the Dockerfile. The specified directory is a relative directory, and the root directory of the code branch serves as the parent directory. In this example, the directory of the Dockerfile is /Dockerfile. Enter /.	/
   Dockerfile Filename	The name of the Dockerfile. Default value: Dockerfile. For example, if the path of the Dockerfile is /Dockerfile, specify Dockerfile as the value of this parameter.	Dockerfile
   Image Tag	The tag of the image to be built.	V1.0.0

4. Click Confirm.

5. In the Build Rules section, find the rule that you created and click Build in the Actions column that corresponds to the rule.

   After you start the building, a building record is generated in the Build Log section. When the status of the building record becomes Successful, the image is built.

Results

Check whether the image is built

Run the image in Docker