Skip to main content

Build Failures

Build phase issues are primarily docker errors, mostly due to incorrect Dockerfile configuration. Refer to optimizing container images or search online for docker-related solutions and tutorials.

How to handle the error message "network connection aborted."?​

Due to unforeseeable factors such as unstable access to overseas networks, it is recommended to use domestic sites as mirrors for downloading dependencies and extensions.

How to Handle Missing Dependency Errors? For example: java.lang.NoClassDefFoundError: Could not initialize class xxx​

The Dockerfile is missing the corresponding dependency installation command. It is recommended to prioritize using a more complete base image for building rather than directly adding dependency installation commands (RUN apk xxx), as it is simpler, more convenient, and improves build speed. Please go to the official repository of GitHub-Containers on Docker Hub to choose a suitable base image yourself (which by default includes all the dependencies you need), then replace the "FROM xxxxx as build" command in the Dockerfile.

How to handle the error message "xxxxxx: no such file or directory"?​

Please first check the following configuration information:

  • Ensure the file actually exists in the code repository/package and the path is correct.
  • Ensure that this file is not included in .gitignore or .dockerignore. If included, it will be ignored during the build; simply remove it.
  • Ensure that the COPY command in the Dockerfile does not alter the original file paths when copying files.

How to Troubleshoot When No Error Logs Are Displayed and the Screen Is Blank?​

It is highly likely that the build has timed out (> 10 minutes). Please optimize the container image to improve build speed and prevent timeouts. Please refer to Optimizing Container Images.