Hyperledger Fabric 1.4.6网络搭建实例(raft)

近期在帮其他部门搭建fabric测试网络，采用1.4.1的配置文件、1.4.6的核心模块，在创建通道的时候爆出了以下错误：

Error: got unexpected status: BAD_REQUEST -- error validating channel creation transaction for new channel 'mychannel', could not succesfully apply update to template configuration: error authorizing update: error validating DeltaSet: policy for [Group]  /Channel/Application not satisfied: implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Admins' sub-policies to be satisfied 

在网上查询的时候，很多帖子说是历史数据没有清理干净，但是我可以保证我的历史数据绝对是清理干净了。
但是，当我把bin目录下的核心模块换回1.4.1时，就没有这个问题，因此，错误的原因可以确定为版本问题，即1.4.6修改了某些功能和策略.
于是开始研读fabric1.4.1之后的版本文档，发现在1.4.3的时候进行了以下更新

可以确定，在configtx.yaml文件的Capabilities模块的配置发生了变化，而Capabilities功能模块定义了fabric二进制核心模块必须提供的特性。

经过修改，搭建起fabric1.4.6区块链网络实例，此实例采用raft共识机制。

本实例采用java chaincode ，从本地加载依赖。部署过程没有做特别详细的说明，建议有一定fabric基础的同学食用，基础较薄弱的同学可百度博客园博主灵龙，他写的fabric入门博客十分详细，可读性很高。

由于家境贫寒，笔记本内存只有8G，所以只有三台虚拟机，部署策略如下：

192.168.43.167  orderer0 peer0org1 peer1org2 192.168.43.91  orderer1 peer1org1 192.168.43.241  orderer2 peer0org2 

配置文件

各虚拟机配置文件如下：

192.168.43.167

configtx.yaml

# Copyright IBM Corp. All Rights Reserved. # # SPDX-License-Identifier: Apache-2.0 #  --- ################################################################################ # #   Section: Organizations # #   - This section defines the different organizational identities which will #   be referenced later in the configuration. # ################################################################################ Organizations:      # SampleOrg defines an MSP using the sampleconfig.  It should never be used     # in production but may be used as a template for other definitions     - &OrdererOrg         # DefaultOrg defines the organization which is used in the sampleconfig         # of the fabric.git development environment         Name: OrdererOrg          # ID to load the MSP definition as         ID: OrdererMSP          # MSPDir is the filesystem path which contains the MSP configuration         MSPDir: crypto-config/ordererOrganizations/example.com/msp          # Policies defines the set of policies at this level of the config tree         # For organization policies, their canonical path is usually         #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>         Policies:             Readers:                 Type: Signature                 Rule: "OR('OrdererMSP.member')"             Writers:                 Type: Signature                 Rule: "OR('OrdererMSP.member')"             Admins:                 Type: Signature                 Rule: "OR('OrdererMSP.admin')"      - &Org1         # DefaultOrg defines the organization which is used in the sampleconfig         # of the fabric.git development environment         Name: Org1MSP          # ID to load the MSP definition as         ID: Org1MSP          MSPDir: crypto-config/peerOrganizations/org1.example.com/msp          # Policies defines the set of policies at this level of the config tree         # For organization policies, their canonical path is usually         #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>         Policies:             Readers:                 Type: Signature                 Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"             Writers:                 Type: Signature                 Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"             Admins:                 Type: Signature                 Rule: "OR('Org1MSP.admin')"          # leave this flag set to true.         AnchorPeers:             # AnchorPeers defines the location of peers which can be used             # for cross org gossip communication.  Note, this value is only             # encoded in the genesis block in the Application section context             - Host: peer0.org1.example.com               Port: 7051      - &Org2         # DefaultOrg defines the organization which is used in the sampleconfig         # of the fabric.git development environment         Name: Org2MSP          # ID to load the MSP definition as         ID: Org2MSP          MSPDir: crypto-config/peerOrganizations/org2.example.com/msp          # Policies defines the set of policies at this level of the config tree         # For organization policies, their canonical path is usually         #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>         Policies:             Readers:                 Type: Signature                 Rule: "OR('Org2MSP.admin', 'Org2MSP.peer', 'Org2MSP.client')"             Writers:                 Type: Signature                 Rule: "OR('Org2MSP.admin', 'Org2MSP.client')"             Admins:                 Type: Signature                 Rule: "OR('Org2MSP.admin')"          AnchorPeers:             # AnchorPeers defines the location of peers which can be used             # for cross org gossip communication.  Note, this value is only             # encoded in the genesis block in the Application section context             - Host: peer0.org2.example.com               Port: 7051  ################################################################################ # #   SECTION: Capabilities # #   - This section defines the capabilities of fabric network. This is a new #   concept as of v1.1.0 and should not be utilized in mixed networks with #   v1.0.x peers and orderers.  Capabilities define features which must be #   present in a fabric binary for that binary to safely participate in the #   fabric network.  For instance, if a new MSP type is added, newer binaries #   might recognize and validate the signatures from this type, while older #   binaries without this support would be unable to validate those #   transactions.  This could lead to different versions of the fabric binaries #   having different world states.  Instead, defining a capability for a channel #   informs those binaries without this capability that they must cease #   processing transactions until they have been upgraded.  For v1.0.x if any #   capabilities are defined (including a map with all capabilities turned off) #   then the v1.0.x peer will deliberately crash. # ################################################################################ Capabilities:     # Channel capabilities apply to both the orderers and the peers and must be     # supported by both.     # Set the value of the capability to true to require it.     Channel: &ChannelCapabilities         # V1.4.3 for Channel is a catchall flag for behavior which has been         # determined to be desired for all orderers and peers running at the v1.4.3         # level, but which would be incompatible with orderers and peers from         # prior releases.         # Prior to enabling V1.4.3 channel capabilities, ensure that all         # orderers and peers on a channel are at v1.4.3 or later.         V1_4_3: true         # V1.3 for Channel enables the new non-backwards compatible         # features and fixes of fabric v1.3         V1_3: false         # V1.1 for Channel enables the new non-backwards compatible         # features and fixes of fabric v1.1         V1_1: false      # Orderer capabilities apply only to the orderers, and may be safely     # used with prior release peers.     # Set the value of the capability to true to require it.     Orderer: &OrdererCapabilities         # V1.4.2 for Orderer is a catchall flag for behavior which has been         # determined to be desired for all orderers running at the v1.4.2         # level, but which would be incompatible with orderers from prior releases.         # Prior to enabling V1.4.2 orderer capabilities, ensure that all         # orderers on a channel are at v1.4.2 or later.         V1_4_2: true         # V1.1 for Orderer enables the new non-backwards compatible         # features and fixes of fabric v1.1         V1_1: false      # Application capabilities apply only to the peer network, and may be safely     # used with prior release orderers.     # Set the value of the capability to true to require it.     Application: &ApplicationCapabilities         # V1.4.2 for Application enables the new non-backwards compatible         # features and fixes of fabric v1.4.2.         V1_4_2: true         # V1.3 for Application enables the new non-backwards compatible         # features and fixes of fabric v1.3.         V1_3: false         # V1.2 for Application enables the new non-backwards compatible         # features and fixes of fabric v1.2 (note, this need not be set if         # later version capabilities are set)         V1_2: false         # V1.1 for Application enables the new non-backwards compatible         # features and fixes of fabric v1.1 (note, this need not be set if         # later version capabilities are set).         V1_1: false  ################################################################################ # #   SECTION: Application # #   - This section defines the values to encode into a config transaction or #   genesis block for application related parameters # ################################################################################ Application: &ApplicationDefaults      # Organizations is the list of orgs which are defined as participants on     # the application side of the network     Organizations:      # Policies defines the set of policies at this level of the config tree     # For Application policies, their canonical path is     #   /Channel/Application/<PolicyName>     Policies:         Readers:             Type: ImplicitMeta             Rule: "ANY Readers"         Writers:             Type: ImplicitMeta             Rule: "ANY Writers"         Admins:             Type: ImplicitMeta             Rule: "MAJORITY Admins"      Capabilities:         <<: *ApplicationCapabilities ################################################################################ # #   SECTION: Orderer # #   - This section defines the values to encode into a config transaction or #   genesis block for orderer related parameters # ################################################################################ Orderer: &OrdererDefaults      # Orderer Type: The orderer implementation to start     # Available types are "solo","kafka"  and "etcdraft"     OrdererType: solo      Addresses:         - orderer0.example.com:7050      # Batch Timeout: The amount of time to wait before creating a batch     BatchTimeout: 2s      # Batch Size: Controls the number of messages batched into a block     BatchSize:          # Max Message Count: The maximum number of messages to permit in a batch         MaxMessageCount: 10          # Absolute Max Bytes: The absolute maximum number of bytes allowed for         # the serialized messages in a batch.         AbsoluteMaxBytes: 99 MB          # Preferred Max Bytes: The preferred maximum number of bytes allowed for         # the serialized messages in a batch. A message larger than the preferred         # max bytes will result in a batch larger than preferred max bytes.         PreferredMaxBytes: 512 KB      Kafka:         # Brokers: A list of Kafka brokers to which the orderer connects         # NOTE: Use IP:port notation         Brokers:             - 127.0.0.1:9092      # EtcdRaft defines configuration which must be set when the "etcdraft"     # orderertype is chosen.     EtcdRaft:         # The set of Raft replicas for this network. For the etcd/raft-based         # implementation, we expect every replica to also be an OSN. Therefore,         # a subset of the host:port items enumerated in this list should be         # replicated under the Orderer.Addresses key above.         Consenters:             - Host: orderer0.example.com               Port: 7050               ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/server.crt               ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/server.crt             - Host: orderer1.example.com               Port: 7050               ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/server.crt               ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/server.crt             - Host: orderer2.example.com               Port: 7050               ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/server.crt               ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/server.crt             #- Host: orderer3.example.com               #Port: 7050               #ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer4.example.com/tls/server.crt               #ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer4.example.com/tls/server.crt             #- Host: orderer4.example.com               #Port: 7050               #ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer5.example.com/tls/server.crt               #ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer5.example.com/tls/server.crt      # Organizations is the list of orgs which are defined as participants on     # the orderer side of the network     Organizations:      # Policies defines the set of policies at this level of the config tree     # For Orderer policies, their canonical path is     #   /Channel/Orderer/<PolicyName>     Policies:         Readers:             Type: ImplicitMeta             Rule: "ANY Readers"         Writers:             Type: ImplicitMeta             Rule: "ANY Writers"         Admins:             Type: ImplicitMeta             Rule: "MAJORITY Admins"         # BlockValidation specifies what signatures must be included in the block         # from the orderer for the peer to validate it.         BlockValidation:             Type: ImplicitMeta             Rule: "ANY Writers"  ################################################################################ # #   CHANNEL # #   This section defines the values to encode into a config transaction or #   genesis block for channel related parameters. # ################################################################################ Channel: &ChannelDefaults     # Policies defines the set of policies at this level of the config tree     # For Channel policies, their canonical path is     #   /Channel/<PolicyName>     Policies:         # Who may invoke the 'Deliver' API         Readers:             Type: ImplicitMeta             Rule: "ANY Readers"         # Who may invoke the 'Broadcast' API         Writers:             Type: ImplicitMeta             Rule: "ANY Writers"         # By default, who may modify elements at this config level         Admins:             Type: ImplicitMeta             Rule: "MAJORITY Admins"      # Capabilities describes the channel level capabilities, see the     # dedicated Capabilities section elsewhere in this file for a full     # description     Capabilities:         <<: *ChannelCapabilities  ################################################################################ # #   Profile # #   - Different configuration profiles may be encoded here to be specified #   as parameters to the configtxgen tool # ################################################################################ Profiles:      TwoOrgsOrdererGenesis:         <<: *ChannelDefaults         Orderer:             <<: *OrdererDefaults             Organizations:                 - *OrdererOrg             Capabilities:                 <<: *OrdererCapabilities         Consortiums:             SampleConsortium:                 Organizations:                     - *Org1                     - *Org2     TwoOrgsChannel:         Consortium: SampleConsortium         <<: *ChannelDefaults         Application:             <<: *ApplicationDefaults             Organizations:                 - *Org1                 - *Org2             Capabilities:                 <<: *ApplicationCapabilities      SampleDevModeKafka:         <<: *ChannelDefaults         Capabilities:             <<: *ChannelCapabilities         Orderer:             <<: *OrdererDefaults             OrdererType: kafka             Kafka:                 Brokers:                 - kafka.example.com:9092              Organizations:             - *OrdererOrg             Capabilities:                 <<: *OrdererCapabilities         Application:             <<: *ApplicationDefaults             Organizations:             - <<: *OrdererOrg         Consortiums:             SampleConsortium:                 Organizations:                 - *Org1                 - *Org2      SampleMultiNodeEtcdRaft:         <<: *ChannelDefaults         Capabilities:             <<: *ChannelCapabilities         Orderer:             <<: *OrdererDefaults             OrdererType: etcdraft             EtcdRaft:                 Consenters:                 - Host: orderer0.example.com                   Port: 7050                   ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/server.crt                   ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/server.crt                 - Host: orderer1.example.com                   Port: 7050                   ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/server.crt                   ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/server.crt                 - Host: orderer2.example.com                   Port: 7050                   ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/server.crt                   ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/server.crt                 #- Host: orderer3.example.com                   #Port: 7050                   #ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer3.example.com/tls/server.crt                   #ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer3.example.com/tls/server.crt                 #- Host: orderer4.example.com                   #Port: 7050                   #ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer4.example.com/tls/server.crt                   #ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer4.example.com/tls/server.crt             Addresses:                 - orderer0.example.com:7050                 - orderer1.example.com:7050                 - orderer2.example.com:7050                 #- orderer3.example.com:7050                 #- orderer4.example.com:7050              Organizations:             - *OrdererOrg             Capabilities:                 <<: *OrdererCapabilities         Application:             <<: *ApplicationDefaults             Organizations:             - <<: *OrdererOrg         Consortiums:             SampleConsortium:                 Organizations:                 - *Org1                 - *Org2 

crypto-config.yaml

# Copyright IBM Corp. All Rights Reserved. # # SPDX-License-Identifier: Apache-2.0 #  # --------------------------------------------------------------------------- # "OrdererOrgs" - Definition of organizations managing orderer nodes # --------------------------------------------------------------------------- OrdererOrgs:   # ---------------------------------------------------------------------------   # Orderer   # ---------------------------------------------------------------------------   - Name: Orderer     Domain: example.com     EnableNodeOUs: true     # ---------------------------------------------------------------------------     # "Specs" - See PeerOrgs below for complete description     # ---------------------------------------------------------------------------     Specs:       - Hostname: orderer0       - Hostname: orderer1       - Hostname: orderer2       #- Hostname: orderer3       #- Hostname: orderer4  # --------------------------------------------------------------------------- # "PeerOrgs" - Definition of organizations managing peer nodes # --------------------------------------------------------------------------- PeerOrgs:   # ---------------------------------------------------------------------------   # Org1   # ---------------------------------------------------------------------------   - Name: Org1     Domain: org1.example.com     EnableNodeOUs: true     # ---------------------------------------------------------------------------     # "Specs"     # ---------------------------------------------------------------------------     # Uncomment this section to enable the explicit definition of hosts in your     # configuration.  Most users will want to use Template, below     #     # Specs is an array of Spec entries.  Each Spec entry consists of two fields:     #   - Hostname:   (Required) The desired hostname, sans the domain.     #   - CommonName: (Optional) Specifies the template or explicit override for     #                 the CN.  By default, this is the template:     #     #                              "{{.Hostname}}.{{.Domain}}"     #     #                 which obtains its values from the Spec.Hostname and     #                 Org.Domain, respectively.     # ---------------------------------------------------------------------------     # Specs:     #   - Hostname: foo # implicitly "foo.org1.example.com"     #     CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above     #   - Hostname: bar     #   - Hostname: baz     # ---------------------------------------------------------------------------     # "Template"     # ---------------------------------------------------------------------------     # Allows for the definition of 1 or more hosts that are created sequentially     # from a template. By default, this looks like "peer%d" from 0 to Count-1.     # You may override the number of nodes (Count), the starting index (Start)     # or the template used to construct the name (Hostname).     #     # Note: Template and Specs are not mutually exclusive.  You may define both     # sections and the aggregate nodes will be created for you.  Take care with     # name collisions     # ---------------------------------------------------------------------------     Template:       Count: 2       # Start: 5       # Hostname: {{.Prefix}}{{.Index}} # default     # ---------------------------------------------------------------------------     # "Users"     # ---------------------------------------------------------------------------     # Count: The number of user accounts _in addition_ to Admin     # ---------------------------------------------------------------------------     Users:       Count: 1   # ---------------------------------------------------------------------------   # Org2: See "Org1" for full specification   # ---------------------------------------------------------------------------   - Name: Org2     Domain: org2.example.com     EnableNodeOUs: true     Template:       Count: 2     Users:       Count: 1 

orderer0.yaml

version: '2'  services:   orderer0.example.com:     container_name: orderer0.example.com     image: hyperledger/fabric-orderer     environment:       - FABRIC_LOGGING_SPEC=INFO       - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0       - ORDERER_GENERAL_GENESISMETHOD=file       - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block       - ORDERER_GENERAL_LOCALMSPID=OrdererMSP       - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp       # enabled TLS       - ORDERER_GENERAL_TLS_ENABLED=true       - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]       - ORDERER_KAFKA_TOPIC_REPLICATIONFACTOR=1       - ORDERER_KAFKA_VERBOSE=true       - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]     working_dir: /opt/gopath/src/github.com/hyperledger/fabric     command: orderer     volumes:         - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/var/hyperledger/orderer/msp         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/var/hyperledger/orderer/tls     ports:       - 7050:7050     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241" 

peer0org1.yaml

version: '2'  services:   couchdb0:     image: hyperledger/fabric-couchdb     container_name: couchdb0     environment:       - COUCHDB_USER=admin       - COUCHDB_PASSWORD=123456     ports:       - 5984:5984          peer0.org1.example.com:     image: hyperledger/fabric-peer     container_name: peer0.org1.example.com     environment:       - CORE_PEER_ID=peer0.org1.example.com       - CORE_PEER_ADDRESS=peer0.org1.example.com:7051       - CORE_PEER_LISTENADDRESS=0.0.0.0:7051       - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052       - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052       #- CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.example.com:8051       - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051       - CORE_PEER_LOCALMSPID=Org1MSP       - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock       # the following setting starts chaincode containers on the same       # bridge network as the peers       # https://docs.docker.com/compose/networking/       - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=raft-cluster_default       - FABRIC_LOGGING_SPEC=INFO       #- FABRIC_LOGGING_SPEC=DEBUG       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_GOSSIP_USELEADERELECTION=true       - CORE_PEER_GOSSIP_ORGLEADER=false       - CORE_PEER_PROFILE_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt       - CORE_LEDGER_STATE_STATEDATABASE=CouchDB       - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984       # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD       # provide the credentials for ledger to connect to CouchDB.  The username and password must       # match the username and password set for the associated CouchDB.       - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin       - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=123456     depends_on:       - couchdb0     volumes:         - /var/run/:/host/var/run/         - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp         - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls     ports:       - 7051:7051       - 7052:7052       - 7053:7053     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"           cli0:     container_name: cli0     image: hyperledger/fabric-tools     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=cli0       - CORE_PEER_ADDRESS=peer0.org1.example.com:7051       - CORE_PEER_LOCALMSPID=Org1MSP       - 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       - 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       - 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       - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp     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/         - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts         - ./peer:/opt/gopath/src/github.com/hyperledger/fabric/peer/     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"       #- "peer0.org1.richfit.com:11.11.54.172"       - "peer1.org1.example.com:192.168.43.91"       - "peer0.org2.example.com:192.168.43.241"       #- "peer1.org2.richfit.com:11.11.54.172" 

peer1org2.yaml

version: '2'  services:   couchdb3:     container_name: couchdb3     image: hyperledger/fabric-couchdb     # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password     # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.     environment:       - COUCHDB_USER=admin       - COUCHDB_PASSWORD=123456     # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,     # for example map it to utilize Fauxton User Interface in dev environments.     ports:       - 6984:5984          peer1.org2.example.com:     container_name: peer1.org2.example.com     image: hyperledger/fabric-peer     environment:       - CORE_PEER_ID=peer1.org2.example.com       - CORE_PEER_ADDRESS=peer1.org2.example.com:8051       - CORE_PEER_LISTENADDRESS=0.0.0.0:8051       - CORE_PEER_CHAINCODEADDRESS=peer1.org2.example.com:8052       - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:8052       - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:8051       #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.example.com:7051       - CORE_PEER_LOCALMSPID=Org2MSP       - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock       # the following setting starts chaincode containers on the same       # bridge network as the peers       # https://docs.docker.com/compose/networking/       - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=raft-cluster_default       - FABRIC_LOGGING_SPEC=INFO       #- FABRIC_LOGGING_SPEC=DEBUG       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_GOSSIP_USELEADERELECTION=true       - CORE_PEER_GOSSIP_ORGLEADER=false       - CORE_PEER_PROFILE_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt       - CORE_LEDGER_STATE_STATEDATABASE=CouchDB       - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb3:5984       # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD       # provide the credentials for ledger to connect to CouchDB.  The username and password must       # match the username and password set for the associated CouchDB.       - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin       - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=123456     depends_on:       - couchdb3     volumes:         - /var/run/:/host/var/run/         - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/msp:/etc/hyperledger/fabric/msp         - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls:/etc/hyperledger/fabric/tls     ports:       - 8051:7051       - 8052:7052       - 8053:7053     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.richfit.com:192.168.43.91"       - "orderer2.richfit.com:192.168.43.241"           cli1:     container_name: cli1     image: hyperledger/fabric-tools     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=cli1       - CORE_PEER_ADDRESS=peer1.org2.example.com:8051       - CORE_PEER_LOCALMSPID=Org2MSP       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt       - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp     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/         - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts         - ./peer:/opt/gopath/src/github.com/hyperledger/fabric/peer/     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"       #- "peer0.org1.richfit.com:11.11.54.172"       - "peer1.org1.example.com:192.168.43.91"       - "peer0.org2.example.com:192.168.43.241"       #- "peer1.org2.richfit.com:11.11.54.172"  

192.168.43.91

orderer1.yaml

version: '2'  services:   orderer1.example.com:     container_name: orderer1.example.com     image: hyperledger/fabric-orderer     environment:       - FABRIC_LOGGING_SPEC=INFO       - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0       - ORDERER_GENERAL_GENESISMETHOD=file       - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block       - ORDERER_GENERAL_LOCALMSPID=OrdererMSP       - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp       # enabled TLS       - ORDERER_GENERAL_TLS_ENABLED=true       - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]       - ORDERER_KAFKA_TOPIC_REPLICATIONFACTOR=1       - ORDERER_KAFKA_VERBOSE=true       - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]     working_dir: /opt/gopath/src/github.com/hyperledger/fabric     command: orderer     volumes:         - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/msp:/var/hyperledger/orderer/msp         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/:/var/hyperledger/orderer/tls     ports:       - 7050:7050     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"  

peer1org1.yaml

version: '2'  services:   couchdb1:     container_name: couchdb1     image: hyperledger/fabric-couchdb     # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password     # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.     environment:       - COUCHDB_USER=admin       - COUCHDB_PASSWORD=123456     # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,     # for example map it to utilize Fauxton User Interface in dev environments.     ports:       - 5984:5984          peer1.org1.example.com:     container_name: peer1.org1.example.com     image: hyperledger/fabric-peer     environment:       - CORE_PEER_ID=peer1.org1.example.com       - CORE_PEER_ADDRESS=peer1.org1.example.com:7051       - CORE_PEER_LISTENADDRESS=0.0.0.0:7051       - CORE_PEER_CHAINCODEADDRESS=peer1.org1.example.com:7052       - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052       - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051       #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051       - CORE_PEER_LOCALMSPID=Org1MSP       - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock       # the following setting starts chaincode containers on the same       # bridge network as the peers       # https://docs.docker.com/compose/networking/       - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=raft-cluster_default       - FABRIC_LOGGING_SPEC=INFO       #- FABRIC_LOGGING_SPEC=DEBUG       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_GOSSIP_USELEADERELECTION=true       - CORE_PEER_GOSSIP_ORGLEADER=false       - CORE_PEER_PROFILE_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt       - CORE_LEDGER_STATE_STATEDATABASE=CouchDB       - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb1:5984       # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD       # provide the credentials for ledger to connect to CouchDB.  The username and password must       # match the username and password set for the associated CouchDB.       - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin       - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=123456     depends_on:       - couchdb1     volumes:         - /var/run/:/host/var/run/         - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/fabric/msp         - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/etc/hyperledger/fabric/tls     ports:       - 7051:7051       - 7052:7052       - 7053:7053     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"          cli1:     container_name: cli1     image: hyperledger/fabric-tools     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=cli1       - CORE_PEER_ADDRESS=peer1.org1.example.com:7051       - CORE_PEER_LOCALMSPID=Org1MSP       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt       - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp     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/         - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts         - ./peer:/opt/gopath/src/github.com/hyperledger/fabric/peer/     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"       - "peer0.org1.example.com:192.168.43.167"       - "peer1.org1.example.com:192.168.43.91"       - "peer0.org2.example.com:192.168.43.241"       - "peer1.org2.example.com:192.168.43.167"  

192.168.43.241

orderer2.yaml

version: '2'  services:   orderer2.example.com:     container_name: orderer2.example.com     image: hyperledger/fabric-orderer     environment:       - FABRIC_LOGGING_SPEC=INFO       - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0       - ORDERER_GENERAL_GENESISMETHOD=file       - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block       - ORDERER_GENERAL_LOCALMSPID=OrdererMSP       - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp       # enabled TLS       - ORDERER_GENERAL_TLS_ENABLED=true       - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]       - ORDERER_KAFKA_TOPIC_REPLICATIONFACTOR=1       - ORDERER_KAFKA_VERBOSE=true       - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt       - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key       - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]     working_dir: /opt/gopath/src/github.com/hyperledger/fabric     command: orderer     volumes:         - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/msp:/var/hyperledger/orderer/msp         - ./crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/:/var/hyperledger/orderer/tls     ports:       - 7050:7050     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241" 

peer0org2.yaml

version: '2'  services:   couchdb2:     container_name: couchdb2     image: hyperledger/fabric-couchdb     # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password     # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.     environment:       - COUCHDB_USER=admin       - COUCHDB_PASSWORD=123456     # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,     # for example map it to utilize Fauxton User Interface in dev environments.     ports:       - 5984:5984          peer0.org2.example.com:     container_name: peer0.org2.example.com     image: hyperledger/fabric-peer     environment:       - CORE_PEER_ID=peer0.org2.example.com       - CORE_PEER_ADDRESS=peer0.org2.example.com:7051       - CORE_PEER_LISTENADDRESS=0.0.0.0:7051       - CORE_PEER_CHAINCODEADDRESS=peer0.org2.example.com:7052       - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052       - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051       #- CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.example.com:8051       - CORE_PEER_LOCALMSPID=Org2MSP       - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock       # the following setting starts chaincode containers on the same       # bridge network as the peers       # https://docs.docker.com/compose/networking/       - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=raft-cluster_default       - FABRIC_LOGGING_SPEC=INFO       #- FABRIC_LOGGING_SPEC=DEBUG       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_GOSSIP_USELEADERELECTION=true       - CORE_PEER_GOSSIP_ORGLEADER=false       - CORE_PEER_PROFILE_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt       - CORE_LEDGER_STATE_STATEDATABASE=CouchDB       - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb2:5984       # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD       # provide the credentials for ledger to connect to CouchDB.  The username and password must       # match the username and password set for the associated CouchDB.       - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin       - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=123456     depends_on:       - couchdb2     volumes:         - /var/run/:/host/var/run/         - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp         - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls     ports:       - 7051:7051       - 7052:7052       - 7053:7053     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"          cli0:     container_name: cli0     image: hyperledger/fabric-tools     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=cli0       - CORE_PEER_ADDRESS=peer0.org2.example.com:7051       - CORE_PEER_LOCALMSPID=Org2MSP       - CORE_PEER_TLS_ENABLED=true       - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.crt       - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.key       - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt       - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp     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/         - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts         - ./peer:/opt/gopath/src/github.com/hyperledger/fabric/peer/     extra_hosts:       - "orderer0.example.com:192.168.43.167"       - "orderer1.example.com:192.168.43.91"       - "orderer2.example.com:192.168.43.241"       - "peer0.org1.example.com:192.168.43.167"       - "peer1.org1.example.com:192.168.43.91"       - "peer0.org2.example.com:192.168.43.241"       - "peer1.org2.example.com:192.168.43.167" 

部署文档

//清理环境 docker stop $(docker ps -aq)  docker rm $(docker ps -aq)  rm -rf channel-artifacts/  rm -rf crypto-config  sudo rm -rf peer/  //生成证书、通道配置文件、创世区块等 ./bin/cryptogen generate --config=./crypto-config.yaml  mkdir channel-artifacts ./bin/configtxgen -profile SampleMultiNodeEtcdRaft -outputBlock ./channel-artifacts/genesis.block  ./bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel  //crypto-config和channel-artifacts两个目录拷贝到其他节点 scp -r ./crypto-config/ hao@192.168.43.91:/home/hao/Desktop/fabric/raft-cluster scp -r ./channel-artifacts/ hao@192.168.43.91:/home/hao/Desktop/fabric/raft-cluster  scp -r ./crypto-config/ hao@192.168.43.241:/home/hao/Desktop/fabric/raft-cluster scp -r ./channel-artifacts/ hao@192.168.43.241:/home/hao/Desktop/fabric/raft-cluster   //启动orderer节点 docker-compose -f orderer0.yaml up -d  docker-compose -f orderer1.yaml up -d  docker-compose -f orderer2.yaml up -d   //启动peer0org1 docker-compose -f peer0org1.yaml up -d  docker exec -it cli0 bash  //创建通道 ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem peer channel create -o orderer0.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx --tls --cafile $ORDERER_CA  //节点加入通道 peer channel join -b mychannel.block  //安装智能合约 peer chaincode install -n mycc -p /opt/gopath/src/github.com/chaincode/java/DCChainCode -l java -v 1.0  //实例化是能合约 ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem peer chaincode instantiate -o orderer0.example.com:7050 --tls --cafile $ORDERER_CA -C mychannel -l java -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR ('Org1MSP.peer','Org2MSP.peer')"  //查询 peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'   //交易 ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem peer chaincode invoke --tls --cafile $ORDERER_CA -C mychannel -n mycc -c '{"Args":["invoke","a","b","20"]}'  //启动peer1org1节点 docker-compose -f peer1org1.yaml up -d  //将peer0org1生成的通道配置区块发送到peer1org1节点 scp -r ./mychannel.block hao@192.168.43.91:/home/hao/Desktop/fabric/raft-cluster/  sudo mv ./mychannel.block ./peer  //重新启动peer1org1节点 docker-compose -f peer1org1.yaml up -d  docker exec -it cli1 bash  //节点加入通道 peer channel join -b mychannel.block  //节点安装链码 peer chaincode install -n mycc -p /opt/gopath/src/github.com/chaincode/java/DCChainCode -l java -v 1.0  //启动peer0org2节点 docker-compose -f peer0org2.yaml up -d   //将peer0org1生成的通道配置区块发送到peer0org2节点 scp -r ./mychannel.block hao@192.168.43.241:/home/hao/Desktop/fabric/raft-cluster/  sudo mv ./mychannel.block ./peer  //重启peer0org2节点 docker-compose -f peer0org2.yaml up -d  docker exec -it cli0 bash  //节点加入通道 peer channel join -b mychannel.block  //节点安装智能合约 peer chaincode install -n mycc -p /opt/gopath/src/github.com/chaincode/java/DCChainCode -l java -v 1.0   //启动peer1org2 docker-compose -f peer1org2.yaml up -d  docker exec -it cli1 bash  peer channel join -b mychannel.block  peer chaincode install -n mycc -p /opt/gopath/src/github.com/chaincode/java/DCChainCode -l java -v 1.0  

最后，如果在部署的过程中出现问题，欢迎在本博客下留言或私信。