replaced URLs for weave proxy section
This commit is contained in:
abuehrle committed
1 parent
c3d96ca448
commit
905d923880
12 files changed
+17
-17
No files matched your search
+1
-1
@@ -117,5 +117,5 @@ Ubuntu image with those two commands added.
|
||||
|
||||
* [Troubleshooting Weave](/site/troubleshooting.md)
|
||||
* [Troubleshooting IPAM](/site/tasks/ipam/ipam.md)
|
||||
* [Troubleshooting the Proxy](/site/weave-docker-api/using-proxy.md)
|
||||
* [Troubleshooting the Proxy](/site/tasks/weave-docker-api/using-proxy.md)
|
||||
|
||||
@@ -17,7 +17,7 @@ If you are on OSX and you are using Docker Machine ensure that a VM is running a
|
||||
before downloading Weave Net. To set up a VM see [the Docker Machine
|
||||
documentation](https://docs.docker.com/installation/mac/#from-your-shell) or refer to ["Part 1: Launching Weave Net with Docker Machine"](/guides/part-1-launching-weave-net-with-docker-machine/).
|
||||
|
||||
After your VM is setup with Docker Machine, Weave Net can be launched directly from the OSX host. Weave Net respects the environment variable `DOCKER_HOST`, so that you can run and control a Weave Network locally on a remote host. See [Using The Weave Docker API Proxy](/site/weave-docker-api/using-proxy.md).
|
||||
After your VM is setup with Docker Machine, Weave Net can be launched directly from the OSX host. Weave Net respects the environment variable `DOCKER_HOST`, so that you can run and control a Weave Network locally on a remote host. See [Using The Weave Docker API Proxy](/site/tasks/weave-docker-api/using-proxy.md).
|
||||
|
||||
With Weave Net downloaded onto your VMs or hosts, you are ready to launch a Weave network and deploy apps onto it. See [Using Weave Net](/site/using-weave.md).
|
||||
|
||||
|
||||
@@ -58,7 +58,7 @@ See [Using Fast Datapath](/site/tasks/manage/fastdp.md) and
|
||||
|
||||
### <a name="docker"></a>Seamless Docker Integration (Weave Docker API Proxy)
|
||||
|
||||
Weave Net includes a [Docker API Proxy](/site/weave-docker-api.md), which can be
|
||||
Weave Net includes a [Docker API Proxy](/site/tasks/weave-docker-api/weave-docker-api.md), which can be
|
||||
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:
|
||||
@@ -71,7 +71,7 @@ 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`.
|
||||
|
||||
See [Integrating Docker via the API Proxy](/site/weave-docker-api.md).
|
||||
See [Integrating Docker via the API Proxy](/site/tasks/weave-docker-api/weave-docker-api.md).
|
||||
|
||||
|
||||
### <a name="plugin"></a>Weave Network Docker Plugin
|
||||
|
||||
@@ -32,7 +32,7 @@ with the `--without-dns` argument).
|
||||
10.32.0.1
|
||||
|
||||
If you would like `/etc/hosts` to contain the Weave Net address (the
|
||||
same way [the proxy does](/site/weave-docker-api/name-resolution-proxy.md)),
|
||||
same way [the proxy does](/site/tasks/weave-docker-api/name-resolution-proxy.md)),
|
||||
specify `--rewrite-hosts` when running `weave attach`:
|
||||
|
||||
host1$ weave attach --rewrite-hosts c1
|
||||
|
||||
@@ -56,5 +56,5 @@ to the proxy, the specified label takes precedence over the container's name.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Name resolution via `/etc/hosts`](/site/weave-docker-api/name-resolution-proxy.md)
|
||||
* [Name resolution via `/etc/hosts`](/site/tasks/weave-docker-api/name-resolution-proxy.md)
|
||||
* [How Weave Finds Containers](/site/tasks/weavedns/how-works-weavedns.md)
|
||||
@@ -31,5 +31,5 @@ Docker-managed networks), the proxy must be launched using the
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using Automatic Discovery With the Weave Proxy](/site/weave-docker-api/automatic-discovery-proxy.md)
|
||||
* [Using Automatic Discovery With the Weave Proxy](/site/tasks/weave-docker-api/automatic-discovery-proxy.md)
|
||||
|
||||
@@ -56,4 +56,4 @@ proxy port.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api.md)
|
||||
* [Setting Up The Weave Docker API Proxy](/site/tasks/weave-docker-api/weave-docker-api.md)
|
||||
@@ -70,5 +70,5 @@ If for some reason you need to disable the proxy, but still want to start other
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Setting Up The Weave Docker API Proxy](/site/weave-docker-api.md)
|
||||
* [Securing Docker Communications With TLS](/site/weave-docker-api/securing-proxy.md)
|
||||
* [Setting Up The Weave Docker API Proxy](/site/tasks/weave-docker-api/weave-docker-api.md)
|
||||
* [Securing Docker Communications With TLS](/site/tasks/weave-docker-api/securing-proxy.md)
|
||||
@@ -89,8 +89,8 @@ to the original settings prior to running `stop`.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Using The Weave Docker API Proxy](/site/weave-docker-api/using-proxy.md)
|
||||
* [Securing Docker Communications With TLS](/site/weave-docker-api/securing-proxy.md)
|
||||
* [Launching Containers With Weave Run (without the Proxy)](/site/weave-docker-api/launching-without-proxy.md)
|
||||
* [Using The Weave Docker API Proxy](/site/tasks/weave-docker-api/using-proxy.md)
|
||||
* [Securing Docker Communications With TLS](/site/tasks/weave-docker-api/securing-proxy.md)
|
||||
* [Launching Containers With Weave Run (without the Proxy)](/site/tasks/weave-docker-api/launching-without-proxy.md)
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ The following topics are discussed:
|
||||
## <a name="domain-search-path"></a>Configuring the domain search paths
|
||||
|
||||
If you don't supply a domain search path (with `--dns-search=`), Weave
|
||||
Net (via the [proxy](/site/weave-docker-api.md) or via `weave attach`)
|
||||
Net (via the [proxy](/site/tasks/weave-docker-api/weave-docker-api.md) or via `weave attach`)
|
||||
tells a container to look for "bare" hostnames, like `pingme`, in its
|
||||
own domain (or in `weave.local` if it has no domain).
|
||||
|
||||
|
||||
@@ -45,5 +45,5 @@ disable weaveDNS itself, launch weave with the `--no-dns` option.
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Integrating Docker via the API Proxy](/site/weave-docker-api.md)
|
||||
* [Integrating Docker via the API Proxy](/site/tasks/weave-docker-api/weave-docker-api.md)
|
||||
* [Load Balancing and Fault Resilience with WeaveDNS](/site/tasks/weavedns/load-balance-fault-weavedns.md)
|
||||
@@ -286,7 +286,7 @@ on reboot. This can be disabled via:
|
||||
|
||||
Note that the Weave Net router will create the `weave` network bridge
|
||||
if necessary when it restarts, and the [Weave Net Docker API
|
||||
Proxy](/site/weave-docker-api.md) will re-attach any application
|
||||
Proxy](/site/tasks/weave-docker-api/weave-docker-api.md) will re-attach any application
|
||||
containers that it originally attached to the Weave network when they
|
||||
restart.
|
||||
|
||||
@@ -308,4 +308,4 @@ and the container image versions as git hashes.
|
||||
**See Also**
|
||||
|
||||
* [Troubleshooting IPAM](/site/tasks/ipam/troubleshooting-ipam.md)
|
||||
* [Troubleshooting the Proxy](/site/weave-docker-api/using-proxy.md)
|
||||
* [Troubleshooting the Proxy](/site/tasks/weave-docker-api/using-proxy.md)
|
||||
Reference in new issue
Block a user