docs/engine/security/https
Sebastiaan van Stijn 03d5b3396d
Use consistent formatting for notes
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2019-02-09 00:49:57 +01: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 Use consistent formatting for notes 2019-02-09 00:49:57 +01: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 is 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/moby/moby
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 connects first with --tls and then with --tlsverify, both should succeed.