run Command Execution Failed
Symptom 1
When you add the deployment action Run Docker Command and set Command to run, the operation does not stop until it fails.
Cause Analysis
The parameters set on the page are not specified to run in the background.
Solution
Add -d in the parameters to run the run command in the background.
Symptom 2
During the deployment of the run command in the action Run Docker Command, the error message Unable to find image * locally is displayed.
Cause Analysis
The local image does not exist.
Solution
Check that the image name and tag are correct, and run the image again.
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
