Insecure, private v2 registry not working with 1.9.x engine?

Brad,
I’m very new to docker also but to answer your questions to the best of my ability here.

  1. No. an insecure registry is only accessible from local host. You need to set-up TLS/Certs to access beyond local host. It’s not a big deal for experimentation just generate self signed certs.
  2. Can’t be done to the best of my knowledge.

Now this is just a thought and not sure it would work. But if you don’t really care about security and running TLS properly then why don’t you create a dokerfile that follows the steps outlined to generate self signed certs and make a secure registry? This way you could configure it like I did but in the dockerfile and not on the command line. It’s not the right way but would probably get you around this issue. Now that the containers would be ephemeral I guess you have a plan on how to have clients connect to those containers. I saw this that might help you create that virtual domain if that’s how you where planning to do it: http://tech.mybuilder.com/virtual-hosts-with-docker/

v/r,
Frank