ERROR: Network timed out while trying to connect

[mahnunchik]

Expected behavior

docker pull works

Actual behavior

docker pull does not work

ERROR: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/redis/images. You may want to check your internet connection or if you are behind a proxy.

Information

Steps to reproduce the behavior

1. docker pull any-image

[dgageot]

Hi @mahnunchik Could you share your logs or a diagnostic id? Thanks a lot!

[Icantthinkofanyname]

I have the same issue. I tried it both on stable and beta version as well.

[dgageot]

Hi @Icantthinkofanyname could you share your logs or a diagnostic id? Thanks a lot!

[mahnunchik]

@dgageot logs http://pastebin.com/RYi6tY04

[dgageot]

@Icantthinkofanyname @mahnunchik Can you try with a fixed DNS server?
Something like 8.8.8.8

[mahnunchik]

@dgageot I've tried, nothing has changed.

[glennsills]

I had this problem. I had previously been using Docker Toolbox with VirtualBox which I had uninstalled before installing Docker for Windows. I tried many suggestions involving fiddling around with the virtual network. Then I noticed that the uninstalling Docker Toolbox had left some folder in my AppData folder and so had Virtual Box. I deleted all that stuff manually, reinstalled Docker for Windows and voila - working Docker.

This could all be coincidental but you might want to give it a try. It only takes 5 minutes.

[changeisnormal]

@dgageot I've also tried that and it didn't work for me either.
@glennsills I had never install toolbox with VirtualBox before so I don't think that fits my situation.

[changeisnormal]

@dgageot

A diagnostic was uploaded with id: A4341136-0CD7-4779-AF29-A378002D0636/2016-08-05_15-23-48

[hineios]

I had the same problem. But after changing to a fixed DNS server it fixed my problem!

[Senegura]

Fixed DNS server don't solve my problem. I am always get "Network timed out while trying to connect to ... You may want to check your internet connection or if you are behind a proxy".

[saule1508]

I just installed docker, then I had this error. I switched to fixed DNS (8.8.8.8) and it solved the problem. Then I reverted the setting (removed the fixed DNS) and it keeps working.
I found the solution here: http://stackoverflow.com/questions/31990757/network-timed-out-while-trying-to-connect-to-https-index-docker-io

[Rhynier]

None of the advice above worked for me either. I am running Windows 10 Enterprise version 1511, build 10586.545. Uploaded diagnostic with ID AFCCE8AA-DEFB-4046-93FD-68B40FF3D9D8/2016-08-18_08-55-33.

[khalidsalomao]

+1
Same problem here with Windows 10 Pro version 1607 build 14393.51.
Diagnostic ID: B625FBF8-26D1-4A80-8F24-B93512DD68B9/2016-08-23_11-18-23

[zcl0621]

+1
I always got this issue

[dgageot]

@mahnunchik @Icantthinkofanyname @changeisnormal @Senegura @Rhynier @khalidsalomao @zcl0621 A new version (Beta25) was released yesterday with fixes to the network/dns stack. Could you please give it a try and tell us if you see an improvement? Thanks a lot!

[saule1508]

@dgageot : it solved the problem for me, thanks. (in a previous post I mentioned that switching to fixed DNS solved my issue but it was only temporarily fixed).

[dgageot]

@saule1508 \0/

[dgageot]

I believe this is a duplicate of #55

When I get a bit more users saying that Beta25 fixes the issue, I'll close both tickets

[dgageot]

Looks like Beta25 fixes the issue for a lot of users and nobody complained that the issue is still here. So let's close this ticket!

[mahnunchik]

It solved my problem. Thanks!

[khalidsalomao]

Problem solved!

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked