Component Construction

Mirror Build Problem Troubleshooting

Mirroring is a basic way for Kato to build components. For specific operations, please refer to DOCKER Mirror Support Specification

During the construction process, the following problems may occur.

Service Build Source Detection Failed

This error screenshot appears, indicating that Kato failed to pull the specified image.

  • Solution:
    • First check, try docker pull <specified image> on the Kato management node to see if the image can be pulled normally
    • Check if the mirror address is wrong. Including but not limited to “:” in Chinese
    • Check whether the mirror repository requires a user name and password. If necessary, determine whether to fill in the user name and password when building
    • Is there any network restriction from Kato server to mirror repository server? Check network communication, whether the port is open

Based on mirrored components, it is a very robust construction method. As long as the image can be obtained normally, the build can be successful. Operation abnormality appears during runtime, please refer to Component Operation Troubleshooting

Troubleshooting Based on Dockerfile Source Code Build Problem

When building based on Dockerfile source code, please refer to DOCKERFILE build specification

During the construction process, the following problems may occur.

Service Build Source Detection Failed

This error message appears, indicating that Kato failed to obtain the code correctly from the code repository.

  • Solution:
    • Confirm whether the project address is filled in correctly. If the code to be pulled is in a subdirectory of the project root directory, add ?dir=<subdirectory name> to the repository address.
    • The project requires security verification, and the correct user name and password are not provided.
    • Use the ssh protocol to pull the code, you need to confirm whether the ssh authorization is correct.
    • Is there any network restriction from Kato server to code repository, and whether the domain name can be resolved. The simple verification strategy is to test git clone <repository address> on the Kato management node.

Build Failed

After the code is normally obtained, Kato will automatically enter the build process. The specific log will be reflected in the operation log. If the build operation finally shows build failed.

  • Solution:
    • There will be a detailed record of the construction process in the operation log, see if there is an error.
    • Try to build this project on the Kato management node. If the build fails, check the Dockerfile code first. Search for documents such as Nine Common Mistakes in Writing Dockerfile to learn how to write Dockerfile.
    • Determine whether the Kato server can connect to the specified resource to perform operations such as apt-get and wget.

Build Timeout

If there is a build timeout during the build process, this not necessarily indicates that the build has failed! It just means that the construction time exceeds the default value set by Kato. Whether it fails, and to determine the cause of the build error, please refer to the operation log for specific information.

Build Problem Troubleshooting Based on JAVA Language Source Code

When building based on the JAVA language source code, please refer to JAVA Development Language Support Specification

The Java language is the most used development language on the market. Kato not only directly deploys jar and war package projects, but also supports direct construction of java-maven projects. During the construction process, the following problems may occur.

Service Build Source Detection Failed

This error message appears, indicating that Kato failed to obtain the code correctly from the code repository.

  • Solution:
    • Confirm whether the project address is filled in correctly. If the code to be pulled is in a subdirectory of the project root directory, add ?dir=<subdirectory name> to the repository address.
    • The project requires security verification, and the correct user name and password are not provided.
    • Use the ssh protocol to pull the code, you need to confirm whether the ssh authorization is correct.
    • Is there any network restriction from Kato server to code repository, and whether the domain name can be resolved. The simple verification strategy is to test git clone <repository address> on the Kato management node.

GZIP STDIN not in GZIP Format

If this error message appears, it is confirmed that downloading jdk or maven failed.

Build Failed

After entering the maven build phase, the operation log will print maven build information starting with words such as [INFO] [WARNING] [ERROR]. The reasons for reporting errors at this stage are very complex and changeable. We have prepared a special document to describe the principle of this process, related settings and specific troubleshooting documents. Please read the following documents in order:

My Question is not Covered

If you still fail to build after reading this document, you can:

  • Go to GitHub to check whether there are related issues, and if not, submit issues

  • Go to Community to read the post with the prefix [Build Question] [Use Question] to find answers to similar questions