docker搭建fabric

已于 2022-10-30 12:23:32 修改
阅读量1.7k 收藏 4
点赞数 1
分类专栏： 区块链 文章标签： docker fabric linux ubuntu
于 2022-10-06 21:23:30 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zhangmingfie/article/details/127188120
版权

前置准备

修改/etc/hosts文件的域名映射

vim /etc/hosts

# 新增

192.168.2.130 orderer0.example.com
192.168.2.130 orderer1.example.com
192.168.2.130 orderer2.example.com

192.168.2.130 peer0.org1.example.com
192.168.2.130 peer1.org1.example.com

192.168.2.130 peer0.org2.example.com
192.168.2.130 peer1.org2.example.com

把order以及peer的各个证书通道生成完毕，如果没有生成各个证书通道文件，可以去看下面的这篇文章
生成通道以及证书文件

编写docker-compose-3orderer.yaml

  1. 进入根目录
mkdir docker
mkdir chaincodes
cd docker
vim docker-compose-3orderer.yaml



version: '2.0'

services:

    cli:
        image: hyperledger/fabric-tools:2.4.1
        restart: always
        container_name: fabric-cli
        hostname: fabric-cli
        tty: true
        extra_hosts:
            - "orderer0.example.com:192.168.2.130"
            - "orderer1.example.com:192.168.2.130"
            - "orderer2.example.com:192.168.2.130"
            - "peer0.org1.example.com:192.168.2.130"
            - "peer1.org1.example.com:192.168.2.130"
            - "peer0.org2.example.com:192.168.2.130"
            - "peer1.org2.example.com:192.168.2.130"
        environment:
            - CORE_PEER_ID=fabric-cli
            - CORE_PEER_ADDRESS=peer0.org1.example.com:7051 # default to operate on peer0.org1
            - CORE_PEER_LOCALMSPID=Org1MSP
            - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
            - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
            - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
            - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
            - FABRIC_LOGGING_SPEC=DEBUG
            - FABRIC_LOGGING_FORMAT=%{color}[%{id:03x} %{time:01-02 15:04:05.00 MST}] [%{module}] %{shortfunc} -> %{level:.4s}%{color:reset} %{message}
            - CORE_PEER_TLS_ENABLED=true  # to enable TLS, change to true
            - ORDERER_CA=/etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
        volumes:
            - ../crypto-config.yaml:/etc/hyperledger/fabric/crypto-config.yaml
            - ../config/configtx.yaml:/etc/hyperledger/fabric/configtx.yaml
            - ../crypto-config:/etc/hyperledger/fabric/crypto-config
            - ../channel-artifacts:/tmp/channel-artifacts
            - ../chaincodes:/etc/hyperledger/fabric/chaincodes
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
        command: bash -c 'cd /tmp; source scripts/func.sh; while true; do sleep 20170504; done'


    orderer0.example.com:  # There can be multiple orderers
        image: hyperledger/fabric-orderer:2.4.1
        restart: always
        container_name: orderer0.example.com
        hostname: orderer0.example.com
        ports:
            - "7050:7050"
        extra_hosts:
            - "orderer0.example.com:192.168.2.130"
            - "orderer1.example.com:192.168.2.130"
            - "orderer2.example.com:192.168.2.130"
            - "peer0.org1.example.com:192.168.2.130"
            - "peer1.org1.example.com:192.168.2.130"
            - "peer0.org2.example.com:192.168.2.130"
            - "peer1.org2.example.com:192.168.2.130"
        environment:
            - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
            - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 # default: 127.0.0.1
            - ORDERER_GENERAL_LISTENPORT=7050
            - ORDERER_GENERAL_GENESISMETHOD=file # default: provisional
            - ORDERER_GENERAL_BOOTSTRAPFILE=/etc/hyperledger/fabric/orderer.genesis.block # by default, all materials should be put under $FABRIC_CFG_PATH, which defaults to /etc/hyperledger/fabric
            - ORDERER_GENERAL_LOCALMSPID=OrdererMSP # default: DEFAULT
            - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/fabric/msp
            - ORDERER_GENERAL_LEDGERTYPE=file
            #- ORDERER_GENERAL_LEDGERTYPE=json  # default: file
            - ORDERER_OPERATIONS_LISTENADDRESS=0.0.0.0:8443  # operation RESTful API
            - ORDERER_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from orderer via /metrics RESTful API
            #- ORDERER_RAMLEDGER_HISTORY_SIZE=100  #only useful when use ram ledger
            # enabled TLS
            - ORDERER_GENERAL_TLS_ENABLED=true # default: false
            - ORDERER_GENERAL_TLS_PRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_TLS_CERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_TLS_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            # Only required by raft mode
            - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            - FABRIC_LOGGING_SPEC=DEBUG
        volumes:
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/etc/hyperledger/fabric/msp
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/etc/hyperledger/fabric/tls
            - ../channel-artifacts/orderer.genesis.block:/etc/hyperledger/fabric/orderer.genesis.block
        expose:
            - "7050"  # gRPC
            - "8443"  # Operation REST
        command: orderer start

    orderer1.example.com:
        image: hyperledger/fabric-orderer:2.4.1
        restart: always
        container_name: orderer1.example.com
        hostname: orderer1.example.com
        ports:
            - "8050:7050"
        extra_hosts:
            - "orderer0.example.com:192.168.2.130"
            - "orderer1.example.com:192.168.2.130"
            - "orderer2.example.com:192.168.2.130"
            - "peer0.org1.example.com:192.168.2.130"
            - "peer1.org1.example.com:192.168.2.130"
            - "peer0.org2.example.com:192.168.2.130"
            - "peer1.org2.example.com:192.168.2.130"
        environment:
            - FABRIC_LOGGING_SPEC=DEBUG
            - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
            - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 # default: 127.0.0.1
            - ORDERER_GENERAL_LISTENPORT=7050
            - ORDERER_GENERAL_GENESISMETHOD=file # default: provisional
            - ORDERER_GENERAL_BOOTSTRAPFILE=/etc/hyperledger/fabric/orderer.genesis.block # by default, all materials should be put under $FABRIC_CFG_PATH, which defaults to /etc/hyperledger/fabric
            - ORDERER_GENERAL_LOCALMSPID=OrdererMSP # default: DEFAULT
            - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/fabric/msp
            - ORDERER_GENERAL_LEDGERTYPE=file
            #- ORDERER_GENERAL_LEDGERTYPE=json  # default: file
            - ORDERER_OPERATIONS_LISTENADDRESS=0.0.0.0:8443  # operation RESTful API
            - ORDERER_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from orderer via /metrics RESTful API
            #- ORDERER_RAMLEDGER_HISTORY_SIZE=100  #only useful when use ram ledger
            # enabled TLS
            - ORDERER_GENERAL_TLS_ENABLED=true # default: false
            - ORDERER_GENERAL_TLS_PRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_TLS_CERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_TLS_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            # Only required by raft mode
            - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            - ORDERER_GENERAL_CLUSTER_SENDBUFFERSIZE=10
        volumes:
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/msp:/etc/hyperledger/fabric/msp
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/:/etc/hyperledger/fabric/tls
            - ../channel-artifacts/orderer.genesis.block:/etc/hyperledger/fabric/orderer.genesis.block
        command: orderer start    


    orderer2.example.com:
        image: hyperledger/fabric-orderer:2.4.1
        restart: always
        container_name: orderer2.example.com
        hostname: orderer2.example.com
        ports:
            - "9050:7050"
        extra_hosts:
            - "orderer0.example.com:192.168.2.130"
            - "orderer1.example.com:192.168.2.130"
            - "orderer2.example.com:192.168.2.130"
            - "peer0.org1.example.com:192.168.2.130"
            - "peer1.org1.example.com:192.168.2.130"
            - "peer0.org2.example.com:192.168.2.130"
            - "peer1.org2.example.com:192.168.2.130"
        environment:
            - FABRIC_LOGGING_SPEC=DEBUG  # default: INFO
            - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
            - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 # default: 127.0.0.1
            - ORDERER_GENERAL_LISTENPORT=7050
            - ORDERER_GENERAL_GENESISMETHOD=file # default: provisional
            - ORDERER_GENERAL_BOOTSTRAPFILE=/etc/hyperledger/fabric/orderer.genesis.block # by default, all materials should be put under $FABRIC_CFG_PATH, which defaults to /etc/hyperledger/fabric
            - ORDERER_GENERAL_LOCALMSPID=OrdererMSP # default: DEFAULT
            - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/fabric/msp
            - ORDERER_GENERAL_LEDGERTYPE=file
            #- ORDERER_GENERAL_LEDGERTYPE=json  # default: file
            - ORDERER_OPERATIONS_LISTENADDRESS=0.0.0.0:8443  # operation RESTful API
            - ORDERER_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from orderer via /metrics RESTful API
            #- ORDERER_RAMLEDGER_HISTORY_SIZE=100  #only useful when use ram ledger
            # enabled TLS
            - ORDERER_GENERAL_TLS_ENABLED=true # default: false
            - ORDERER_GENERAL_TLS_PRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_TLS_CERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_TLS_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            # Only required by raft mode
            - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
            - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
            - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
            - ORDERER_GENERAL_CLUSTER_SENDBUFFERSIZE=10
        volumes:
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/msp:/etc/hyperledger/fabric/msp
            - ../crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/:/etc/hyperledger/fabric/tls
            - ../channel-artifacts/orderer.genesis.block:/etc/hyperledger/fabric/orderer.genesis.block
        command: orderer start

  1. 启动配置文件

    docker-compose -f docker-compose-3orderer.yaml up -d

    如果想停止并且删除服务：

    docker-compose -f docker-compose-3orderer.yaml down

    ​

    ps:想要在图形化界面中进行访问需要安装portainer.io

    安装命令：

    docker pull portainer/portainer
docker run -d -p 9000:9000 -v /root/portainer:/data -v /var/run/docker.sock:/var/run/docker.sock --name portainer portainer/portainer

编写docker-compose-org1-2peer-couchdb.yaml

  1. 进入到docker目录下

  2. 编写docker-compose-org1-2peer-couchdb.yaml文件

version: '2.0'
    
services:
       peer0.org1.example.com:
           image: hyperledger/fabric-peer:2.4.1
           restart: always
           container_name: peer0.org1.example.com
           hostname: peer0.org1.example.com
           ports:
               - 7051:7051
               - 7052:7052
               - 9443:9443
           extra_hosts:
               - "orderer0.example.com:192.168.2.130"
               - "orderer1.example.com:192.168.2.130"
               - "orderer2.example.com:192.168.2.130"
               - "peer0.org1.example.com:192.168.2.130"
               - "peer1.org1.example.com:192.168.2.130"
               - "peer0.org2.example.com:192.168.2.130"
               - "peer1.org2.example.com:192.168.2.130"
           environment:
               - FABRIC_LOGGING_SPEC=INFO
               - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
               - CORE_PEER_ADDRESSAUTODETECT=false
               - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=host  # uncomment this to use specific network
               - CORE_PEER_GOSSIP_USELEADERELECTION=true
               - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to false
               - CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9443  # operation RESTful API
               - CORE_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from fabric via /metrics RESTful API
               - CORE_PEER_PROFILE_ENABLED=false
               - CORE_PEER_TLS_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_BUILDER=hyperledger/fabric-ccenv:2.4.1
               - CORE_CHAINCODE_GOLANG_RUNTIME=hyperledger/fabric-baseos:2.4.1
               - CORE_CHAINCODE_JAVA_RUNTIME=hyperledger/fabric-javaenv:2.4.1
               - CORE_CHAINCODE_NODE_RUNTIME=hyperledger/fabric-nodeenv:2.4.1
               - CORE_PEER_ID=peer0.org1.example.com
               - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
               - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
               - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
               - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
               - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
               - CORE_PEER_LOCALMSPID=Org1MSP
               - FABRIC_LOGGING_SPEC=DEBUG # info:core.chaincode=debug
               - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
               - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=peer0.org1.couchdb:5984
               - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
               - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
           volumes:
               - /var/run/docker.sock:/var/run/docker.sock
               - ../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
           expose:
               - "7051"  # gRPC
               - "9443"  # Operation REST
           #command: bash -c 'bash /tmp/peer_build.sh; peer node start'
           command: peer node start
           depends_on:
               - peer0.org1.couchdb
    
    
       peer1.org1.example.com:
           image: hyperledger/fabric-peer:2.4.1
           restart: always
           container_name: peer1.org1.example.com
           hostname: peer1.org1.example.com
           ports:
               - 8051:7051
               - 8052:7052
               - 9444:9443
           extra_hosts:
               - "orderer0.example.com:192.168.2.130"
               - "orderer1.example.com:192.168.2.130"
               - "orderer2.example.com:192.168.2.130"
               - "peer0.org1.example.com:192.168.2.130"
               - "peer1.org1.example.com:192.168.2.130"
               - "peer0.org2.example.com:192.168.2.130"
               - "peer1.org2.example.com:192.168.2.130"
           environment:
               - FABRIC_LOGGING_SPEC=INFO
               - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
               - CORE_PEER_ADDRESSAUTODETECT=false
               - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=host  # uncomment this to use specific network
               - CORE_PEER_GOSSIP_USELEADERELECTION=true
               - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to false
               - CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9443  # operation RESTful API
               - CORE_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from fabric via /metrics RESTful API
               - CORE_PEER_PROFILE_ENABLED=false
               - CORE_PEER_TLS_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_BUILDER=hyperledger/fabric-ccenv:2.4.1
               - CORE_CHAINCODE_GOLANG_RUNTIME=hyperledger/fabric-baseos:2.4.1
               - CORE_CHAINCODE_JAVA_RUNTIME=hyperledger/fabric-javaenv:2.4.1
               - CORE_CHAINCODE_NODE_RUNTIME=hyperledger/fabric-nodeenv:2.4.1
               - CORE_PEER_ID=peer1.org1.example.com
               - CORE_PEER_ADDRESS=peer1.org1.example.com:8051
               - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
               - CORE_PEER_CHAINCODEADDRESS=peer1.org1.example.com:8052
               - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:8051
               - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.example.com:8051
               - CORE_PEER_LOCALMSPID=Org1MSP
               - FABRIC_LOGGING_SPEC=DEBUG # info:core.chaincode=debug
               - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
               - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=peer1.org1.couchdb:5984
               - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
               - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
           volumes:
               - /var/run/docker.sock:/var/run/docker.sock
               - ../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
           expose:
               - "8051"  # gRPC
               - "8052"  # chaincode
               - "9444"  # Operation REST
           #command: bash -c 'bash /tmp/peer_build.sh; peer node start'
           command: peer node start
           depends_on:
               - peer1.org1.couchdb
    
       
                       
       peer0.org1.couchdb:
           image: couchdb:3.1.1
           container_name: peer0.org1.couchdb
           ports:
               - 5984:5984  # this is the restful API addr, can also access fauxton web ui thru http://localhost:5984/_utils/
           environment:
               - COUCHDB_USER=admin
               - COUCHDB_PASSWORD=adminpw
    
       peer1.org1.couchdb:
           image: couchdb:3.1.1
           container_name: peer1.org1.couchdb
           ports:
               - 6984:5984  # this is the restful API addr, can also access fauxton web ui thru http://localhost:5984/_utils/
           environment:
               - COUCHDB_USER=admin
               - COUCHDB_PASSWORD=adminpw

  1. 启动配置文件

    docker-compose -f docker-compose-org1-2peer-couchdb.yaml up -d

编写docker-compose-org2-2peer-couchdb.yaml

  1. 进入docker目录

  2. 编辑docker-compose-org2-2peer-couchdb.yaml

version: '2.0'

services:

   peer0.org2.example.com:
       image: hyperledger/fabric-peer:2.4.1
       restart: always
       container_name: peer0.org2.example.com
       hostname: peer0.org2.example.com
       ports:
           - 9051:7051
           - 9052:7052
           - 9445:9443
       extra_hosts:
           - "orderer0.example.com:192.168.2.130"
           - "orderer1.example.com:192.168.2.130"
           - "orderer2.example.com:192.168.2.130"
           - "peer0.org1.example.com:192.168.2.130"
           - "peer1.org1.example.com:192.168.2.130"
           - "peer0.org2.example.com:192.168.2.130"
           - "peer1.org2.example.com:192.168.2.130"
       environment:
           - FABRIC_LOGGING_SPEC=INFO
           - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
           - CORE_PEER_ADDRESSAUTODETECT=false
           - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=host  # uncomment this to use specific network
           - CORE_PEER_GOSSIP_USELEADERELECTION=true
           - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to false
           - CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9443  # operation RESTful API
           - CORE_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from fabric via /metrics RESTful API
           - CORE_PEER_PROFILE_ENABLED=false
           - CORE_PEER_TLS_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_BUILDER=hyperledger/fabric-ccenv:2.4.1
           - CORE_CHAINCODE_GOLANG_RUNTIME=hyperledger/fabric-baseos:2.4.1
           - CORE_CHAINCODE_JAVA_RUNTIME=hyperledger/fabric-javaenv:2.4.1
           - CORE_CHAINCODE_NODE_RUNTIME=hyperledger/fabric-nodeenv:2.4.1
           - CORE_PEER_ID=peer0.org2.example.com
           - CORE_PEER_ADDRESS=peer0.org2.example.com:9051
           - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
           - CORE_PEER_CHAINCODEADDRESS=peer0.org2.example.com:9052
           - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:9051
           - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.example.com:9051
           - CORE_PEER_LOCALMSPID=Org2MSP
           - FABRIC_LOGGING_SPEC=DEBUG # info:core.chaincode=debug
           - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
           - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=peer0.org1.couchdb:5984
           - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
           - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
       volumes:
           - /var/run/docker.sock:/var/run/docker.sock
           - ../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
       expose:
           - "9051"  # gRPC
           - "9445"  # Operation REST
       #command: bash -c 'bash /tmp/peer_build.sh; peer node start'
       command: peer node start
       depends_on:
           - peer0.org1.couchdb


   peer1.org2.example.com:
       image: hyperledger/fabric-peer:2.4.1
       restart: always
       container_name: peer1.org2.example.com
       hostname: peer1.org2.example.com
       ports:
           - 10051:7051
           - 10052:7052
           - 9446:9443
       extra_hosts:
           - "orderer0.example.com:192.168.2.130"
           - "orderer1.example.com:192.168.2.130"
           - "orderer2.example.com:192.168.2.130"
           - "peer0.org1.example.com:192.168.2.130"
           - "peer1.org1.example.com:192.168.2.130"
           - "peer0.org2.example.com:192.168.2.130"
           - "peer1.org2.example.com:192.168.2.130"
       environment:
           - FABRIC_LOGGING_SPEC=INFO
           - FABRIC_LOGGING_FORMAT="%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}"
           - CORE_PEER_ADDRESSAUTODETECT=false
           - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=host  # uncomment this to use specific network
           - CORE_PEER_GOSSIP_USELEADERELECTION=true
           - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to false
           - CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9443  # operation RESTful API
           - CORE_METRICS_PROVIDER=prometheus  # prometheus will pull metrics from fabric via /metrics RESTful API
           - CORE_PEER_PROFILE_ENABLED=false
           - CORE_PEER_TLS_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_BUILDER=hyperledger/fabric-ccenv:2.4.1
           - CORE_CHAINCODE_GOLANG_RUNTIME=hyperledger/fabric-baseos:2.4.1
           - CORE_CHAINCODE_JAVA_RUNTIME=hyperledger/fabric-javaenv:2.4.1
           - CORE_CHAINCODE_NODE_RUNTIME=hyperledger/fabric-nodeenv:2.4.1
           - CORE_PEER_ID=peer1.org2.example.com
           - CORE_PEER_ADDRESS=peer1.org2.example.com:10051
           - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
           - CORE_PEER_CHAINCODEADDRESS=peer1.org2.example.com:10052
           - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:10051
           - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.example.com:10051
           - CORE_PEER_LOCALMSPID=Org2MSP
           - FABRIC_LOGGING_SPEC=DEBUG # info:core.chaincode=debug
           - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
           - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=peer1.org2.couchdb:5984
           - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
           - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
       volumes:
           - /var/run/docker.sock:/var/run/docker.sock
           - ../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
       expose:
           - "10051"  # gRPC
           - "9446"  # Operation REST
       #command: bash -c 'bash /tmp/peer_build.sh; peer node start'
       command: peer node start
       depends_on:
           - peer1.org2.couchdb


   peer0.org1.couchdb:
       image: couchdb:3.1.1
       container_name: peer0.org1.couchdb
       ports:
           - 7984:5984  # this is the restful API addr, can also access fauxton web ui thru http://localhost:5984/_utils/
       environment:
           - COUCHDB_USER=admin
           - COUCHDB_PASSWORD=adminpw

   peer1.org2.couchdb:
       image: couchdb:3.1.1
       container_name: peer1.org2.couchdb
       ports:
           - 8984:5984  # this is the restful API addr, can also access fauxton web ui thru http://localhost:5984/_utils/
       environment:
           - COUCHDB_USER=admin
           - COUCHDB_PASSWORD=adminpw

  1. 启动配置文件

    docker-compose -f docker-compose-org2-2peer-couchdb.yaml up -d

    ​

  2. 登录进去docker 容器中

    docker exec -it fabric-cli bash

    ​

加入通道

  1. 创建通道，登录进docker容器之中

  2. 创建成功之后会生成businesschannel.block文件

    export APP_CHANNEL=businesschannel
export TIMEOUT=30
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp

peer channel create -o orderer0.example.com:7050 -c ${APP_CHANNEL} -f "/tmp/channel-artifacts/$APP_CHANNEL.tx" --timeout "${TIMEOUT}s" --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    ​

  3. org1-peer0 加入通道：

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051

peer channel join -b /tmp/channel-artifacts/businesschannel.block

    结果如下

    [020 02-18 03:57:28.30 UTC] [channelCmd] executeJoin -> INFO Successfully submitted proposal to join channel

    ​

  4. org1-peer1加入通道

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer1.org1.example.com:8051


peer channel join -b /tmp/channel-artifacts/businesschannel.block

    ​

  5. org2-peer0加入通道

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer0.org2.example.com:9051

peer channel join -b /tmp/channel-artifacts/businesschannel.block

    ​

  6. org2-peer1加入通道

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer1.org2.example.com:10051

peer channel join -b /tmp/channel-artifacts/businesschannel.block

    ​

更新锚节点

  1. org1更新锚节点

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051

peer channel update -o orderer0.example.com:7050 -c businesschannel -f /tmp/channel-artifacts/Org1MSPanchors.tx --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    ​

  2. org2更新锚节点

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer0.org2.example.com:9051

peer channel update -o orderer0.example.com:7050 -c businesschannel -f /tmp/channel-artifacts/Org2MSPanchors.tx --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    锚节点配置更新后，同一通道内不同组织之间的 Peer 也可以进行 Gossip 通信，共同维护通道账本。后续，用户可以通过智能合约使用通道账本。

安装链码

  1. 进入cli容器

    docker exec -it fabric-cli bash

    ​

  2. 把链码上传到chaincodes目录中，对应的挂载目录为/etc/hyperledger/fabric/chaincodes/,将chaincode.jar以及META-INF和collections_config.json放到新建的hyperledger-fabric-contract-java-demo目录中

  3. 打包链码

    peer lifecycle chaincode package hyperledger-fabric-contract-java-demo.tar.gz --path /etc/hyperledger/fabric/chaincodes/hyperledger-fabric-contract-java-demo/ --lang java --label hyperledger-fabric-contract-java-demo_1

    ​

  4. 在各个peer上安装链码

    cd /etc/hyperledger/fabric/chaincodes/

    这一步可以省略，只要保证在docker容器中的这个目录下即可

    cd /opt/gopath/src/github.com/hyperledger/fabric/peer

    ​

  5. org1-peer0节点

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051


peer lifecycle chaincode install hyperledger-fabric-contract-java-demo.tar.gz

    结果如下

    [020 02-18 03:26:06.78 UTC] [cli.lifecycle.chaincode] submitInstallProposal -> INFO Installed remotely: response:<status:200 payload:"\nhhyperledger-fabric-contract-java-demo_1:bbc6a881b7cf349cd608a608d32e638b546341575e48614524761ab51fc6a457\022'hyperledger-fabric-contract-java-demo_1" > 

[021 02-18 03:26:06.78 UTC] [cli.lifecycle.chaincode] submitInstallProposal -> INFO Chaincode code package identifier: hyperledger-fabric-contract-java-demo_1:bbc6a881b7cf349cd608a608d32e638b546341575e48614524761ab51fc6a457

    ​

  6. org1-peer1

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer1.org1.example.com:8051

peer lifecycle chaincode install hyperledger-fabric-contract-java-demo.tar.gz

    ​

  7. org2- peer0节点

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer0.org2.example.com:9051

peer lifecycle chaincode install hyperledger-fabric-contract-java-demo.tar.gz

    ​

  8. org2-peer1节点

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer1.org2.example.com:10051

peer lifecycle chaincode install hyperledger-fabric-contract-java-demo.tar.gz

    ​

  9. 查询包ID

    peer lifecycle chaincode queryinstalled

    ​

  10. 包 ID 是链码标签和链码二进制文件的哈希值的组合。每个 peer 节点将生成相同的包 ID。你应该看到类似于以下内容的输出：

    Installed chaincodes on peer:
Package ID: hyperledger-fabric-contract-java-demo_1:bbc6a881b7cf349cd608a608d32e638b546341575e48614524761ab51fc6a457, Label: hyperledger-fabric-contract-java-demo_1

    ​

  11. 将包ID保存为环境变量

    export CC_PACKAGE_ID=hyperledger-fabric-contract-java-demo_1:bbc6a881b7cf349cd608a608d32e638b546341575e48614524761ab51fc6a457

    ​

批准链码定义

  1. org1批准链码定义

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051

peer lifecycle chaincode approveformyorg -o orderer0.example.com:7050 --ordererTLSHostnameOverride orderer0.example.com --channelID businesschannel --name hyperledger-fabric-contract-java-demo --version 1.0 --package-id $CC_PACKAGE_ID --sequence 1 --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    结果如下：

    [025 02-18 05:37:12.44 UTC] [chaincodeCmd] ClientWait -> INFO txid [895c0d4b9eee30419e068072b816906f660c1f9ddb7400b63d6892a001470c38] committed with status (VALID) at peer0.org1.example.com:7051

    ​

  2. org2批准链码定义：

    export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=peer0.org2.example.com:9051

peer lifecycle chaincode approveformyorg -o orderer0.example.com:7050 --ordererTLSHostnameOverride orderer0.example.com --channelID businesschannel --name hyperledger-fabric-contract-java-demo --version 1.0 --package-id $CC_PACKAGE_ID --sequence 1 --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    ​

  3. 检查通道成员是否已批准相同的链码定义：

    peer lifecycle chaincode checkcommitreadiness --channelID businesschannel --name hyperledger-fabric-contract-java-demo --version 1.0 --sequence 1 --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json

    输出结果如下：

    {
	"approvals": {
		"Org1MSP": true,
		"Org2MSP": true
	}
}

    ​

  4. 将链码提交到通道

    peer lifecycle chaincode commit -o orderer0.example.com:7050 --ordererTLSHostnameOverride orderer0.example.com --channelID businesschannel --name hyperledger-fabric-contract-java-demo --version 1.0 --sequence 1 --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt

    结果如下

    [029 02-18 05:50:47.62 UTC] [chaincodeCmd] ClientWait -> INFO txid [2c06365cd94ebcc95e4fc6e5a5334aafda35e874bf894ef604fd3a9fe18d86be] committed with status (VALID) at peer0.org2.example.com:7051
[02a 02-18 05:50:47.81 UTC] [chaincodeCmd] ClientWait -> INFO txid [2c06365cd94ebcc95e4fc6e5a5334aafda35e874bf894ef604fd3a9fe18d86be] committed with status (VALID) at peer0.org1.example.com:7051

    用 peer lifecycle chaincode querycommitted 命令来确认链码定义已提交给通道:

    peer lifecycle chaincode querycommitted --channelID businesschannel --name hyperledger-fabric-contract-java-demo --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    结果如下：

    Committed chaincode definition for chaincode 'hyperledger-fabric-contract-java-demo' on channel 'businesschannel':
Version: 1.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]

    ​

调用链码

# 调用 createCat 函数
peer chaincode invoke -o orderer0.example.com:7050 --ordererTLSHostnameOverride orderer0.example.com --tls --cafile /etc/hyperledger/fabric/crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C businesschannel -n hyperledger-fabric-contract-java-demo --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /etc/hyperledger/fabric/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /etc/hyperledger/fabric/crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c '{"function":"createCat","Args":["cat-0" , "tom" ,  "3" , "蓝色" , "大懒猫"]}'

# 调用 queryCat 函数
peer chaincode query -C businesschannel -n hyperledger-fabric-contract-java-demo -c '{"Args":["queryCat" , "cat-0"]}'
爱写代码的大狼
关注
  • 1
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 3
    评论
专栏目录
区块链之Hyperledgerd搭建（二、下载fabric源代码并用Docker 创建Fabric网络 & 创建/加入通道（账本））
zhangliangqi2000的博客
06-22 3208
上一张说到把docker 以及docker-compose的安装，现在开始下载源代码以及加入通道下载并安装 Curl 工具1、 创建 Fabric 工程和项目目录.mkdir -p work cd work然后, 执行如下代码:curl -L https://raw.githubusercontent.com/voodoo12345/polaris/master/fabpre.tar.gz -o
Fabric Docker：多机多节点部署生产网络
06-25
docker-yaml peer-yaml bin config-yaml
Docker 方式多机部署 Fabric 网络
黑帽子技术的博客
02-18 953
Docker 方式多机部署 Fabric 网络 规划网络拓扑 3 个 orderer 节点; 组织 org1 , org1 下...
Michael.W谈hyperledger Fabric第9期-手动搭建Fabric网络之编写用于启动网络的docker-compose配置文件-peer节点
Revelation_of_Turing
03-10 866
Michael.W谈hyperledger Fabric第9期-手动搭建Fabric网络之编写用于启动网络的docker-compose配置文件-peer节点4 修改peer节点容器的配置4.1 leader节点 4 修改peer节点容器的配置 老样子，先看一下docker-compose-cli.yaml文件中对peer节点容器的配置： # 文件：docker-compose-cli.yaml...
基于docker的 Hyperledger Fabric 多机环境搭建（上）
weixin_33782386的博客
06-12 143
环境：ubuntu 16.04 Docker 17.04.0-ce go 1.7.4 consoul v0.8.0.4 ======================================================================= 一、项目准备 想必能搜到这篇文章的人对Hyperledger Fabric(以下简称Fabric)已经是有了一定的了...
深入理解Fabric环境搭建的详细过程
weixin_34008933的博客
08-30 868
博主之前的文章都是教大家怎么快速的搭建一个Fabric的环境，但是其中大量的工作都隐藏到了官方的脚本中，并不方便大家深入理解其中的过程，所以博主这里就将其中的过程一步步分解，方便大家！ 前面的准备工作我就不用多说了，也就是各种软件和开发环境的安装，安装好以后，我们git clone下来最新的代码，并切换到v1.0.0，并且下载好我们需要使用的docker镜像，也就是到步骤6，接下来我们要解析的是...
2.搭建Fabric区块链网络环境——前提条件和fabric的安装
weixin_61275790的博客
05-21 1884
Fabric二进制工具是Hyperledger Fabric区块链框架的核心组件，用于管理、操作和部署区块链网络，并可以执行各种区块链操作，从而实现可信的、去中心化的应用程序和业务逻辑。Fabric镜像下载为您提供了一种方便的方式来获取和部署Fabric网络，加速开发和部署过程，并提供了一个可靠和可重复的环境来构建和测试Fabric应用程序。Fabric的安装作用是将Fabric的二进制文件安装到系统中，以便后面使用Fabric的命令行工具进行链码开发，网络配置和管理等操作。
hyperledger fabric 基础环境搭建（win10下VMware中centos7）一
weixin_41803458的博客
08-13 1013
一、安装环境：centos 7 安装过程中踩了n多的坑，虚拟机就装了很多次。 二、安装环境：docker等 引用了这个链接：https://blog.csdn.net/u010857052/article/details/83931500 包含了docker、docker-compose、go 、git的安装步骤，亲测可行，安装简便。其中从链接第四步开始，本人做了些改动。 其中上图的第3小步设置环境变量时，记得用su命令进入root权限下再用vim /etc/profile，否则不能保存。
Fabric8 构建可执行Docker镜像，采用默认DockerFile
iteye_7129的博客
09-18 519
Fabric8构建可执行镜像
Fabric建链docker-compose方式（客户端与节点主机分离）
最新发布
天天向上
11-01 516
前文启动节点都是在主机本地，这里将换用docker容器启动各个节点，同样也是保证客户端和节点主机不在一个机器。假设客户端主机在192.168.2.195，在节点主机192.168.3.128部署1个orderer节点和1个peer节点。最终一样保证链码的正常安装和调用。
基于docker容器的fabric浏览器的搭建.md
05-07
区块链技术、联盟链fabric
详解使用docker 1.12 搭建多主机docker swarm集群
01-10
swarm是docker公司自己的容器集群管理工具，本文介绍了使用docker 1.12 搭建多主机docker swarm集群，分享给大家 准备 准备至少两台的centos 7 主机(全新最小安装, 可以使用虚拟机安装) 开放端口2377 tcp端口, ...
Fabric开发（一）ubuntu下快速搭建fabric1.4.3
01-07
1、安装前准备： 安装 git、curl、pip sudo apt-get install git sudo apt-get install curl sudo apt-get install python-pip pip install --upgrade pip 2、安装go 我这次安装的是go12.5 ...sudo tar -C /usr/local ...
Hypterledger Fabric 1.4环境搭建
01-07
环境搭建流程 1. 环境依赖 依赖的软件版本根据安装的Fabric的版本差异而略有不同，具体请查看fabric的docs/source目录下的prereqs.rst。 1.1 注 本次配置使用的为阿里云主机，系统：CentOS Linux release 7.5.1804 ...
Hyperledger Fabric 搭建 mac and centos7
12-19
Hyperledger Fabric 搭建 mac and centos7 压缩包包含 1.boot2docker.iso version:17.09.1-ce 2.fabric 官方例子 3.mac and centos7 一键安装脚本
【速通区块链】Fabric开发运行环境（一）——Docker-ce、Docker-Compose、Go语言环境、Node.js+npm、Git安装
Matrix的博客
04-20 5857
（一）安装Docker-ce （1）安装依赖 sudo yum install -y yum-utils device-mapper-persistent-data lvm2 （2）换源 sudo yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo （3）更新 yum 软件源缓存 sudo yum makecache fast （4）安装Docker-c
记一次ubuntu18 采用docker部署Fabric1.4以及所遇到的大坑(一)
weixin_41767181的博客
10-28 329
记一次ubuntu18 采用docker部署Fabric1.4（一） 目录记一次ubuntu18 采用docker部署Fabric1.4（一）关于Docker和Fabric1.4下载（包含go_lang配置）Docker的一些常用操作指令 关于Docker和Fabric1.4下载（包含go_lang配置） 00 导言 由 Linux 基金会发起创建的开源区块链分布式账本 —— Hyperledger Fabric，已经迎来了 1.4.0 版本。该项目着重于性能和可靠性，以及推动区块链和分布式账本技术的跨行
【Hyperledger Fabric 开发学习3.2】docker手动部署fabric网络
Herbert
07-02 450
编写文件 创建docker文件夹 在docker文件夹内创建docker-compose.yaml文件(注意文件结构） 部署 orderer0 节点 编辑 文件： 启动 orderer0节点 : 查看日志：部署 orderer1 节点 编辑 orderer.yaml 文件： 启动 orderer1节点 : 查看日志：部署 orderer2 节点 编辑 orderer.yaml 文件： 启动 orderer2 节点 : 查看日志： 查看 orderer 节点进程：启动：org1-peer0 启动： org
Hyperledger Fabric 环境配置之docker和docker-compose指定版本的安装
iijik55的博客
03-25 9123
测试机硬件配置 在Window10系统下，用VMware 15.5软件安装Ubuntu16.04版本的虚拟机，并分配其2GB内存，4个处理器。（后续文章中，如无特别指明，默认是该配置） 注意：上述配置中只需要注意一下虚拟机的版本，其它的如内存、处理器个数按需设置即可 安装指定版本docker，以docker 19.03.5为例 为什么要指定版本呢？ 根据fabric官方文档所示，不同发布版本所需要的环境依赖（这里泛指fabric官方测试案例运行时所需要的各种软件的版本，如：go、docker等）要求不同。因
fabric-explorer的docker
08-26
fabric-explorer的docker镜像可通过以下步骤安装和运行： 1. 首先，打开终端或命令提示符，并在浏览器中输入网址http://localhost:8080，以登录监视浏览器。 2. 接下来，在终端或命令提示符中输入以下命令来启动fabric-explorer的docker容器： ```shell echo "=========== Explorer start Installing ==============" # remove docker container docker rm -f explorer.mynetwork.com docker rm -f explorerdb.mynetwork.com # remove docker volumes docker volume rm artifacts_walletstore docker volume rm artifacts_pgdata # start up the docker container docker-compose up -d echo "=========== Explorer Successfully installed ==============" ``` 3. 之后，进入fabric-explorer的目录，并将fabric网络的crypto-config文件夹复制到该目录下。然后执行以下命令： ```shell cd fabric-explorer cp -R /path/to/crypto-config . touch docker-compose.yaml touch config.json touch connection-profile/test-network.json ``` 4. 最后，在终端或命令提示符中执行以下命令来启动fabric-explorer的docker容器： ```shell docker-compose up -d ``` 这样，fabric-explorer的docker镜像就成功安装并运行了。你可以通过访问http://localhost:8080来访问fabric-explorer，并使用以下登录凭据进行登录： - 用户名：admin - 密码：adminpw 请注意，上述的路径都是相对于docker容器的绝对路径，而不是容器外的路径。你需要根据自己的网络配置进行相应的调整。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* [Fabric-explorer 搭建](https://blog.csdn.net/weixin_41946008/article/details/124609204)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] - *2* *3* [fabric-explorer快速搭建(dockercompose)](https://blog.csdn.net/qq_21553301/article/details/116948043)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

爱写代码的大狼

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值