I'm following the guide at https://docs.docker.com/get-started/part2/#publish-the-image
Throughout the guide I've had trouble with this error sometimes coming up and sometimes when I rerun the commands they will work.
docker push %username%/%repository%:%tag%
I will get a response of Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I'm using Windows Home with Docker Toolbox.
Please let me know if any additional information is needed.
Simply go to the Docker's Settings > Network and change DNS Server radio button to Fixed
Unfortunately answers above didn't help in my case, but restarting Docker did.
For anyone else who's looking I found the answer here which led me to here
Specifically for me these steps were helpful. In case the links break in the future.
This worked for Windows 10 Home/Docker Toolbox
Right click on wifi icon on bottom right of the screen and open network and sharing center.
Right click on the connection at "connections:"
Click on Properties
Uncheck IPv6
Check IPv4
Click properties
Select radio button Use the following DNS addresses
For preferred use 8.8.8.8
Restart the computer and try again.
In case someone runs his own docker repo.
I had a similar "Client.Timeout exceeded while awaiting headers" when running
docker login myownrepo.com:5000
It happened to be that i had port forwarding only for port 5000, and forgotten to add for port 5001.
The issue was resolved by adding port 5001 (on my router) pointing to the same docker-repo-host.
Do not add proxy unless it is required to access registry. In my case behind corporate network, I had added proxy which resulted in timeout error, after removing the proxy configuration in Docker Desktop, it got resolved. Hope it helps somebody.
"Client.Timeout exceeded while awaiting headers" is a symptom of several possible causes. In my case it was simply a case of the private network firewall blocking the docker client machine from accessing the registry host machine.
To test if that's the case (for whoever may be reading this), first try temporarily disabling the private network firewall.
For instance, if the private docker registry is hosted on Windows 10:
1) open Windows Security
2) click on Firewall & network protection
3) ensure Private Network is "active" and click on it
4) under "Microsoft Defender Wall" switch OFF private firewall
If the IP is suddenly accessible then you need to re-enable the firewall on the host and configure it to allow access to the docker registry.
I had this problem as I was using docker-reg:5000 under WSL2.
Adding it to /etc/hosts did not work.
As docker really works under windows, you need to add it to the WINDOWS hosts file.
C:\Windows\System32\drivers\etc\hosts
In my case having a slow and not stable internet connection was causing the issue. So if it is possible to increase performance of your connection do that, but in my case i retried it multiple times and it worked after a while.
I've hit a brick wall and can't get past it as there isn't too much information out there on this problem. I have a VirtualBox on my Windows machine running Ubuntu with JetBrains Hub and Upsource installed on it. For making it public I am using apache2. I am able to run 'upsource.sh start' and start upsource ok, however when I try to access the website from an external network, the page gets stuck at 'Loading...' and then fails with '[name of my virtual box] server DNS address could not be found.'.
I am able to access the site from the internal network and everything works fine. I am forwarding a port from my public IP to the virtualbox port that is listening for JetBrains Upsource.
My hint is that the virtualbox is redirecting to itself and the client on the external network cannot reach that address. I am unfamiliar with apache so I'm not sure that it's configuration is setup properly. If anyone has run into this problem and fixed it or if anyone knows how to begin to debug/fix this... I'm all ears.
Thank you guys.
EDIT: The server seems to be hanging when the request for OAuth2 is made. Its making request to the virtualbox's local address rather than the public ip.
To anyone who runs into the problem in the future, I had to reinstall and put in the correct base-url. I'm guessing I was missing some properties that I needed to re configure and I could not find anywhere what all properties that I could configure.
I am able to access the link http://localhost/men/tops-men/jackets-men.html successfully from my VM (configured using X2Go client).
IP Address of the VM: 10.146.106.204
I am also able to ping the VM successfully from my host machine (Windows).
The page that I am trying to access is a php page deployed on Apache Web Server.
However I am not able to do so from my Windows host machine.
I tried http://10.146.106.204/men/tops-men/jackets-men.html from my Windows machine but it did not work.
Do I have to configure something on my host machine or on my VM ?
Not sure what I am missing.
On VM check you can view http://10.146.106.204/men/tops-men/jackets-men.html
If not you need to configure the web server to listen on that IP (if you're running IIS this is under "bindings" in the right-hand side panel of IIS Manager).
On Host open a cmd window and check you can ping 10.146.106.204
If not check your firewall settings on the VM.
If neither of these 2 things help then you need to add more information about your setup to the question. Those are 2 very simple things you can do to diagnose 2 basic problems you might be having.
I was finally able to solve the problem based on this SO link: Unable to access magento site from anywhere but localhost
Updated the DB table core_config_data and updated the data by replacing http://localhost with http://ip-of-vm and then restarted the apache web server.
I'm trying to reach a TFS server (either via VS2015 or Web) from my Windows 10 dev box with no luck. I keep getting timeout error
This server is on a remote network that I access via VPN.
I've tried on different Win10 boxes, and it is the same problem.
People in the local network (no vpn) also tried on Windows 10 with no luck
If I access the server on a Windows 7 dev box, everything is OK.
I am able to access a different TFS server (located on my domain network) correctly; same port and protocol.
I disabled the computer firewall
Any clue?
Try to use the IP Address such as http://xxx.xxx.xx.xx:8080/tfs instead of http://compandyname:8080/tfs
I have successfully installed hortonworks sandbox in vmware and finally I am getting this screenshot of vmware
However I tried that ipaddress in browser but getting below error .
This site can’t be reached
192.168.247.135 took too long to respond.
Try:
Reloading the page
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_TIMED_OUT
To access the Hortornworks Sandbox from putty or browser you have to perform 2 steps in Network setting as below in picture:
Set Adapter 1 attached to NAT
Set Adapter 2 attached to Host-only Adapter
Please refer the steps from the pictures above and it will work because same setting is working for me.