From 42953faf70c5bc1ac66883e2f6bf85771fda3e01 Mon Sep 17 00:00:00 2001 From: Ilya Dmitrichenko Date: Fri, 5 May 2017 12:42:05 +0100 Subject: [PATCH] Fix some broken links in documentation --- site/cni-plugin.md | 2 +- site/operational-guide/tasks.md | 2 +- site/plugin.md | 1 - site/weavedns/load-balance-fault-weavedns.md | 2 +- site/weavedns/managing-entries-weavedns.md | 4 ---- 5 files changed, 3 insertions(+), 8 deletions(-) diff --git a/site/cni-plugin.md b/site/cni-plugin.md index 1afc632d..a3d114a3 100644 --- a/site/cni-plugin.md +++ b/site/cni-plugin.md @@ -12,7 +12,7 @@ search_type: Documentation CNI, the [_Container Network Interface_](https://github.com/containernetworking/cni), is a proposed standard for configuring network interfaces for Linux application containers. CNI is supported by -[Kubernetes](http://kubernetes.io/), [Apache Mesos](mesos.apache.org) +[Kubernetes](http://kubernetes.io/), [Apache Mesos](http://mesos.apache.org) and [others](https://github.com/containernetworking/cni#who-is-using-cni). diff --git a/site/operational-guide/tasks.md b/site/operational-guide/tasks.md index 370426a0..3cb14c87 100644 --- a/site/operational-guide/tasks.md +++ b/site/operational-guide/tasks.md @@ -44,7 +44,7 @@ or possible: In some cases you may already be aware of the problem, as you were unable to execute `weave reset` successfully or because you know through other channels that the host has died. In these cases you can -proceed straight to [Manually Reclaiming Lost Address Space](#reclaim-address-space). +proceed straight to [Manually Reclaiming Lost Address Space](#manually-reclaim-address-space). However in some scenarios it may not be obvious that space has been lost, in which case you can check for it periodically with the diff --git a/site/plugin.md b/site/plugin.md index 476eeee2..deb8b1de 100644 --- a/site/plugin.md +++ b/site/plugin.md @@ -6,7 +6,6 @@ search_type: Documentation * [Launching Weave Net and Running Containers Using the Plugin](#launching) * [Restarting the Plugin](#restarting) - * [Configuring the Plugin](#configuring) Docker versions 1.9 and later have a plugin mechanism for adding different network providers. Weave Net installs itself as a network diff --git a/site/weavedns/load-balance-fault-weavedns.md b/site/weavedns/load-balance-fault-weavedns.md index 78991cb4..d55c416a 100644 --- a/site/weavedns/load-balance-fault-weavedns.md +++ b/site/weavedns/load-balance-fault-weavedns.md @@ -49,7 +49,7 @@ WeaveDNS removes the addresses of any container that dies. This offers a simple way to implement redundancy. E.g. if in our example we stop one of the `pingme` containers and re-run the ping tests, eventually (within ~30s at most, since that is the weaveDNS -[cache expiry time](#ttl)) we will only be hitting the address of the +[cache expiry time](/site/weavedns/managing-entries-weavedns.md#ttl)) we will only be hitting the address of the container that is still alive. **See Also** diff --git a/site/weavedns/managing-entries-weavedns.md b/site/weavedns/managing-entries-weavedns.md index edfb6408..b2085248 100644 --- a/site/weavedns/managing-entries-weavedns.md +++ b/site/weavedns/managing-entries-weavedns.md @@ -4,17 +4,13 @@ menu_order: 40 search_type: Documentation --- - The following topics are discussed: * [Adding and removing extra DNS entries](#add-remove) * [Resolving WeaveDNS entries from the Host](#resolve-weavedns-entries-from-host) * [Hot-swapping Service Containers](#hot-swapping) -* [Retaining DNS Entries When Containers Stop](#retain-stopped) * [Configuring a Custom TTL](#ttl) - - ### Adding and Removing Extra DNS Entries If you want to give the container a name in DNS *other* than its