New docker clients refuse to talk to docker registry

[sarahkevinking]

Receiving an error when pushing a local image to the coreapp repository.

The push refers to a repository [192.168.64.1:5000/foobar]
Get https://192.168.64.1:5000/v1/_ping: http: server gave HTTP response to HTTPS client

Using docker client

Docker version 1.12.1, build 23cf638, experimental

It would be nice if the registry would support TLS out of the box. I think it would be sufficient to generate our own TLS cert and key and support traffic over HTTPS

[rimusz]

need to look to that at some point

[lorin]

I've got the same problem, but a different error message:

The push refers to a repository [localhost:5000/ubuntu]
Put http://localhost:5000/v1/repositories/ubuntu/: dial tcp [::1]:5000: getsockopt: connection refused

The error message is misleading, the port is open:

$ nc -z localhost 5000
Connection to localhost port 5000 [tcp/commplex-main] succeeded!
$  curl localhost:5000/v2/
{}

Using docker client

Docker version 1.12.1, build 6f9534c

[rimusz]

sorry guys, it is in my plans already, I'm not using docker 1.12.1 yet, so had no chance to look to it yet.