Normal command output
Warning: failed to get default registry endpoint from daemon (Error response from daemon: dial tcp 10.0.75.2:2375: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).
I am getting this intermittently: after a while (of inactivity?) no docker command can contact the daemon running in the Hyper-V machine and I have to restart the machine manually using the Windows Hyper-V client app. Everything runs as usual as soon as it has restarted.
Steps to reproduce the behavior
Haven’t find any way to reproduce this (except by just waiting until it fails).
Same here. I stop Docker via SysTray and restart completely, because restarting the MobyLinuxVM via Hyper-V seems to work only sometimes.
I can reproduce the symptome by CTRL-C a long running operation e.g. pull
+1. Version 1.11.0.-beta6 (build 1288). I use stop Docker via systray and restart as a workaround. Restarting MobyLinuxVM once caused completely non-working state on previous build of Docker.
Thanks for your reports.
We changed the way the network is setup in Beta6 and unfortunately you and several other users have experienced intermittent failures. We think we have identified what’s going on and are working on a solution.
In the meantime, restarting the application via the systray, while unsatisfying, should help.
yup, having a hard time with this one as well. Can’t get my build to get all the way through before failing…
[19:44:35.198][Proxy ][Info ] 2016/04/11 19:44:35 dial tcp 10.0.75.2:2375: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Good news, we root-caused and (hopefully) fixed the issue with the connection stopping after a while. This will be pushed with the next Beta sometime later this week (we are holding back for the 1.11 release).
We also hopefully fixed a number of other networking related issues, though we were unable to reproduce some of the issues reported in this thread and elsewhere. For these cases we have hopefully improved our data collection should these issues occur, which should help with the debug.
Apologies for the issues and many thanks for the feedback and help in debugging them
Good! I think it would be a good idea for all of us and you if there was a
better way to track issues in some way.
In the upcoming beta releases, is the docker team planning for any type of telemetry support?
Since some of the issues that the beta testers have encountered may not be possible to be replicated within the docker team, if there is some way for us to share the logs or additional info with the team when the system crashes or fails to work as expected, may be useful to do root cause analysis and help with future bug fixes.
we already have that in place, but in the upcoming Beta we improved what data we collect. We also now added the unique ID to the logs, so if users experience an issue they can report the ID in the forum, making it easier for us to identify the logs on our server.
Any update on this? I consistently have failing error messages when starting Docker Beta on OSX.
Error message is listed below
Warning: failed to get default registry endpoint from daemon (Error response from daemon: Bad response from Docker engine). Using system default: https://index.docker.io/v1/
@jaredestroud this is the Docker for Windows forums. If you have issues with Docker for Mac please post on it’s forum
I also seem to lose internet connectivity during a large operation where many modules need to downloaded.
I am using this version: v1.11.2-beta15 (build: 4450).
This issue prevents me from completing the large operation.
Try sudo chmod 666 /var/run/docker*
Hi @jaredestroud have you solved this issue?