docs/engine/security/https
Misty Stanley-Jones e3a3145cd9 Sync vnext-engine branch to docker/docker SHA 2f12d2808464dcfdf45e0920fd508ce0ff12bd29
This branch will contain forward-looking Engine-specific docs
and be the equivalent of docker/docker master for docs
2017-01-19 10:10:15 -08:00
..
Dockerfile Sync vnext-engine branch to docker/docker SHA 2f12d2808464dcfdf45e0920fd508ce0ff12bd29 2017-01-19 10:10:15 -08:00
Makefile Sync vnext-engine branch to docker/docker SHA 2f12d2808464dcfdf45e0920fd508ce0ff12bd29 2017-01-19 10:10:15 -08:00
README.md Change 'draft: true' to 'published: false' for Jekyll 2016-10-10 16:19:47 -07:00
make_certs.sh Sync vnext-engine branch to docker/docker SHA 2f12d2808464dcfdf45e0920fd508ce0ff12bd29 2017-01-19 10:10:15 -08:00
parsedocs.sh Sync vnext-engine branch to docker/docker SHA 2f12d2808464dcfdf45e0920fd508ce0ff12bd29 2017-01-19 10:10:15 -08:00

README.md

published
false

This is an initial attempt to make it easier to test the examples in the https.md doc.

At this point, it has to be a manual thing, and I've been running it in boot2docker.

My process is as following:

$ boot2docker ssh
root@boot2docker:/# git clone https://github.com/docker/docker
root@boot2docker:/# cd docker/docs/articles/https
root@boot2docker:/# make cert

lots of things to see and manually answer, as openssl wants to be interactive

NOTE: make sure you enter the hostname (boot2docker in my case) when prompted for Computer Name)

root@boot2docker:/# sudo make run

Start another terminal:

$ boot2docker ssh
root@boot2docker:/# cd docker/docs/articles/https
root@boot2docker:/# make client

The last will connect first with --tls and then with --tlsverify, both should succeed.