Ping @ewindisch @unclejack @dmp42 @dmcgowan

Please add some documentation about this special case.

I restarted the drone build

do we want to move forward with this? (i.e: would you consider merging if I make the doc changes)

What about ::1?

@mmdriley good catch, wondering if this work at all with docker pull ::1/foo.

+1

I'm NO on this. I prefer secure-by-default.

Note that our use of TLS here is not for protocol security, i.e. to prevent MITM, but for host verification. It verifies that the registry is trusted by the daemon and the systems administrator.

There seem to be good workarounds to this including setting '--insecure-registry localhost' and making localhost-with-TLS easier to deploy out of the box.

There seem to be good workarounds to this including setting '--insecure-registry localhost' and making localhost-with-TLS easier to deploy out of the box.

Yes, but that's not something that's easy to control with boot2docker today, or with the current registry. So current users of the docker (1.3.1) + boot2docker + registry might be broken for a while.

Sorry @ewindisch I'll have to merge this, this is a stopgap, and has no UI change compared to 1.3.1. We can revert it for 1.4 once we have a better user experience, like putting a URL to a page explaining how to setup a TLS private registry. We would update that page to have a one-liner like $(docker run -v /etc/docker/certs.d:/certs.d registry:tls).

LGTM @proppy rebase please

rebased PTAL

added DCO

hey @proppy I'm going to carry this.

Closing this, please review over at #9124

I have to run this command every time I start boot2docker to fix this issue:

boot2docker ssh 'sudo sh -c "echo \"EXTRA_ARGS=\\\"--insecure-registry 10.0.0.0/8\\\"\" > /var/lib/boot2docker/profile && sudo /etc/init.d/docker restart"'