tag Command Execution Failed
Symptom 1
After you add the deployment action Run Docker Command and set Command to tag, the error message ...requires exactly 2 arguments... is displayed.
Cause Analysis
The possible causes are as follows:
- Multiple groups of images are not separated by line breaks.
- The format of the image tag is incorrect.
Solution
Perform the following operations based on the failure causes:
- Separate multiple groups of images with line breaks.
- Modify the image tag format as prompted.
Symptom 2
After you add the deployment action Run Docker Command and set Command to tag, the output indicates that the tag command is in the format of docker tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]... and that the execution parameters end with a line break.
Cause Analysis
One or more line breaks (\n) are mistakenly added to the end of the images to be tagged.
Solution
Delete the last line break in the text box for tagging multiple groups of images.
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