reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Emphasise the ways in which IP addresses must not conflict

Browse Source
This commit is contained in:
Bryan Boreham committed 2014-11-04 12:08:38 +00:00
1 parent 97c31f0a15
commit 0d3de8bd38
1 file changed
+5 -5
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -5
View File
@@ -73,11 +73,11 @@ shell in it. There's also a `weave start` command, which invokes
If our application consists of more than one container on this host we
simply launch them with a variation on that second line.
The IP addresses and networks can be anything you like which doesn't
conflict with any IP ranges of 'external' services the hosts or your
containers need to connect to. The same IP range must be used
everywhere, and the individual IP addresses must, of course, be
unique.
The IP addresses and netmasks can be anything you like, but make sure
they don't conflict with any IP ranges in use on the hosts or IP
addresses of external services the hosts or containers need to connect
to. The same IP range must be used everywhere, and the individual IP
addresses must, of course, be unique.
We repeat similar steps on $HOST2...