Reword weave proxy intro
This commit is contained in:
1 parent
5382037c4e
commit
aafc1a56f9
2 files changed
+7
-6
No files matched your search
+1
-1
@@ -408,7 +408,7 @@ out more about WeaveDNS from its [documentation](weavedns.html).
|
||||
|
||||
### <a name="proxy"></a>Starting containers with Docker
|
||||
|
||||
Instead of the weave command-line utility, you may prefer to use the
|
||||
Instead of the `weave` command-line utility, you may prefer to use the
|
||||
standard Docker command-line interface, or the Docker remote API, for
|
||||
starting weave-enabled containers. This can be accomplished with the
|
||||
[Weave Proxy](proxy.html).
|
||||
+6
-5
@@ -5,9 +5,11 @@ layout: default
|
||||
|
||||
# Proxy
|
||||
|
||||
The weave proxy automatically attaches containers to the weave network
|
||||
that have been started using the ordinary Docker command-line
|
||||
interface or Docker remote API.
|
||||
Instead of the `weave` command-line utility, you may prefer to use the
|
||||
standard Docker command-line interface, or the Docker remote API. The
|
||||
weave proxy sits between the `docker` command or API and the Docker
|
||||
daemon, so that it can automatically attach containers to the weave
|
||||
network.
|
||||
|
||||
Using the proxy brings some additional benefits over `weave run`. The
|
||||
proxy ensures that the weave network interface is available before
|
||||
@@ -17,8 +19,7 @@ can be started in foreground mode, and can be automatically removed
|
||||
|
||||
## Setup
|
||||
|
||||
To do this, while still connecting containers to the weave network,
|
||||
you can use the weave proxy. We can start the proxy with
|
||||
Start the proxy with
|
||||
|
||||
host1$ weave launch-proxy
|
||||
|
||||
|
||||
Reference in new issue
Block a user