hyperledge fabric 1.4 单机部署

àì夳堔傛蜴生んèń 2022-02-13 03:51 228阅读 0赞

# hyperledge fabric 1.4 单机部署 #

环境搭建及镜像下载和获取bin目录请看链接：https://blog.csdn.net/xulvejie0143/article/details/89496860
    参考链接： https://www.cnblogs.com/llongst/p/9571321.html
    https://www.jianshu.com/p/e16345cc2cde

\-**1 创建solo-fabric目录及复制bin目录**

![在这里插入图片描述][2019042617313857.png]

*  **2 准备crypto-config.yaml配置文件**  
    该配置文件用来生成证书文件

./bin/cryptogen showtemplate > crypto-config.yaml

用文本编辑器或vi打开，去掉\#注释，并修改成如下

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

*  **3 生成证书文件**

./bin/cryptogen generate --config=./crypto-config.yaml

*  **4 准备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')"
    
        - &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')"
    
            AnchorPeers:
    
                - Host: peer0.org1.example.com
                  Port: 7051
    
    
    Capabilities:
       
        Global: &ChannelCapabilities
            
            V1_1: true
    
        
        Orderer: &OrdererCapabilities
           
            V1_1: true
    
      
        Application: &ApplicationCapabilities
           
            V1_2: true
    
    
    Application: &ApplicationDefaults
    
        
        Organizations:
    
        
        Policies:
            Readers:
                Type: ImplicitMeta
                Rule: "ANY Readers"
            Writers:
                Type: ImplicitMeta
                Rule: "ANY Writers"
            Admins:
                Type: ImplicitMeta
                Rule: "MAJORITY Admins"
    
        
        Capabilities:
            <<: *ApplicationCapabilities
    
    
    Orderer: &OrdererDefaults
    
        
        OrdererType: solo
    
        Addresses:
            - orderer.example.com:7050
    
       
        BatchTimeout: 2s
    
        
        BatchSize:
    
            
            MaxMessageCount: 10
    
            
            AbsoluteMaxBytes: 98 MB
    
            
            PreferredMaxBytes: 512 KB
    
        Kafka:
            
            Brokers:
                - 127.0.0.1:9092
    
        
        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"
    
        
        Capabilities:
            <<: *OrdererCapabilities
    
    
    Channel: &ChannelDefaults
        
        Policies:
            
            Readers:
                Type: ImplicitMeta
                Rule: "ANY Readers"
            
            Writers:
                Type: ImplicitMeta
                Rule: "ANY Writers"
            
            Admins:
                Type: ImplicitMeta
                Rule: "MAJORITY Admins"
    
    
        
        Capabilities:
            <<: *ChannelCapabilities
    
    
    Profiles:
    
        OneOrgsOrdererGenesis:
            <<: *ChannelDefaults
            Orderer:
                <<: *OrdererDefaults
                Organizations:
                    - *OrdererOrg
            Consortiums:
                SampleConsortium:
                    Organizations:
                        - *Org1
        OneOrgsChannel:
            Consortium: SampleConsortium
            Application:
                <<: *ApplicationDefaults
                Organizations:
                    - *Org1

*  **5 生成创世区块**

mkdir channel-artifacts
    ./bin/configtxgen -profile OneOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

*  **6 生成通道文件mychannel.tx**

./bin/configtxgen -profile OneOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel

*  **7 docker-compose.yaml文件**

version: '2'
    
    services:
        orderer.example.com:
            container_name: orderer.example.com
            image: hyperledger/fabric-orderer
            environment:
                - GODEBUG=netdns=go
                - TZ=Asia/Shanghai
                - ORDERER_GENERAL_LOGLEVEL=debug
                - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
                - ORDERER_GENERAL_GENESISMETHOD=file
                - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
                - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
                - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
                # enabled TLS
                - ORDERER_GENERAL_TLS_ENABLED=false
                - 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_OPERATIONS_LISTENADDRESS=orderer.example.com:8443
                - ORDERER_METRICS_PROVIDER=prometheus
            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
                - ./data/orderer/var/hyperledger/:/var/hyperledger/
            ports:
                - 7050:7050
                - 8443:8443
    
        couchdb0:
            container_name: couchdb0
            image: hyperledger/fabric-couchdb
            environment:
                - GODEBUG=netdns=go
                - TZ=Asia/Shanghai
            #    volumes:
            #      - ./data/couchdb/data:/opt/couchdb/data
            ports:
                - 5984:5984
       
        ca0:
            image: hyperledger/fabric-ca
            environment:
                - GODEBUG=netdns=go
                - TZ=Asia/Shanghai
                - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
                - FABRIC_CA_SERVER_CA_NAME=ca-org1
                - FABRIC_CA_SERVER_TLS_ENABLED=true
                - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
                # 替换成你自己./crypto-config/peerOrganizations/org1.example.com/ca/路径下的
                - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/bfd8ee7583e75dc3c64c9403b2f19007dd9e3c5324a814c2eb11890e556dfca9_sk
            ports:
                - 7054:7054
            # 替换成你自己./crypto-config/peerOrganizations/org1.example.com/ca/路径下的
            command: sh -c 'fabric-ca-server start --cfg.affiliations.allowremove --cfg.identities.allowremove --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/bfd8ee7583e75dc3c64c9403b2f19007dd9e3c5324a814c2eb11890e556dfca9_sk -b admin:adminpw -d'
            volumes:
                - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
                - ./data/ca0/:/etc/hyperledger/fabric-ca-server
            container_name: ca_peerOrg1
       
        peer0.org1.example.com:
            container_name: peer0.org1.example.com
            image: hyperledger/fabric-peer
            environment:
                - GODEBUG=netdns=go
                - TZ=Asia/Shanghai
                - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
                - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
                - CORE_PEER_ID=peer0.org1.example.com
                - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
                - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
                - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
                - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
                - CORE_PEER_LOCALMSPID=Org1MSP
    
                - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
                # the following setting starts chaincode containers on the same
                # bridge network as the peers
                # https://docs.docker.com/compose/networking/
                - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=solo-fabric_default
                #- CORE_LOGGING_LEVEL=ERROR
                - CORE_LOGGING_LEVEL=DEBUG
                - CORE_PEER_TLS_ENABLED=false
                - 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_OPERATIONS_LISTENADDRESS=peer0.org1.example.com:9443
                - CORE_METRICS_PROVIDER=prometheus
            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
                - ./data/peer0org1/var/hyperledger/:/var/hyperledger/
            working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
            command: peer node start
            ports:
                - 7051:7051
                - 7052:7052
                - 7053:7053
                - 9443:9443
    
        cli:
            container_name: cli
            image: hyperledger/fabric-tools
            tty: true
            environment:
                - GODEBUG=netdns=go
                - TZ=Asia/Shanghai
                - GOPATH=/opt/gopath
                - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
                - CORE_LOGGING_LEVEL=DEBUG
                - CORE_PEER_ID=cli
                - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
                - CORE_PEER_LOCALMSPID=Org1MSP
                - CORE_PEER_TLS_ENABLED=false
                - 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
            volumes:
                - /var/run/:/host/var/run/
                - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/solo-fabric/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
            depends_on:
                - orderer.example.com
                - peer0.org1.example.com

*  **8 启动fabric网络**

docker-compose -f docker-compose-cli.yaml up -d

启动cli容器

docker exec -it cli bash

创建Channel

peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx

Peer加入Channel

peer channel join -b mychannel.block

*  **9 安装与部署智能合约**  
    准备部署智能合约

> 拷贝examples/chaincode/go/example02目录下的文件到solo-fabric/chaincode/go/example02目录下

安装智能合约

peer chaincode install -n mycc -p github.com/hyperledger/fabric/solo-fabric/chaincode/go/example02 -v 1.0

实例化智能合约 不成功报这个错  
![在这里插入图片描述][20190428152747357.png]

[2019042617313857.png]: /images/20220213/fef6c7896ff0483aa561e985338ad765.png
[20190428152747357.png]: /images/20220213/65c1021d2ec3429aa3dbdab260713959.png