TLS handshake timeout

[DBProductions]

Get https://registry-1.docker.io/v1/repositories/library/redis/tags/latest: net/http: TLS handshake timeout

Happens all the time (tried four times), I ask myself if it's based on my current location or a common problem. Maybe the government of China is blocking this service because your website is also blocked.
The URI https://registry-1.docker.io/v1/repositories/library/redis/tags/latest itself is reachable.
Same behaviour with Nginx image but works fine with boot2docker and docker on command line.

[ruandao]

get similar issue:

Get https://registry-1.docker.io/v1/repositories/library/node/tags/latest:
 net/http: TLS handshake timeout

I am in China, too.

[ruandao]

I get the same result when I use Japanese vpn(on aws)

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

[ruandao]

my download was success, after i delete previous machine and let Kitematic create a new one:

docker-machine rm default

It was easy get stuck in some layer download, even i kill terminal, and restart pull image.
It just hint this layer was download by another, and will not download it.

[FrenchBen]

@ruandao Did you take a look at the wiki on setting up a proxy?
https://github.com/kitematic/kitematic/wiki/Common-Issues-and-Fixes#proxy-issues

Perhaps it can help smooth some of the connection issues.

[FrenchBen]

Closing due to no further details provided

[jppmateus]

Have the same problem in Portugal. I've deleted default machine but the problem persists. Anyone know how to solve this problem?

[FrenchBen]

@jppmateus did you look at https://github.com/kitematic/kitematic/wiki/Common-Issues-and-Fixes#proxy-issues ?

[leowmjw]

Hit this (from Malaysia) when working with a slightly more complex Docker setup --> openspending/openspending#891

Tried a few time; and each time after it freezes, I have to restart the docker-machine (see steps below) and it continue to works until it fails again. When it fails, it seems like all network operations do not work any further.

Kitematic / docker-machine needs to be more robust to poor network condition and not die; needing a restart.

To fix, followed the steps in moby/moby#16829; but root cause of this "hang" is unknown.

docker-machine restart default
eval $(docker-machine env default)

[vipulswarup]

I did a "docker logout" and then a "docker login" and reran the command. Problem gone.

[mathieu-rossignol]

For me a simple "docker logout" (no login afterwards) dit it. Thx @vipulswarup.

[ghost]

Hi guys, I've a similar issue, this is the error:

ERROR: error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/19/1934b0b038d1e8bc64c275b2535fbe808477f5702fbd9a437851a24f9b97d15d/data?Expires=1510843446&Signature=cD2XmGfoJ3wWe3Ybs8Mj1Uaie0gpdNBnuWgjSLUl3Att-u0bN2UObR2VQkdK-5oV1ZlO-VkOhpo1Uryw2O0GZv9TL25bS9VKotCUPWKfXPiXD--0~dGy89dXss4sApT68fAJWA5-sQLLFMIMRamAsOH8EQLaYQ2YyJerFQbABso_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp 54.192.59.197:443: i/o timeout

but also I've got TLS handshake timeout too..

Any thoughts about this?

Appreciated in advance.

FYI: I'm on linux environment (ubuntu 14.04)

Thanks,

[gavin-cooker]

I always get the result:TLS handshake timeout

[inonbaguio]

Thanks @vipulswarup

@bruno-serfe @LinShouGui A simple docker login and docker logout fixed this issue. Should be applicable if you created the machine without first logging in. I believe docker needs to refresh the registries for proper docker push in the future.

[helmesjo]

The solution @vipulswarup proposed worked for me, even though I was never logged in, and when running docker login I just pressed enter and let it fail (Error: Non-null Username Required)...
#looksfinetome :)

[icbd]

如果使用SS时遇到此问题, 请在docker里手动设置代理.

[DlnZH]

@icbd ,请问这个代理。。。是您自己架设的吗？需要用代理是因为 大绿墙 吗？

[menglong2234]

@DlnZH 只是把端口设置在本机的代理本地端口而已，需要代理的原因大家都知道就没必要说出来了😏
我就是这样解决的。。

[Kevin-Zhang225]

@menglong2234 能不能不要只 show( off ), 说的详细点可好？

[Kevin-Zhang225]

@icbd 说的详细点可好？

[Kevin-Zhang225]

try dockerhub of Chinese version, it can bypass the tls handshake problem:
$ docker pull myname/myrepo:mytag -->$ docker pull registry.docker-cn.com/myname/myrepo:mytag
hope my advice will help you

[notHide]

@MarinZhang Thx ! worked

[alitrack]

@helmesjo , it works, thanks

[bryan831]

for me, i had a stupid mistake. i entered the wrong address for the image.
Hopefully this will help others who might've run into this as well.
i ran docker run continuum.io/anaconda instead of docker run continuumio/anaconda and it threw this error.

[korya]

I started to experience the issue about 2-3 weeks ago. My observation is that if docker fails to push an image to the registry (in my case it is Docker Hub) at some layer, it can keep failing at the same layer. The solution that worked for me is to remove the image and rebuild it from scratch. Note: in my setup, rebuilding an image from scratch always results in a new hash of the generated image.

The error I see:

fccbfa2912f0: Layer already exists
Head https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/c9/c91c36f3dddeecb85898a43fe550163a755e570666249265c339820fab0ca89f/data?verify=1531171424-bntwmPUbN8267s1brEWwenzSkvQ%3D: net/http: TLS handshake timeout

Docker version:

$ docker version
Client:
 Version:      18.05.0-ce
 API version:  1.35 (downgraded from 1.37)
 Go version:   go1.10.2
 Git commit:   f150324
 Built:        unknown-buildtime
 OS/Arch:      darwin/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.01.0-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.2
  Git commit:   03596f5
  Built:        Wed Jan 10 20:13:12 2018
  OS/Arch:      linux/amd64
  Experimental: false

[adipuscasu]

Using a VPN and connecting to another network did the trick.

[jian-mo]

I'm in China. Using a vpn solved this problem

[prusswan]

Setting DNS to 8.8.8.8 worked for me: https://stackoverflow.com/questions/39655314/docker-for-windows-error-pulling-image-configuration-i-o-timeout

[bennytaccardi]

To be honest, I resolved this issue with a simple restart of Docker

[runzhliu]

For Chinese users, I recommend this setting as follows:

[andrew-aladev]

Hello. I can say how to reproduce it.

rc-service docker stop
docker login
rc-service docker start
buildah/docker push

And you can fix it with:

docker logout
rc-service docker restart
docker login
buildah/docker push

[dhruvgajwa]

Or you can disable the TLS handshake!
Step 1: Right click on docker icon in your system tray
Step 2: CLick on Settings -> General
Step 3: Check the box with title: Expose daemon without TLS

[DrPride]

win 10 pro + docker desktop
logout do solve the problem.

[lunaryan]

To be honest, I resolved this issue with a simple restart of Docker

Me, too

[letmerecall]

try switching your internet connection.

[SasukeBo]

I did a "docker logout" and then a "docker login" and reran the command. Problem gone.

this work, thx

[pavanmbm]

I did a "docker logout" and then a "docker login" and reran the command. Problem gone.

it worked for me as well

[nayan2]

I was having the same issue. I just configured Manual DNS which is 1.1.1.1. That solves everything for me.