HyperLedger Fabric 1.4 智能合约 Helloworld运行（9）

网易云课堂视频在线教学，地址：https://study.163.com/course/introduction/1209401942.htm

9.1 Helloworld案例简介

通过执行官方End-2-End案例，初始了解Fabric网络的运行流程及yaml配置，官方End-2-End案例把执行过程集成，通过一条命令即可完成全部操作，对于初学者只能了解Fabric网络搭建是否成功，对于Fabric网络的执行细节还是迷惑。
      为了能让初学者全面了解Fabric网络的执行细节，本章通过手动方式搭建一个orderer、一个组织和一个peer的SOLO排序的Fabric网络，把配置独立出来，形成orderer和peer配置等单个yaml文件，通过手动执行orderer和peer搭建Fabric网络。
编写最简单的智能合约，初始化时在区块中存储Hello world字符串，然后通过智能合约可以查询出Hello world字符串，初步了解智能合约编写。
9.2Helloworld链码编写
      Helloworld链码实现Init和Invoke两个接口，通过stub.PutState和stub.GetState保存和获取链值对数据。

• Init(stub shim.ChaincodeStubInterface)：用于智能合约初始化及升级初始化,实现初始化时保存链值对；
• Invoke(stub shim.ChaincodeStubInterface)：是节点（peer）调用链码的入口函数，实现对账本进行保存和获取链值对；

　　实现两个文件,分别chaincode.go和cmd/ main.go，main.go是主入口函数　　

具体代码如下：

• main.go:

/*

 *

 * 文件名称 : main.go

 * 创建者 : linwf

 * 创建日期: 2018/08/23

 * 文件描述: 主入口函数

 * 历史记录: 无

 */

package main

import (

    "fmt"

    "github.com/hyperledger/fabric/core/chaincode/shim"

    "github.com/hyperledger/fabric/helloworld/chaincode/go/helloworld"

)

func main() {

    err := shim.Start(new(helloworld.SimpleChaincode))

    if err != nil {

        fmt.Printf("Error starting Simple chaincode: %s", err)

    }

}

• chaincode.go

/*

 *

 * 文件名称 : chaincode.go

 * 创建者 : linwf

 * 创建日期: 2018/08/23

 * 文件描述: 实现存储Helloworld字符串的智能合约

 * 历史记录: 无

 */

package helloworld

import (

	"fmt"

	"github.com/hyperledger/fabric/core/chaincode/shim"

	pb "github.com/hyperledger/fabric/protos/peer"

)

// SimpleChaincode implements a simple chaincode to manage an asset

type SimpleChaincode struct {

}

// 链码实例化时，调用Init函数初始化数据

// 链码升级时，也会调用此函数重置或迁移数据

func (t *SimpleChaincode) Init(stub shim.ChaincodeStubInterface) pb.Response {

	// 获取交易提案中的参数

	args := stub.GetStringArgs()

	if len(args) != 2 {

		return shim.Error("Incorrect arguments. Expecting a key and a value")

	}

	// 通过调用stub.PutState()设置变量和数值

	// 在账本上设置key和value

	err := stub.PutState(args[0], []byte(args[1]))

	if err != nil {

		return shim.Error(fmt.Sprintf("Failed to create asset: %s", args[0]))

	}

	return shim.Success(nil)

}

// 调用Invoke函数进行资产交易

// 每笔交易通过get或set操作Init函数创建的key和value

// 通过set可以创建新的key和value

func (t *SimpleChaincode) Invoke(stub shim.ChaincodeStubInterface) pb.Response {

	// 获取交易提案中的函数和参数

	fn, args := stub.GetFunctionAndParameters()

	var result string

	var err error

	if fn == "set" {

		result, err = set(stub, args)

	} else { // assume 'get' even if fn is nil

		result, err = get(stub, args)

	}

	if err != nil {

		return shim.Error(err.Error())

	}

	// Return the result as success payload

	return shim.Success([]byte(result))

}

// 保存key和value到账本上

// 如果key存在，覆盖原有的value

func set(stub shim.ChaincodeStubInterface, args []string) (string, error) {

	if len(args) != 2 {

		return "", fmt.Errorf("Incorrect arguments. Expecting a key and a value")

	}

	err := stub.PutState(args[0], []byte(args[1]))

	if err != nil {

		return "", fmt.Errorf("Failed to set asset: %s", args[0])

	}

	return args[1], nil

}

// 获取key对应的value

func get(stub shim.ChaincodeStubInterface, args []string) (string, error) {

	if len(args) != 1 {

		return "", fmt.Errorf("Incorrect arguments. Expecting a key")

	}

	value, err := stub.GetState(args[0])

	if err != nil {

		return "", fmt.Errorf("Failed to get asset: %s with error: %s", args[0], err)

	}

	if value == nil {

		return "", fmt.Errorf("Asset not found: %s", args[0])

	}

	return string(value), nil

}

9.3 Helloworld案例运行
9.3.1创建helloworld目录

# cd $GOPATH/src/github.com/hyperledger/fabric

# mkdir helloworld

# cd helloworld

9.3.2 获取“cryptogen”和“configtxgen”工具
       访问网址：https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.4.0/，下载“cryptogen”和“configtxgen”等工具的二进制文件包hyperledger-fabric-linux-amd64-1.4.0.tar.gz，解压后把bin目录拷贝到helloworld目录下。Bin目录下的文件如下图所示：

图：bin目录文件

# chmod -R  ./bin

9.3.3 准备生成证书和区块配置文件

配置crypto-config.yaml和configtx.yaml文件，拷贝到helloworld目录下。

• crypto-config.yaml：

# Copyright IBM Corp. All Rights Reserved.

#

# SPDX-License-Identifier: Apache-2.0

#

# ---------------------------------------------------------------------------

# "OrdererOrgs" - Definition of organizations managing orderer nodes

# ---------------------------------------------------------------------------

OrdererOrgs:

  # ---------------------------------------------------------------------------

  # Orderer

  # ---------------------------------------------------------------------------

  - Name: Orderer

    Domain: example.com

    CA:

        Country: US

        Province: California

        Locality: San Francisco

    # ---------------------------------------------------------------------------

    # "Specs" - See PeerOrgs below for complete description

    # ---------------------------------------------------------------------------

    Specs:

      - Hostname: orderer

# ---------------------------------------------------------------------------

# "PeerOrgs" - Definition of organizations managing peer nodes

# ---------------------------------------------------------------------------

PeerOrgs:

  # ---------------------------------------------------------------------------

  # Org1

  # ---------------------------------------------------------------------------

  - Name: Org1

    Domain: org1.example.com

    EnableNodeOUs: true

    CA:

        Country: US

        Province: California

        Locality: San Francisco

    # ---------------------------------------------------------------------------

    # "Specs"

    # ---------------------------------------------------------------------------

    # Uncomment this section to enable the explicit definition of hosts in your

    # configuration.  Most users will want to use Template, below

    #

    # Specs is an array of Spec entries.  Each Spec entry consists of two fields:

    #   - Hostname:   (Required) The desired hostname, sans the domain.

    #   - CommonName: (Optional) Specifies the template or explicit override for

    #                 the CN.  By default, this is the template:

    #

    #                              "{{.Hostname}}.{{.Domain}}"

    #

    #                 which obtains its values from the Spec.Hostname and

    #                 Org.Domain, respectively.

    # ---------------------------------------------------------------------------

    # Specs:

    #   - Hostname: foo # implicitly "foo.org1.example.com"

    #     CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above

    #   - Hostname: bar

    #   - Hostname: baz

    # ---------------------------------------------------------------------------

    # "Template"

    # ---------------------------------------------------------------------------

    # Allows for the definition of  or more hosts that are created sequentially

    # from a template. By default, this looks like "peer%d" from  to Count-.

    # You may override the number of nodes (Count), the starting index (Start)

    # or the template used to construct the name (Hostname).

    #

    # Note: Template and Specs are not mutually exclusive.  You may define both

    # sections and the aggregate nodes will be created for you.  Take care with

    # name collisions

    # ---------------------------------------------------------------------------

    Template:

      Count:

      # Start:

      # Hostname: {{.Prefix}}{{.Index}} # default

    # ---------------------------------------------------------------------------

    # "Users"

    # ---------------------------------------------------------------------------

    # Count: The number of user accounts _in addition_ to Admin

    # ---------------------------------------------------------------------------

    Users:

      Count: 

• configtx.yaml：

# Copyright IBM Corp. All Rights Reserved.

#

# SPDX-License-Identifier: Apache-2.0

#

---

################################################################################

#

#   Section: Organizations

#

#   - This section defines the different organizational identities which will

#   be referenced later in the configuration.

#

################################################################################

Organizations:

    # SampleOrg defines an MSP using the sampleconfig.  It should never be used

    # in production but may be used as a template for other definitions

    - &OrdererOrg

        # DefaultOrg defines the organization which is used in the sampleconfig

        # of the fabric.git development environment

        Name: OrdererOrg

        # ID to load the MSP definition as

        ID: OrdererMSP

        # MSPDir is the filesystem path which contains the MSP configuration

        MSPDir: crypto-config/ordererOrganizations/example.com/msp

        # Policies defines the set of policies at this level of the config tree

        # For organization policies, their canonical path is usually

        #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>

        Policies:

            Readers:

                Type: Signature

                Rule: "OR('OrdererMSP.member')"

            Writers:

                Type: Signature

                Rule: "OR('OrdererMSP.member')"

            Admins:

                Type: Signature

                Rule: "OR('OrdererMSP.admin')"

    - &Org1

        # DefaultOrg defines the organization which is used in the sampleconfig

        # of the fabric.git development environment

        Name: Org1MSP

        # ID to load the MSP definition as

        ID: Org1MSP

        MSPDir: crypto-config/peerOrganizations/org1.example.com/msp

        # Policies defines the set of policies at this level of the config tree

        # For organization policies, their canonical path is usually

        #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>

        Policies:

            Readers:

                Type: Signature

                Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"

            Writers:

                Type: Signature

                Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"

            Admins:

                Type: Signature

                Rule: "OR('Org1MSP.admin')"

        AnchorPeers:

            # AnchorPeers defines the location of peers which can be used

            # for cross org gossip communication.  Note, this value is only

            # encoded in the genesis block in the Application section context

            - Host: peer0.org1.example.com

              Port:

################################################################################

#

#   SECTION: Capabilities

#

#   - This section defines the capabilities of fabric network. This is a new

#   concept as of v1.1.0 and should not be utilized in mixed networks with

#   v1..x peers and orderers.  Capabilities define features which must be

#   present in a fabric binary for that binary to safely participate in the

#   fabric network.  For instance, if a new MSP type is added, newer binaries

#   might recognize and validate the signatures from this type, while older

#   binaries without this support would be unable to validate those

#   transactions.  This could lead to different versions of the fabric binaries

#   having different world states.  Instead, defining a capability for a channel

#   informs those binaries without this capability that they must cease

#   processing transactions until they have been upgraded.  For v1..x if any

#   capabilities are defined (including a map with all capabilities turned off)

#   then the v1..x peer will deliberately crash.

#

################################################################################

Capabilities:

    # Channel capabilities apply to both the orderers and the peers and must be

    # supported by both.  Set the value of the capability to true to require it.

    Global: &ChannelCapabilities

        # V1. for Global is a catchall flag for behavior which has been

        # determined to be desired for all orderers and peers running v1..x,

        # but the modification of which would cause incompatibilities.  Users

        # should leave this flag set to true.

        V1_1: true

    # Orderer capabilities apply only to the orderers, and may be safely

    # manipulated without concern for upgrading peers.  Set the value of the

    # capability to true to require it.

    Orderer: &OrdererCapabilities

        # V1. for Order is a catchall flag for behavior which has been

        # determined to be desired for all orderers running v1..x, but the

        # modification of which  would cause incompatibilities.  Users should

        # leave this flag set to true.

        V1_1: true

    # Application capabilities apply only to the peer network, and may be safely

    # manipulated without concern for upgrading orderers.  Set the value of the

    # capability to true to require it.

    Application: &ApplicationCapabilities

        # V1. for Application is a catchall flag for behavior which has been

        # determined to be desired for all peers running v1..x, but the

        # modification of which would cause incompatibilities.  Users should

        # leave this flag set to true.

        V1_2: true

################################################################################

#

#   SECTION: Application

#

#   - This section defines the values to encode into a config transaction or

#   genesis block for application related parameters

#

################################################################################

Application: &ApplicationDefaults

    # Organizations is the list of orgs which are defined as participants on

    # the application side of the network

    Organizations:

    # Policies defines the set of policies at this level of the config tree

    # For Application policies, their canonical path is

    #   /Channel/Application/<PolicyName>

    Policies:

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

    # Capabilities describes the application level capabilities, see the

    # dedicated Capabilities section elsewhere in this file for a full

    # description

    Capabilities:

        <<: *ApplicationCapabilities

################################################################################

#

#   SECTION: Orderer

#

#   - This section defines the values to encode into a config transaction or

#   genesis block for orderer related parameters

#

################################################################################

Orderer: &OrdererDefaults

    # Orderer Type: The orderer implementation to start

    # Available types are "solo" and "kafka"

    OrdererType: solo

    Addresses:

        - orderer.example.com:

    # Batch Timeout: The amount of time to wait before creating a batch

    BatchTimeout: 2s

    # Batch Size: Controls the number of messages batched into a block

    BatchSize:

        # Max Message Count: The maximum number of messages to permit in a batch

        MaxMessageCount:

        # Absolute Max Bytes: The absolute maximum number of bytes allowed for

        # the serialized messages in a batch.

        AbsoluteMaxBytes:  MB

        # Preferred Max Bytes: The preferred maximum number of bytes allowed for

        # the serialized messages in a batch. A message larger than the preferred

        # max bytes will result in a batch larger than preferred max bytes.

        PreferredMaxBytes:  KB

    Kafka:

        # Brokers: A list of Kafka brokers to which the orderer connects. Edit

        # this list to identify the brokers of the ordering service.

        # NOTE: Use IP:port notation.

        Brokers:

            - 127.0.0.1:

    # Organizations is the list of orgs which are defined as participants on

    # the orderer side of the network

    Organizations:

    # Policies defines the set of policies at this level of the config tree

    # For Orderer policies, their canonical path is

    #   /Channel/Orderer/<PolicyName>

    Policies:

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

        # BlockValidation specifies what signatures must be included in the block

        # from the orderer for the peer to validate it.

        BlockValidation:

            Type: ImplicitMeta

            Rule: "ANY Writers"

    # Capabilities describes the orderer level capabilities, see the

    # dedicated Capabilities section elsewhere in this file for a full

    # description

    Capabilities:

        <<: *OrdererCapabilities

################################################################################

#

#   CHANNEL

#

#   This section defines the values to encode into a config transaction or

#   genesis block for channel related parameters.

#

################################################################################

Channel: &ChannelDefaults

    # Policies defines the set of policies at this level of the config tree

    # For Channel policies, their canonical path is

    #   /Channel/<PolicyName>

    Policies:

        # Who may invoke the 'Deliver' API

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        # Who may invoke the 'Broadcast' API

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        # By default, who may modify elements at this config level

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

    # Capabilities describes the channel level capabilities, see the

    # dedicated Capabilities section elsewhere in this file for a full

    # description

    Capabilities:

        <<: *ChannelCapabilities

################################################################################

#

#   Profile

#

#   - Different configuration profiles may be encoded here to be specified

#   as parameters to the configtxgen tool

#

################################################################################

Profiles:

    OneOrgsOrdererGenesis:

        <<: *ChannelDefaults

        Orderer:

            <<: *OrdererDefaults

            Organizations:

                - *OrdererOrg

        Consortiums:

            SampleConsortium:

                Organizations:

                    - *Org1

    OneOrgsChannel:

        Consortium: SampleConsortium

        Application:

            <<: *ApplicationDefaults

            Organizations:

                - *Org1

9.3.4 生成公私钥和证书

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

9.3.5 生成创世区块

# mkdir channel-artifacts

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

9.3.6 生成通道（Channel）配置区块

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

9.3.7 准备docker配置文件
配置docker-orderer.yaml和 docker-peer.yaml文件，拷贝到helloworld目录下。

• docker-orderer.yaml：

version: ''

services:

orderer.example.com:

container_name: orderer.example.com

image: hyperledger/fabric-orderer

environment:

- 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=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]

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:

- :

    docker-peer.yaml：

version: ''

services:

peer0.org1.example.com:

container_name: peer0.org1.example.com

image: hyperledger/fabric-peer

environment:

- CORE_PEER_ID=peer0.org1.example.com

- CORE_PEER_ADDRESS=peer0.org1.example.com:

- CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:

- CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:

- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:

- 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=helloworld_default

#- CORE_LOGGING_LEVEL=ERROR

- CORE_LOGGING_LEVEL=DEBUG

- CORE_PEER_TLS_ENABLED=true

- CORE_PEER_GOSSIP_USELEADERELECTION=true

- CORE_PEER_GOSSIP_ORGLEADER=false

- CORE_PEER_PROFILE_ENABLED=true

- CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt

- CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key

- CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

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

working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

command: peer node start

ports:

- :

- :

- :

extra_hosts:

- "orderer.example.com:192.168.235.131"

cli:

container_name: cli

image: hyperledger/fabric-tools

tty: true

environment:

- 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:

- 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/[email protected]/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/helloworld/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:

- peer0.org1.example.com

extra_hosts:

- "orderer.example.com:192.168.235.131"

• docker-peer.yaml：

version: ''

services:

  peer0.org1.example.com:

    container_name: peer0.org1.example.com

    image: hyperledger/fabric-peer

    environment:

      - CORE_PEER_ID=peer0.org1.example.com

      - CORE_PEER_ADDRESS=peer0.org1.example.com:

      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:

      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:

      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:

      - 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=helloworld_default

      #- CORE_LOGGING_LEVEL=ERROR

      - CORE_LOGGING_LEVEL=DEBUG

      - CORE_PEER_TLS_ENABLED=true

      - CORE_PEER_GOSSIP_USELEADERELECTION=true

      - CORE_PEER_GOSSIP_ORGLEADER=false

      - CORE_PEER_PROFILE_ENABLED=true

      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt

      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key

      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

    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

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

    command: peer node start

    ports:

      - :

      - :

      - :

    extra_hosts:

      - "orderer.example.com:192.168.235.131"

  cli:

    container_name: cli

    image: hyperledger/fabric-tools

    tty: true

    environment:

      - 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:

      - 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/[email protected]/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/helloworld/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:

      - peer0.org1.example.com

    extra_hosts:

      - "orderer.example.com:192.168.235.131"

9.3.8 准备部署智能合约
       拷贝编写好的智能合约文件到helloworld/ chaincode/go/helloworld目录下。

9.3.9 启动Fabric网络
1）启动orderer

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

2） 启动peer

# docker-compose -f docker-peer.yaml up -d

3） 启动cli容器

# docker exec -it cli bash

4） 创建Channel

# ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

# peer channel create -o orderer.example.com: -c mychannel -f ./channel-artifacts/mychannel.tx --tls --cafile $ORDERER_CA

5） Peer加入Channel

# peer channel join -b mychannel.block

9.3.10 安装与运行智能合约
1）安装智能合约

# peer chaincode install -n mycc -p github.com/hyperledger/fabric/helloworld/chaincode/go/helloworld/cmd -v 1.0

2） 实例化智能合约

# peer chaincode instantiate -o orderer.example.com: --tls --cafile $ORDERER_CA -C mychannel -n mycc -v 1.0 -c '{"Args":["a","helloworld"]}' -P "OR ('Org1MSP.peer')"

3） Peer上查询A，显示Helloworld

# peer chaincode query -C mychannel -n mycc -c '{"Args":["get","a"]}'

完成后显示如下图所示：

图：Helloworld完成图