From 3254870899639b3cb2744e7e793e766ba019a83d Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Tue, 5 Apr 2016 21:38:10 +0100 Subject: [PATCH] cosmetic: tweak proxy intro to make more sense --- site/features.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/site/features.md b/site/features.md index a71ed469..5473d605 100644 --- a/site/features.md +++ b/site/features.md @@ -65,19 +65,19 @@ See [Using Fast Datapath](/site/fastdp/using-fastdp.md) and ###Seamless Docker Integration (Weave Docker API Proxy) Weave Net includes a [Docker API Proxy](/site/weave-docker-api/set-up-proxy.md), which can be -used to launch containers to the Weave network using the Docker [command-line interface](https://docs.docker.com/reference/commandline/cli/) or the [remote API](https://docs.docker.com/reference/api/docker_remote_api/). +used to start containers using the Docker [command-line interface](https://docs.docker.com/reference/commandline/cli/) or the [remote API](https://docs.docker.com/reference/api/docker_remote_api/), and attach them to the Weave network before they begin execution. -To use the proxy run: +To use the proxy run host1$ eval $(weave env) -With the proxy enabled, you can start and manage containers using standard Docker commands. +and then start and manage containers with standard Docker commands. Containers started in this way that subsequently restart, either by an explicit `docker restart` command or by Docker restart -policy, are re-attached to the Weave network by the `Weave Docker API Proxy` +policy, are re-attached to the Weave network by the `Weave Docker API Proxy`. -See [Using the Weave Docker API](/site/weave-docker-api/using-proxy.md) +See [Using the Weave Docker API Proxy](/site/weave-docker-api/using-proxy.md) ###Weave Network Docker Plugin