[proxy] Documenting TLS autoconfig
This commit is contained in:
1 parent
dbf39403d3
commit
0820c484d6
2 files changed
+21
-17
No files matched your search
+4
-8
@@ -15,15 +15,11 @@ instructions. First, we need to get Boot2Docker running:
|
||||
|
||||
Assuming you have fetched the 'weave' script via curl or similar, and
|
||||
it is in the current directory, launch weave on the Boot2Docker VM and
|
||||
configure our shell. Because Boot2Docker uses TLS, we have to pass a
|
||||
few extra options when launching the docker API proxy:
|
||||
configure our shell. Boot2Docker uses TLS, but weave will auto-detect
|
||||
that, and configure things appropriately.
|
||||
|
||||
host1$ ./weave launch-router
|
||||
host1$ ./weave launch-proxy --tls \
|
||||
--tlscacert /var/lib/boot2docker/tls/ca.pem \
|
||||
--tlscert /var/lib/boot2docker/tls/server.pem \
|
||||
--tlskey /var/lib/boot2docker/tls/serverkey.pem
|
||||
host1$ eval "$(./weave env)"
|
||||
host1$ weave launch
|
||||
host1$ eval "$(weave env)"
|
||||
|
||||
Now, we can use the docker command to run our containers, as shown in
|
||||
the [proxy documentation](proxy.html):
|
||||
|
||||
Reference in new issue
Block a user