[FAB-3195] Sync boot peers in docker-compose-no-tls

The examples/e2e_cli/docker-compose-no-tls.yaml has peer0 as a bootstrap peer for all peers. This is against the design (it needs to be in the same org), and should be synced to what is found in docker-compose.yaml Change-Id: Id7e5d97611f9f64832b6bbc51a3a5e0599c27da0 Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>
hyperledger · Apr 17, 2017 · cafa04e · cafa04e
1 parent 56b6d12
commit cafa04e
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/examples/e2e_cli/docker-compose-no-tls.yaml b/examples/e2e_cli/docker-compose-no-tls.yaml
@@ -62,7 +62,7 @@ services:
       service: peer-base
     environment:
       - CORE_PEER_ID=peer2
-      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0:7051
+      - CORE_PEER_GOSSIP_BOOTSTRAP=peer2:7051
       - CORE_PEER_LOCALMSPID=Org1MSP
     volumes:
         - /var/run/:/host/var/run/
@@ -82,7 +82,7 @@ services:
       service: peer-base
     environment:
       - CORE_PEER_ID=peer3
-      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0:7051
+      - CORE_PEER_GOSSIP_BOOTSTRAP=peer2:7051
       - CORE_PEER_LOCALMSPID=Org1MSP
     volumes:
         - /var/run/:/host/var/run/

diff --git a/examples/e2e_cli/docker-compose.yaml b/examples/e2e_cli/docker-compose.yaml
@@ -154,7 +154,7 @@ services:
       - CORE_PEER_ID=peer3
       - CORE_PEER_ADDRESS=peer3:7051
       - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer3:7051
-      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0:7051
+      - CORE_PEER_GOSSIP_BOOTSTRAP=peer2:7051
       - CORE_PEER_LOCALMSPID=Org1MSP
       - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/msp/sampleconfig/signcerts/peer3Signer.pem
       - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/msp/sampleconfig/keystore/peer3Signer.pem