docker - Hyperledger Fabric docker 组成CORE_PEER_GOSSIP_BOOTSTRAP

Question

我有一些组织有2个以上的同行。当我编辑docker-compose-base.yaml时，我不确定如何定义CORE_PEER_GOSSIP_BOOTSTRAP。以下是我的操作，但日志显示对等方无法连接到八卦对等方。正确的方法是什么？先感谢您!

docker-compose-base.yaml

peer0.caseManager.snts.com:
    container_name: peer0.caseManager.snts.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.caseManager.snts.com
      - CORE_PEER_ADDRESS=peer0.caseManager.snts.com:7051
      - CORE_PEER_GOSSIP_BOOTSTRAP=[peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051]
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.caseManager.snts.com:7051
      - CORE_PEER_LOCALMSPID=CaseManagerMSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/tls:/etc/hyperledger/fabric/tls
        - peer0.caseManager.snts.com:/var/hyperledger/production
    ports:
      - 9051:7051
      - 9053:7053

“docker-compose -p docker-compose.yaml up”的 日志

peer0.caseManager.snts.com    | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 023 Could not connect to {peer2.caseManager.snts.com:7051] [] [] peer2.caseManager.snts.com:7051] <nil> <nil>} : context deadline exceeded
peer0.caseManager.snts.com    | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 024 Could not connect to {[peer1.caseManager.snts.com:7051 [] [] [peer1.caseManager.snts.com:7051 <nil> <nil>} : context deadline exceeded

Answer 1

从对等方的 Angular 来看，Bootstrap对等方是同一组织的另一个对等方，在引导过程中，Bootstrap对等方可以联系到该对等方，并获取一些必要的信息以使通信得以进行。 (see here)

您的设置看起来正确，完全有理由认为您的Peer0比Peer1和Peer2更早启动，并且在启动过程中找不到它们，但这并不罕见。您最终有任何错误吗？如果不是，这看起来像正常操作。