Connection Timed Out
Symptom 1
After you add the deployment action Run Docker Command and set Command to pull, the error message request canceled while waiting for connection is displayed.
Cause Analysis
The image to be pulled is not tagged with the repository address, repository branch, or username, or the tag information is incorrect.
Solution
Enter a correct and complete image name, and try to pull the image again.
Symptom 2
After you add the deployment action Run Docker Command and set Command to push, the error message request canceled while waiting for connection is displayed.
Cause Analysis
The image to be pushed is not tagged with the repository address, repository branch, or username, or the tag information is incorrect.
Solution
Run the tag command to tag the correct repository branch information for the image to be pushed, and try to push the image again.
Symptom 3
After you add the deployment action Run Docker Command and set Command to login, the error message request canceled while waiting for connection(Client.Timeout exceeded while awaiting headers) is displayed.
Cause Analysis
- The image repository address is incorrect. As a result, the connection fails and Docker fails to verify the v2 interface.
- The host does not have the permission to access external networks or is not configured with a proxy. As a result, the connection to the remote image repository times out.
Solution
- Check the image repository address to ensure that it is correct and reachable.
- Configure a proxy for the host to connect to the image repository.
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.
more
