Hyperledger Fabric 2.2.1 多机部署教程

最新推荐文章于 2024-07-09 23:00:09 发布
最新推荐文章于 2024-07-09 23:00:09 发布
阅读量776 收藏 5
点赞数
文章标签： fabric docker 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_62778805/article/details/128612210
版权

一、搭建环境

1、系统环境

Ubuntu 22.04 LTS

2、设置网络
root@orderer:~# vi /etc/hosts
192.168.0.209 orderer.example.com
192.168.0.237 peer0.org1.example.com
192.168.0.35 peer0.org2.example.com
192.168.0.148 peer0.org3.example.com
3、安装docker和docker-compose
root@orderer:~# apt update
root@orderer:~# apt -y install apt-transport-https ca-certificates curl software-properties-common
root@orderer:~# curl -fsSL https://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
root@orderer:~# add-apt-repository "deb [arch=amd64] https://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
root@orderer:~# apt -y update
root@orderer:~# apt -y install docker-ce
root@orderer:~# service docker start
root@orderer:~# systemctl enable docker
root@orderer:~# curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
root@orderer:~# chmod +x /usr/local/bin/docker-compose
root@orderer:~# docker-compose -v
docker-compose version 1.29.2, build 5becea4c
4、安装Golang环境
root@orderer:~# wget https://golang.google.cn/dl/go1.16.14.linux-amd64.tar.gz
root@orderer:~# tar zxf go1.16.14.linux-amd64.tar.gz
root@orderer:~# mv go /usr/local/
root@orderer:~# vim /etc/profile
export GOPATH=~/Go
export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin
export GO111MODULE=on
export GOPROXY=https://goproxy.cn,direct
root@orderer:~# source /etc/profile
root@orderer:~# go version
go version go1.16.14 linux/amd64

二、生成Fabric证书

1、编写证书文件
root@orderer:~# apt -y install git
root@orderer:~# git clone -b v2.2.1 https://github.com/hyperledger/fabric.git #这里可能中断，请多重复几次
root@orderer:~# cd fabric/scripts/
root@orderer:~/fabric/scripts # /.bootstrap.sh #这里可能中断，请多重复几次
root@orderer:~/fabric/scripts # cp -r fabric-samples/ ~/
root@orderer:~# cp fabric-samples/bin/* /usr/local/bin/
root@orderer:~# vim /etc/profile
export PATH=~/fabric-samples/bin:$PATH
root@orderer:~# source /etc/profile
root@orderer:~# mkdir hyperledger
root@orderer:~# mkdir hyperledger/multinodes/
root@orderer:~# cd hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes# cryptogen showtemplate > crypto-config.yaml
root@orderer:~/hyperledger/multinodes# vim crypto-config.yaml 

OrdererOrgs:

  - Name: Orderer
    Domain: example.com
    EnableNodeOUs: true

    Specs:
      - Hostname: orderer
PeerOrgs:
 
  - Name: org1
    Domain: org1.example.com
    EnableNodeOUs: true
    Template:
      Count: 1
    Users:
      Count: 1
      
  - Name: org2
    Domain: org2.example.com
    EnableNodeOUs: true
    Template:
      Count: 1
    Users:
      Count: 1   

  - Name: org3
    Domain: org3.example.com
    EnableNodeOUs: true
    Template:
      Count: 1
    Users:
      Count: 1
2、生成证书文件
root@orderer:~/hyperledger/multinodes # cryptogen generate --config=crypto-config.yaml
org1.example.com
org2.example.com
org3.example.com
3、复制证书文件到节点
root@org1:~# mkdir hyperledger
root@org1:~# mkdir hyperledger/multinodes/
root@org2:~# mkdir hyperledger
root@org2:~# mkdir hyperledger/multinodes/
root@org3:~# mkdir hyperledger
root@org3:~# mkdir hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes # scp -r ./crypto-config root@192.168.0.237:~/hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes # scp -r ./crypto-config root@192.168.0.35:~/hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes # scp -r ./crypto-config root@192.168.0.148:~/hyperledger/multinodes/

三、生成通道文件

1、编写创世块文件
root@orderer:~/hyperledger/multinodes # vi /configtx.yaml

Organizations:

    - &OrdererOrg

        Name: OrdererOrg
        ID: OrdererMSP
        MSPDir: ./crypto-config/ordererOrganizations/example.com/msp
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('OrdererMSP.admin')"
        OrdererEndpoints:
            - orderer.example.com:7050

    - &Org1
   
        Name: Org1MSP
        ID: Org1MSP
        MSPDir: ./crypto-config/peerOrganizations/org1.example.com/msp
        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')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org1MSP.peer')"
        AnchorPeers:
            - Host: peer0.org1.example.com
              Port: 7051

    - &Org2
    
        Name: Org2MSP
        ID: Org2MSP
        MSPDir: ./crypto-config/peerOrganizations/org2.example.com/msp
        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')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org2MSP.peer')"

        AnchorPeers:
            - Host: peer0.org2.rainpt.com
              Port: 8051

    - &Org3
    
        Name: Org3MSP
        ID: Org3MSP
        MSPDir: ./crypto-config/peerOrganizations/org3.example.com/msp
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('Org3MSP.admin', 'Org3MSP.peer', 'Org3MSP.client')"
            Writers:
                Type: Signature
                Rule: "OR('Org3MSP.admin', 'Org3MSP.client')"
            Admins:
                Type: Signature
                Rule: "OR('Org3MSP.admin')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org3MSP.peer')"

        AnchorPeers:
            - Host: peer0.org3.rainpt.com
              Port: 9051


Capabilities:

    Channel: &ChannelCapabilities

        V2_0: true

    Orderer: &OrdererCapabilities

        V2_0: true

    Application: &ApplicationCapabilities

        V2_0: true

Application: &ApplicationDefaults

    Organizations:

    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        LifecycleEndorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
        Endorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"

    Capabilities:
        <<: *ApplicationCapabilities

Orderer: &OrdererDefaults

    OrdererType: solo 

    Addresses:
        - orderer.example.com:7050

    EtcdRaft:
        Consenters:
        - Host: orderer.example.com
          Port: 7050
          ClientTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
          ServerTLSCert: ../organizations/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt

    BatchTimeout: 2s
    BatchSize:
        MaxMessageCount: 10
        AbsoluteMaxBytes: 99 MB
        PreferredMaxBytes: 512 KB

    Organizations:

    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
      
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"


Channel: &ChannelDefaults

    Policies:
       
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"

    
    Capabilities:
        <<: *ChannelCapabilities

Profiles:

    ThreeOrgsOrdererGenesis:
        <<: *ChannelDefaults
        Orderer:
            <<: *OrdererDefaults
            Organizations:
                - *OrdererOrg
            Capabilities:
                <<: *OrdererCapabilities
        Consortiums:
            SampleConsortium:
                Organizations:
                    - *Org1
                    - *Org2
                    - *Org3
    ThreeOrgsChannel:
        Consortium: SampleConsortium
        <<: *ChannelDefaults
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
                - *Org3
            Capabilities:
                <<: *ApplicationCapabilities
2、生成创世块文件和通道文件
1、生成创世区块
root@orderer:~/hyperledger/multinodes # configtxgen -profile ThreeOrgsOrdererGenesis -channelID fabric-channel -outputBlock ./channel-artifacts/genesis.block

2023-01-07 23:59:46.178 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-01-07 23:59:46.198 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 orderer type: solo
2023-01-07 23:59:46.198 CST [common.tools.configtxgen.localconfig] Load -> INFO 003 Loaded configuration: /root/hyperledger/multinodes/configtx.yaml
2023-01-07 23:59:46.200 CST [common.tools.configtxgen] doOutputBlock -> INFO 004 Generating genesis block
2023-01-07 23:59:46.200 CST [common.tools.configtxgen] doOutputBlock -> INFO 005 Writing genesis block
2、生成通道文件
root@orderer:~/hyperledger/multinodes # configtxgen -profile ThreeOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel

2023-01-08 00:00:03.256 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-01-08 00:00:03.274 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/hyperledger/multinodes/configtx.yaml
2023-01-08 00:00:03.274 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 003 Generating new channel configtx
2023-01-08 00:00:03.277 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 004 Writing new channel tx
3、为Org1定义锚节点
root@orderer:~/hyperledger/multinodes # configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP

2023-01-08 00:00:20.598 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-01-08 00:00:20.617 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/hyperledger/multinodes/configtx.yaml
2023-01-08 00:00:20.617 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Generating anchor peer update
2023-01-08 00:00:20.619 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 004 Writing anchor peer update
4、为Org2定义锚节点
root@orderer:~/hyperledger/multinodes # configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP

2023-01-08 00:00:35.567 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-01-08 00:00:35.586 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/hyperledger/multinodes/configtx.yaml
2023-01-08 00:00:35.586 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Generating anchor peer update
2023-01-08 00:00:35.588 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 004 Writing anchor peer update
5、为Org3定义锚节点
root@orderer:~/hyperledger/multinodes # configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org3MSPanchors.tx -channelID mychannel -asOrg Org3MSP

2023-01-08 00:01:02.890 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2023-01-08 00:01:02.910 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/hyperledger/multinodes/configtx.yaml
2023-01-08 00:01:02.910 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Generating anchor peer update
2023-01-08 00:01:02.912 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 004 Writing anchor peer update
6、将生成的文件拷贝到另外三台机器
root@orderer:~/hyperledger/multinodes # scp -r ./channel-artifacts root@192.168.0.237:~/hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes # scp -r ./channel-artifacts root@192.168.0.35:~/hyperledger/multinodes/
root@orderer:~/hyperledger/multinodes # scp -r ./channel-artifacts root@192.168.0.148:~/hyperledger/multinodes/

四、编写Docker-compose文件

1、orderer节点
root@orderer:~/hyperledger/multinodes # vi docker-compose.yaml

version: '2'

services:
  orderer.example.com:
    container_name: orderer.example.com
    image: hyperledger/fabric-orderer:2.2
    environment:
      - FABRIC_LOGGING_SPEC=INFO
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_LISTENPORT=7050
      - ORDERER_GENERAL_GENESISMETHOD=file
      - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
      - 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/orderer.example.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls
    ports:
      - 7050:7050
    extra_hosts:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
2、org2节点
root@org1:~/hyperledger/multinodes # vi docker-compose.yaml

version: '2'

services:
  couchdb0.org1.example.com:
    container_name: couchdb0.org1.example.com
    image: couchdb:3.1
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=adminpw
    ports:
      - 5984:5984

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    image: hyperledger/fabric-peer:2.2
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - 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=peer0.org1.example.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - FABRIC_LOGGING_SPEC=INFO
      - 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_CHAINCODE_EXECUTETIMEOUT=300s
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0.org1.example.com:5984
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
    depends_on:
      - couchdb0.org1.example.com

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    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:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
  cli:
    container_name: cli
    image: hyperledger/fabric-tools:2.2
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - 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/go/:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go
      - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
      - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
3、org2节点
root@org2:~/hyperledger/multinodes # vi docker-compose.yaml

version: '2'

services:
  couchdb0.org2.example.com:
    container_name: couchdb0.org2.example.com
    image: couchdb:3.1
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=adminpw
    ports:
      - 5984:5984

  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    image: hyperledger/fabric-peer:2.2
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - 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_BOOTSTRAP=peer0.org2.example.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - FABRIC_LOGGING_SPEC=INFO
      - 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_CHAINCODE_EXECUTETIMEOUT=300s
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0.org2.example.com:5984
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
    depends_on:
      - couchdb0.org2.example.com

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    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:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
  cli:
    container_name: cli
    image: hyperledger/fabric-tools:2.2
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - 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/go/:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go
      - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
      - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
5、org3节点
root@org3:~/hyperledger/multinodes # vi docker-compose.yaml

version: '2'

services:
  couchdb0.org3.example.com:
    container_name: couchdb0.org3.example.com
    image: couchdb:3.1
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=adminpw
    ports:
      - 5984:5984

  peer0.org3.example.com:
    container_name: peer0.org3.example.com
    image: hyperledger/fabric-peer:2.2
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org3.example.com
      - CORE_PEER_ADDRESS=peer0.org3.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org3.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org3.example.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org3.example.com:7051
      - CORE_PEER_LOCALMSPID=Org3MSP
      - FABRIC_LOGGING_SPEC=INFO
      - 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_CHAINCODE_EXECUTETIMEOUT=300s
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0.org3.example.com:5984
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
    depends_on:
      - couchdb0.org3.example.com

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls:/etc/hyperledger/fabric/tls
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    extra_hosts:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
  cli:
    container_name: cli
    image: hyperledger/fabric-tools:2.2
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org3.example.com:7051
      - CORE_PEER_LOCALMSPID=Org3MSP
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
      - /var/run/:/host/var/run/
      - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go
      - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
      - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
      - "orderer.example.com:192.168.0.209"
      - "peer0.org1.example.com:192.168.0.237"
      - "peer0.org2.example.com:192.168.0.35"
      - "peer0.org3.example.com:192.168.0.148"
6、启动
root@orderer:~/hyperledger/multinodes # docker-compose up -d

Creating network "multinodes_default" with the default driver
Creating orderer.example.com ... done

root@org1:~/hyperledger/multinodes # docker-compose up -d

Creating network "multinodes_default" with the default driver
Creating couchdb0.org1.example.com ... done
Creating cli                       ... done
Creating peer0.org1.example.com    ... done

root@org2:~/hyperledger/multinodes # docker-compose up -d

Creating network "multinodes_default" with the default driver
Creating cli                       ... done
Creating couchdb0.org2.example.com ... done
Creating peer0.org2.example.com    ... done

root@org3:~/hyperledger/multinodes # docker-compose up -d

Creating network "multinodes_default" with the default driver
Creating cli                       ... done
Creating couchdb0.org3.example.com ... done
Creating peer0.org3.example.com    ... done

五、通道操作

1、创建通道
root@org1:~/hyperledger/multinodes # docker exec -it cli bash

bash-5.1 # peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:09:00.580 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:09:00.625 UTC [cli.common] readBlock -> INFO 002 Received block: 0
bash-5.1 # ls
channel-artifacts  crypto             mychannel.block

将通道文件 mychannel.block 拷贝到宿主机及其他节点的容器

root@org1:~/hyperledger/multinodes # docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel.block ./
root@org1:~/hyperledger/multinodes # scp mychannel.block root@192.168.0.35:~/hyperledger/multinodes/
root@org1:~/hyperledger/multinodes # scp mychannel.block root@192.168.0.148:~/hyperledger/multinodes/
root@org2:~/hyperledger/multinodes # docker cp mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/
root@org3:~/hyperledger/multinodes # docker cp mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/
2、加入通道

org1

root@org1:~/hyperledger/multinodes # docker exec -it cli bash

bash-5.1 # peer channel join -b mychannel.block

2023-01-07 16:10:38.773 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:10:39.131 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel

org2

root@org2:~/hyperledger/multinodes # docker exec -it cli bash

bash-5.1 # peer channel join -b mychannel.block

2023-01-07 16:11:02.265 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:11:02.539 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel

org3

root@org3:~/hyperledger/multinodes # docker exec -it cli bash

bash-5.1 # peer channel join -b mychannel.block

2023-01-07 16:11:23.195 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:11:23.480 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
3、更新锚节点

org1

bash-5.1 # peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:11:45.984 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:11:45.996 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update

org2

bash-5.1 # peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:12:17.781 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:12:17.794 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update

org3

bash-5.1 # peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org3MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:12:47.808 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2023-01-07 16:12:47.822 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update

六、安装调用智能合约

1、复制官方示例智能合约
root@orderer:~/hyperledger/multinodes # cp -r ~/fabric-samples/chaincode/sacc chaincode/go/
root@orderer:~/hyperledger/multinodes # scp -r /chaincode/go/sacc root@192.168.0.237:~/hyperledger/multinodes/chaincode/go
2、容器内设置Go语言依赖包
bash-5.1 # cd /opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go/sacc
bash-5.1 # ls
go.mod        go.sum        sacc.go       sacc_test.go  vendor
bash-5.1 # go env -w GOPROXY=https://goproxy.cn,direct
bash-5.1 # go env -w GO111MODULE=auto
bash-5.1 # go mod init
go: /opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go/sacc/go.mod already exists
bash-5.1 # go mod vendor
go: downloading github.com/hyperledger/fabric-chaincode-go v0.0.0-20190823162523-04390e015b85
go: downloading github.com/hyperledger/fabric-protos-go v0.0.0-20190821214336-621b908d5022
go: downloading github.com/golang/protobuf v1.3.2
go: downloading google.golang.org/grpc v1.23.0
go: downloading golang.org/x/net v0.0.0-20190813141303-74dc4d7220e7
go: downloading google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55
go: downloading golang.org/x/sys v0.0.0-20190813064441-fde4db37ae7a
go: downloading golang.org/x/text v0.3.2
3、打包链码
bash-5.1 # cd /opt/gopath/src/github.com/hyperledger/fabric/peer
bash-5.1 # peer lifecycle chaincode package sacc.tar.gz \
  --path github.com/hyperledger/fabric-cluster/chaincode/go/sacc/ \
  --label sacc_1
bash-5.1 # ls
channel-artifacts  crypto             mychannel.block    sacc.tar.gz
4、安装链码
root@org1:~/hyperledger/multinodes # docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/sacc.tar.gz ./
root@org1:~/hyperledger/multinodes # scp sacc.tar.gz root@192.168.0.35:~/hyperledger/multinodes
root@org1:~/hyperledger/multinodes # scp sacc.tar.gz root@192.168.0.148:~/hyperledger/multinodes
root@org2:~/hyperledger/multinodes # docker cp ~/hyperledger/multinodes/sacc.tar.gz cli:/opt/gopath/src/github.com/hyperledger/fabric/peer
root@org3:~/hyperledger/multinodes # docker cp ~/hyperledger/multinodes/sacc.tar.gz cli:/opt/gopath/src/github.com/hyperledger/fabric/peer

org1

root@org1:~/hyperledger/multinodes# docker exec -it cli bash
bash-5.1# peer lifecycle chaincode install sacc.tar.gz
2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGsacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259\022\006sacc_1" >
2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259

org2

root@org2:~/hyperledger/multinodes# docker exec -it cli bash
bash-5.1# peer lifecycle chaincode install sacc.tar.gz

2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGsacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259\022\006sacc_1" >
2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259

org3

root@org3:~/hyperledger/multinodes# docker exec -it cli bash
bash-5.1# peer lifecycle chaincode install sacc.tar.gz

2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGsacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259\022\006sacc_1" >
2021-11-04 05:44:44.537 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259
5、批准链码

org1

bash-5.1 # peer lifecycle chaincode approveformyorg --channelID mychannel --name sacc --version 1.0 --init-required --package-id  sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:24:16.758 UTC [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
2023-01-07 16:24:19.069 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [b51ade68f0945dae49450e2de531a9355b9e95aaeb799fdb822f8165aca406c9] committed with status (VALID) at peer0.org1.example.com:7051

org2

bash-5.1 # peer lifecycle chaincode approveformyorg --channelID mychannel --name sacc --version 1.0 --init-required --package-id  sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:24:51.265 UTC [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
2023-01-07 16:24:53.486 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [3600b0e40643fb695572fd862c18e15fad7ae5441d6db22ade44c41fb296dc52] committed with status (VALID) at peer0.org2.example.com:7051

org3

bash-5.1 # peer lifecycle chaincode approveformyorg --channelID mychannel --name sacc --version 1.0 --init-required --package-id  sacc_1:2791ff83074c654ab40b864ba03f6bb2710439d720adc883c26438212de8d259 --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

2023-01-07 16:25:10.224 UTC [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
2023-01-07 16:25:12.448 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [f62488656bb49be52068f63f83ea428cfc601036d5f304abe425678325f8f82f] committed with status (VALID) at peer0.org3.example.com:7051
6、查询链码是否就绪

org1

bash-5.1 # peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name sacc --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
        "approvals": {
                "Org1MSP": true,
                "Org2MSP": true,
                "Org3MSP": true
        }
}

org1

bash-5.1 # peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name sacc --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
        "approvals": {
                "Org1MSP": true,
                "Org2MSP": true,
                "Org3MSP": true
        }
}

org2

bash-5.1 # peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name sacc --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
        "approvals": {
                "Org1MSP": true,
                "Org2MSP": true,
                "Org3MSP": true
        }
}

org3

bash-5.1 # peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name sacc --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json
{
        "approvals": {
                "Org1MSP": true,
                "Org2MSP": true,
                "Org3MSP": true
        }
}
7、提交链码

org1

bash-5.1# peer lifecycle chaincode commit -o orderer.example.com:7050 --channelID mychannel --name sacc --version 1.0 --sequence 1 --init-required --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --peerAddresses peer0.org3.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt

2023-01-07 16:26:19.167 UTC [chaincodeCmd] ClientWait -> INFO 001 txid [db855b6edceb89a67e7e4a5f6415da773c20c1d9e926820be3cd2716b11ecc97] committed with status (VALID) at peer0.org2.example.com:7051
2023-01-07 16:26:19.169 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [db855b6edceb89a67e7e4a5f6415da773c20c1d9e926820be3cd2716b11ecc97] committed with status (VALID) at peer0.org3.example.com:7051
2023-01-07 16:26:19.243 UTC [chaincodeCmd] ClientWait -> INFO 003 txid [db855b6edceb89a67e7e4a5f6415da773c20c1d9e926820be3cd2716b11ecc97] committed with status (VALID) at peer0.org1.example.com:7051
8、链码初始化
bash-5.1# peer chaincode invoke -o orderer.example.com:7050 --isInit --ordererTLSHostnameOverride orderer.example.com --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n sacc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --peerAddresses peer0.org3.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt -c '{"Args":["a","bb"]}'

2023-01-07 16:27:12.548 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200
9、查询数据
bash-5.1# peer chaincode query -C mychannel -n sacc -c '{"Args":["query","a"]}'
bb
10、调用链码，新增数据
bash-5.1# peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n sacc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --peerAddresses peer0.org3.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt -c '{"Args":["set","a","cc"]}'

2023-01-07 16:27:38.085 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200 payload:"cc"

bash-5.1# peer chaincode query -C mychannel -n sacc -c '{"Args":["query","a"]}'
cc
云野的生活志
关注
  • 0
    点赞
  • 踩
  • 5
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Fabric 多机部署
10-23
fabric 的多机集群部署教程，包括 1 个 Orderer排序节点和 4 个 peer 节点。
超级账本HyperLedger视频教程：Fabric的全手动、多服务器部署教程
chichitai7025的博客
06-26 540
说明 转自：http://www.lijiaocn.com/%E9%A1%B9%E7%9B%AE/2018/05/04/fabric-ca-example.html 虽然通过Building Your First Network中的docker-compose文件可以直接启动一个all-...
Hyperledger fabric 多机部署
weixin_46698113的博客
04-26 1114
Hyperledger fabric多机部署
Hyperledger Fabric教程--部署Fabric智能合约
未来社会二十年发展的核心技术趋势由ABCD四个字母组成，分别是AI（人工智能）、BlockChain（区块链）、Cloud（云）、和Data（大数据）每一次进步都有新的认知和感触
11-30 4128
在HyperledgerFabric中，智能合约部署在称为链码的包中。想要验证交易或查询分类账的组织需要在其peer节点上安装链码。在加入通道的peer节点上安装链码后，通道成员可以将链码部署到通道，并使用链码中的智能合约在通道分类账上创建或更新资产。链码使用一个称为Fabric chaincode lifecycle的过程部署到通道。Fabric链码生命周期允许多个组织在链码可用之前就其操作方式达成一致。本教程学习如何使用peer lifecycle chaincode命令将链码部署到测试网络。
区块链hyperledger fabric部署
zis0926的博客
04-13 1538
1.2 安装curl 1.3 安装docker 1.4 安装go 新建目录、下载、解压 配置环境 1.5 安装JQ 二 安装实例、二进制和docker镜像 2.1 新建目录，克隆 仓库 选择适当的版本标签，进入目录，切换分支 2.2 下载docker镜像 将指定版本的 Hyperledger Fabric 平台特定二进制文件和配置文件安装到 fabric-samples 下的 和 目录中，下载指定版本的 Hyperledger Fabric do
区块链——Hyperledger Fabric2.2多机搭建及区块链浏览器(修改版)
qq_43197915的博客
02-20 1662
参考(内容有错误,已修改): 区块链——Hyperledger Fabric2.2多机搭建及区块链浏览器前提: order---10.10.10.65，org1---10.10.10.64，org2---10.10.10.53三台服务器都要设置vim /etc/hosts 3、安装golang环境 二、生成Fabric证书（order上执行） 克隆项目fabric和fabric-samples git clone https://gitee.com/hyperledger/fabric.git
阿里云和本地部署fabric多机2.2，踩坑
mei2532的专栏
09-06 781
Fabric多机部署
hyperledger-fabric-linux-amd64-2.2.1.tar.gz
01-18
总结来说，Hyperledger Fabric 2.2.1版本是企业级区块链解决方案的重要里程碑，它的先进特性和持续优化使其在金融、供应链、物联网等多个领域展现出强大的潜力。通过理解并熟练掌握这个压缩包中的组件和工具，开发者...
十二、区块链学习-Hyperledger Fabric (基于release-1.0) 系统架构
01-07
Hyperledger Fabric 系统架构1. 概述2. 系统逻辑架构2.1 从应用程序角度应该关注的要素2.1.1 身份管理2.1.2 账本管理2.1.3 交易管理2.1.4 智能合约2.2 从底层角度应该关注的要素2.2.1 成员管理2.2.2 共识服务2.2.3 ...
hyperledger-fabric-readthedocs-io-en-v2.2.1.pdf
01-27
hyperledger-fabric-readthedocs-io-en-v2.2.1
Hyperledger Fabric kafka配置
03-09
Hyperledger Fabric默认使用solo共识，实际上它早就已经支持kafka共识，只是配置相对复杂点儿。该资源就是使用kafka共识的多orderer集群环境下的网络所需要使用的配置文件。你也可以参考下文帮您理解：http://blog.csdn.net/binbinxyz/article/details/79491254
hyperledger-api:使用Fabric Hyperledger使用可调用的API快速启动区块链
05-01
Hyperledger Fabric演示入门您将需要执行以下操作：先决条件码头工人节点纱建造从根文件夹开始yarn installcd fabric-scripts/build./startBuild.sh对docker缓存问题回答y 如果在较小的服务器上运行此命令，并且构建...
hyperledger-fabric
04-09
它集合了多个不同的区块链框架，其中Hyperledger Fabric是最为成熟且广泛应用于商业场景的一个。 ### 2. Hyperledger Fabric 2.2 特性 #### 2.2.1 模块化设计 Fabric 2.2采用了模块化的设计，使得组件之间可以...
Hyperledger Fabric区块链浏览器搭建
weixin_58267277的博客
10-25 3853
区块链浏览器搭建需要下载和修改配置文件，并需要使用区块链网络的证书文件和区块等信息。在对应的区块链网络启动之后，就可以启动区块链浏览器了。
fabric2.2环境搭建，链码部署至通道
J2633500154的博客
12-14 1531
fabric2.2环境搭建，链码部署至通道
Hyperledger Fabric 开发实战 - Fabric环境部署
张亚平的博客
12-09 815
第2章 Fabric及环境部署
Fabric 超级账本学习【5】Fabric2.4网络环境下——搭建Hyperledger Fabric区块链浏览器
weixin_42694422的博客
03-15 2815
Hyperledger Explorer 是一个简单，强大，易于使用，维护良好的开源实用程序，可浏览底层区块链网络上的活动。用户可以在MacOS和Ubuntu上配置和构建Hyperledger Explorer区块链浏览器。让Hyperledger Fabric实战项目更加可视化，具体节点、通道、链码信息查看更加方便高效。
3. 部署Fabric2.2 集群（使用官方Demo）
菜鸟的博客
02-22 3331
上节作者新购买阿里云，与大家一起操作，不遗漏每个操作步骤，保证大家都可以成功部署区块链集群。环境准备完毕，本节下载Fabric官方demo，并部署区块链集群。 1）安装git命令 yum install -y git 2）下载Fabric 2.2.1 版本代码 有点慢 或者出现中断情况，请反复操作，这是github网址 国内的支持不是很好。 git clone -b v2.2.1 https://github.com/hyperledger/fabric.git 3）下载依赖二进制、镜像 这个步骤也.
docker笔记1
最新发布
计算机小白的奋起
07-09 383
docker学习笔记
基于RS总线的多机通信专业系统设计.doc
11-23
基于RS总线的多机通信专业系统设计 摘要： 在多机通信领域中，单片机由于其灵活高效的多机通信功能和价格优势，应用越来越广泛。然而，由于单片机的收发信号全部是TTI电平，其驱动能力和抗干扰性有限，因此通常需要...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值