p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix doc format issue

Browse Source 
Signed-off-by: Kai Qiang Wu(Kennan) <wkqwu@cn.ibm.com>
Upstream-commit: 4d4d1e7f82592c4996650b92b01d9f4633e8878b
Component: engine
This commit is contained in:
Kai Qiang Wu(Kennan)
2016-02-23 03:42:10 +00:00
parent 0a2d56c7a2
commit d01d130fdc
1 changed files with 15 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
components/engine/docs/security/https/README.md
View File

@ -7,26 +7,27 @@ draft = true
This is an initial attempt to make it easier to test the examples in the https.md
doc
doc.
at this point, it has to be a manual thing, and I've been running it in boot2docker
At this point, it has to be a manual thing, and I've been running it in boot2docker.
so my process is
My process is as following:
$ boot2docker ssh
$$ git clone https://github.com/docker/docker
$$ cd docker/docs/articles/https
$$ make cert
$ boot2docker ssh
$$ git clone https://github.com/docker/docker
$$ cd docker/docs/articles/https
$$ 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`)
$$ sudo make run
start another terminal
$$ sudo make run
$ boot2docker ssh
$$ cd docker/docs/articles/https
$$ make client
Start another terminal:
the last will connect first with `--tls` and then with `--tlsverify`
$ boot2docker ssh
$$ cd docker/docs/articles/https
$$ make client
both should succeed
The last will connect first with `--tls` and then with `--tlsverify`, both should succeed.