Overview
Alibaba Cloud Container Registry within the build out our services you can call on from your source code, set is based on Dockerfile of build rules, automatic image build run Dockerfile to perform the build and how to build it; After the completion of the auto-commit image to the image depending on the CI ability. Errors may lead to image building failures. This topic describes the possible problems during container image building, the causes of failures, and the solutions.
Description
Problem Type | Problem description | Solution |
---|---|---|
Failed to bind source code repositoryNote: to use the container registry service, you must select to bind the corresponding code repository when creating an image repository. |
An error of type "source code account does not have access" occurred while selecting code sources. |
Check whether the code source binding is successful. |
The code source is selected successfully, but the code repository you created cannot be found.
|
Select a solution based on the corresponding problem scenario:
|
|
The repository is created successfully, but the build bar is not found. |
To create an image repository bound to source code in the container registry console, follow these steps:
After successfully completing the entire process:
|
|
Failed to create build rule | The number of build rules exceeds the limit. |
If you require this type of quota, submit a ticket to increase the quota. |
Automatic build failure | The ACR container image building system relies on the webhook request sent by your source code platform to match the building rule, and then triggers the image building. In this case, the building fails. |
|
Slow construction speed | The image building speed is too slow, which may be affected by code pulling, image pulling, and resource downloading. This kind of problem is mainly affected by cross-domain poor network quality and low speed. |
Use ACR product capabilities to accelerate build:
|
Source code related failure | The error message returned because the source code repository does not exist or you are not authorized to perform the operation. |
If you change the username of the Alibaba Cloud Code account, the remote Code library cannot be pulled. See the following steps:
|
Source code pull timeout. |
Cross-domain source code pull times out due to unstable network quality. See use the acceleration feature to speed up code pulling. For more information, see the slow building feature section. |
|
Failed to pull the image. | Failed to pull images from overseas sources. |
ACR Container Build system has mirror dockerhub source. However, if you are using images from a foreign cloud vendor, the cross-domain link may affect the pull speed. You can resolve the issue using the following methods:
|
Failed to pull the Alibaba Cloud VPC domain name image from the ACR default instance. |
Use the public domain name of the default instance for image building. |
|
ACR-EE Enterprise Edition instance fails to pull the Alibaba Cloud Public Network domain name image. |
To build an image for the Container Registry Enterprise Edition instance, use a domain name that is connected to the VPC. |
|
Submit a ticket to solve other problems. | ||
Failed to push the image. |
After the build succeeds, the image push fails due to network problems. |
|
Long wait time for build task | The build service for both the ACR default instance and the Enterprise edition instance limits the number of concurrent builds for a single user. |
|
The build process failed. | The causes of errors during the build process are very responsible, but they can be divided into the following two types and solved by solution. |
|
Application scope
- Container Registry