build Command Execution Failed
Symptom 1
After you add the deployment action Run Docker Command and set Command to build, the error message Dockerfile: no such file or directory is displayed.
Cause Analysis
The Dockerfile path is incorrect, or the Dockerfile does not exist in the path.
Solution
Check whether the Dockerfile path is correct and whether the package and file on which the image build depends are in the same path as the Dockerfile.
Symptom 2
- During the deployment of the build command in the action Run Docker Command, the error message request canceled while waiting for connection and a FROM statement are displayed.
- During the deployment of the build command in the action Run Docker Command, an error message (not found) indicating that the base image is not found and a FROM statement are displayed.
Cause Analysis
The base image following the FROM statement in the Dockerfile does not exist in the local host or the remote repository. Another possible cause is that you have not logged in to the remote repository and cannot pull the base image from the remote repository.
Solution
When deploying the build command, ensure that you have logged in to the remote repository or have pulled the base image from the repository to the local host.
Symptom 3
During the deployment of the build command in the action Run Docker Command, an error message indicating that the command in the Dockerfile fails is displayed in the stderr log and the build command execution logs are also printed.
Cause Analysis
The information such as user information in the Dockerfile is incorrect, or the command is incorrectly run during the build process.
Solution
Modify the Dockerfile based on the log information to ensure that all information in the file is correct and the command can be deployed properly.
Running Docker Commands FAQs
- Docker Not Installed
- Docker Command Parameter Error
- No Deployment Permissions
- Image Does Not Exist
- login Command Execution Failed
- build Command Execution Failed
- tag Command Execution Failed
- push Command Execution Failed
- run Command Execution Failed
- start, restart, stop, or rm Command Execution Failed
- rmi Command Execution Failed
- pull Command Execution Failed
- rm Command Execution Failed
- Connection Timed Out
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
