From 3eda2bd86dc9146c7e52ea857e53aaee673ab176 Mon Sep 17 00:00:00 2001 From: Jose Aguirre Date: Wed, 21 Sep 2016 15:20:12 -0700 Subject: [PATCH] Updating tribe doc to avoid port conflict - Just adds an additional flag to instructions to prevent error from testing on the same machine --- docs/TRIBE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/TRIBE.md b/docs/TRIBE.md index 7b538ecaa..c75954966 100644 --- a/docs/TRIBE.md +++ b/docs/TRIBE.md @@ -59,7 +59,7 @@ Since tribe is implemented on top of a gossip based protocol there is no "master Start another instance of snapd to join to our existing tribe. The local IP address is 192.168.136.176 in our example. Note that we need a few more parameters to avoid conflicting ports on a single system: ``` -$ snapd --tribe -t 0 --tribe-port 6001 --api-port 8182 --tribe-node-name secondnodename --tribe-seed 192.168.136.176:6000 +$ snapd --tribe -t 0 --tribe-port 6001 --api-port 8182 --tribe-node-name secondnodename --tribe-seed 192.168.136.176:6000 --control-listen-port 8083 ``` Both snapd instances will see each other in their member list: