我正在尝试在多台机器上部署hyperledger fabric(v1.4.3)单独模式,role-ip映射如下:
orderer 192.168.1.251
peer0.org1 192.168.1.249
peer0.org2 192.168.1.248
peer1.org1 192.168.1.247
peer1.org2 192.168.1.246
我将fabric-samples/first-network
复制到first
,并删除一些文件,first
文件夹包含:
├── base
│ ├── docker-compose-base.yaml
│ └── peer-base.yaml
├── channel-artifacts
├── configtx.yaml
├── crypto-config.yaml
├── docker-compose-cli.yaml
byfn.sh
我保持crypto-config.yaml
和configtx.yaml
与fabric-samples
相同,只是更改docker-compose-cli.yaml
。
orderer
的docker-compose-cli.yaml
:
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
volumes:
orderer.example.com:
networks:
byfn:
services:
orderer.example.com:
extends:
file: base/docker-compose-base.yaml
service: orderer.example.com
container_name: orderer.example.com
networks:
- byfn
peer0.org1
的docker-compose-cli.yaml
:
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
volumes:
peer0.org1.example.com:
networks:
byfn:
services:
peer0.org1.example.com:
container_name: peer0.org1.example.com
extends:
file: base/docker-compose-base.yaml
service: peer0.org1.example.com
networks:
- byfn
extra_hosts:
- "orderer.example.com:192.168.1.251"
- "peer1.org1.example.com:192.168.1.247"
- "peer0.org2.example.com:192.168.1.248"
- "peer1.org2.example.com:192.168.1.246"
cli:
container_name: cli
image: hyperledger/fabric-tools:$IMAGE_TAG
tty: true
stdin_open: true
environment:
- SYS_CHANNEL=$SYS_CHANNEL
- GOPATH=/opt/gopath
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
- FABRIC_LOGGING_SPEC=DEBUG
#- FABRIC_LOGGING_SPEC=INFO
- CORE_PEER_ID=cli
- CORE_PEER_ADDRESS=peer0.org1.example.com:7051 # change in different peer
- CORE_PEER_LOCALMSPID=Org1MSP # change in different peer
- CORE_PEER_TLS_ENABLED=true
- CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt # change in different peer and org
- CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key # change in different peer and org
- CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt # change in different peer and org
- CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp # change in different org
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: /bin/bash
volumes:
- /var/run/:/host/var/run/
- ./../chaincode/:/opt/gopath/src/github.com/chaincode
- ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
- ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
- ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
depends_on:
- peer0.org1.example.com
networks:
- byfn
extra_hosts:
- "orderer.example.com:192.168.1.251"
- "peer0.org1.example.com:192.168.1.249"
- "peer1.org1.example.com:192.168.1.247"
- "peer0.org2.example.com:192.168.1.248"
- "peer1.org2.example.com:192.168.1.246"
另一个对等体更改为上述yaml文件中的注释。我使用./byfn.sh generate
在每个对等方和订购者上生成通道工件,然后在peer0.org1(192.168.1.249)cli容器中,我成功安装了链码,但是当我实例化链码时,我看到订购者控制台抛出了错误:
[core.comm] ServerHandshake -> ERRO 009 TLS handshake failed with error remote error: tls: bad certificate server=Orderer remoteaddress=192.168.1.249:58812
而且我注意到同行之间也发生了错误,我已经尝试了几种通过互联网进行的方法,但是都失败了。有人可以帮我吗?也欢迎任何以kafka模式部署Hyperledger Fabric的教程!
最好的问候!
最后,当我创建-channelID mychannel
时,通过删除genesis.block
参数解决了这个问题。我不知道为什么,所以如果有任何建议,请在这里评论。