Insecure mode appears to be broken with docker 1.3.1

[jbalonso]

I'm starting to see this:

Invalid registry endpoint https://---REDACTED---/v1/: Get https://---REDACTED---/v1/_ping: EOF. If this
private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-
registry ---REDACTED---` to the daemon's arguments. In the case of HTTPS, if you have access to
the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/
---REDACTED---/ca.crt

I'm sad to see the efforts of #573 and #490 stumble here.

[jbalonso]

For the record: I was able to confirm this behavior by downgrading to docker 1.3.0 and getting the proper behavior from fig pull --allow-insecure-ssl.

[dnephin]

From the changelog it looks like this is new. 1.3 added default HTTPS for the dockerd, 1.3.1 added it for the registry.

I guess we need to either have --allow-insecure-ssl add --insecure-registry as well, or add a second flag, which may also require a docker-py change.

[dnephin]

We've removed the need to communicate with the registry at all, so this should be resolved.