Fix some broken links in documentation
This commit is contained in:
1 parent
6c29a1f648
commit
42953faf70
5 files changed
+3
-8
No files matched your search
+1
-1
@@ -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).
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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**
|
||||
|
||||
@@ -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)
|
||||
|
||||
|
||||
|
||||
### <a name="add-remove"></a>Adding and Removing Extra DNS Entries
|
||||
|
||||
If you want to give the container a name in DNS *other* than its
|
||||
|
||||
Reference in new issue
Block a user