Overview
Alibaba Cloud Container Registry allows you to build images from a code source. Container Registry automates the building and delivery of images from source code repositories to Container Registry repositories based on Dockerfiles. If an error occurs, images may fail to be built. This document describes the issues that may occur in the process of building images, causes, and solutions.
Details
Problem type |
Problem description |
Solution |
Failure to bind a source code repository
|
When you select a code source, an error message appears to remind you that the account of the source code repository has no permission to access GitLab. |
Check whether the code source is bound in Container Registry. |
You select a code source, but the source code repository that you create fails to be found due to one of the following causes:
|
Select an appropriate solution based on your needs:
|
|
You create an image repository, but cannot find the Build page. |
Container Registry performs the following steps to create an image repository and bind it to a source code repository: 1. Create an image repository. 2. Send a request to your source code repository by using the access token that you specify, and set a webhook in the repository. 3. Bind the image repository that is created in Step 1 to your source code repository. Then, you can perform the following steps to go to the Build page:
|
|
Failure to create an image build rule |
The number of image build rules has reached the upper limit. |
If you need to create more rules, submit a ticket. |
Failure to automatically build images |
When Container Registry is triggered to match image build rules and build an image based on a webhook request that is sent by your source code platform, the image may fail to be built. |
|
Slow image building |
The building of images is slowed down by code pulling, image pulling, and resource download due to the unstable network connection across regions. |
Use the following features of Container Registry to accelerate image building:
|
Failure to pull source code |
A source code repository does not exist, or you have no permission to access the source code repository. |
If the username of an Alibaba Cloud Code account is changed, source code cannot be pulled from the remote source code repository. Perform the following steps:
|
Pulling source code times out. |
The issue is caused by the unstable network connection across regions. For more information about how to use the Intelligently Build Overseas Sources feature to accelerate code pulling, see Slow image building. |
|
Failure to pull images |
Images fail to be pulled from a data center outside China. |
Container Registry uses images from Docker Hub. However, if you use an image from a cloud service provider outside China, the speed of image pulling may be slow due to the unstable network connection across regions. Use the following methods:
|
Images fail to be pulled from an instance of Container Registry Default Instance Edition by using the virtual private cloud (VPC) endpoint of the instance. |
If you want to build an image from the instance of Container Registry Default Instance Edition, use the public endpoint of the instance. |
|
Images fail to be pulled from an instance of Container Registry Enterprise Edition by using the public endpoint of the instance. |
If you want to build an image from the instance of Container Registry Enterprise Edition, use the VPC endpoint of the instance. |
|
Submit a ticket for other situations. |
||
Failure to push images |
Images may fail to be pushed due to network conditions. |
|
Long Pending state for image build tasks |
The Image Builder feature of both Container Registry Default Instance Edition and Container Registry Enterprise Edition imposes a limit on the number of concurrent tasks for a single user. |
|
Failure in the process of building images |
Although the cause of errors is complex, the process of building images may fail in two scenarios. |
|
Applicable scope
- Container Registry