registry should generate certs

[proppy]

Since 1.3.1 docker rejects pulls from insecure location unless they are whitelisted with a new --insecure-registry flag.

We should make sure users can run google/docker-registry on localhost:5000, without having them to pass extra flag to their daemon.

For that we need to:

• include https://github.com/SvenDowideit/generate_cert in the docker image
• generate the certs in ttps://github.com/GoogleCloudPlatform/docker-registry/blob/master/run.sh
• update the README instructions to run the image with -v /etc/docker/certs.d

[proppy]

We also need to run a nginx container in front either as a separate container (good) or in the same image (bad).

@ktintc @dlorenc

[proppy]

one trick we could use is having the docker registry entry point output its own usage.

$(docker run docker-registry) would run:

docker run -v ... nginx
docker run -v ... docker-registry

[proppy]

Or we could just setup gunicorn to do SSL:http://gunicorn-docs.readthedocs.org/en/latest/settings.html#ssl

[tiborvass]

@proppy precisely what I did, i have a working example.

[proppy]

@tiborvass do you plan to push this upstream in docker/docker-registry?

[tiborvass]

@proppy yes

[proppy]

@tiborvass I was planning to work on this today, care to collaborate on this? I'm happy to either do the review or take over your working example.