From c6fea4939e1dedbfd8a4c0187a89013f7ccc48e6 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Wed, 30 Mar 2016 00:02:30 +0100 Subject: [PATCH] fix broken link --- site/ipam/allocation-multi-ipam.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/ipam/allocation-multi-ipam.md b/site/ipam/allocation-multi-ipam.md index d036f8b2..5af35e7e 100644 --- a/site/ipam/allocation-multi-ipam.md +++ b/site/ipam/allocation-multi-ipam.md @@ -9,7 +9,7 @@ puts all containers into a subnet that spans the entire allocation range, so that every Weave-attached container can communicate with every other Weave-attached container. -If you want some [isolation](/site/using-weave/isolating-applications.md), you +If you want some [isolation](/site/using-weave/application-isolation.md), you can choose to run containers on different subnets. To request the allocation of an address from a particular subnet, set the `WEAVE_CIDR` environment variable to `net:` when creating the