Hyperledger Fabric 1.2环境搭建

准备工作

1. 官方帮助文档：https://hyperledger-fabric.readthedocs.io/en/release-1.2/
2. 安装 cURL(https://curl.haxx.se/download.html),curl --version 查询版本
3. 安装docker，docker --version 查询版本
4. 安装docker-compose,docker-compose --version 查询版本
5. 安装 go 语言环境，go version 查询版本
6. 安装node.js, node -v 查询版本
7. Python 版本要求为 2.7，python --version 查询版本

1.1 安装docker

1. 基础软件安装

   # 安装基本软件
   $ sudo apt-get update
   $ sudo apt-get install apt-transport-https ca-certificates curl git software-properties-common lrzsz -y
   

2. 添加阿里的docker镜像仓库

   # 添加阿里的docker镜像仓库
   $ curl -fsSL https://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
   $ sudo add-apt-repository "deb [arch=amd64] https://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
   # 更新软件源
   $ sudo apt-get update
   

3. 安装docker

    $ sudo apt-get install docker-ce -y

查看安装的docker版本

$ docker version
	Client:
         Version:           18.06.1-ce
         API version:       1.38
         Go version:        go1.10.3
         Git commit:        e68fc7a
         Built:             Tue Aug 21 17:24:51 2018
         OS/Arch:           linux/amd64
         Experimental:      false
    Got permission denied while trying to connect to the Docker daemon socket at
    unix:///var/run/docker.sock: Get
    http://%2Fvar%2Frun%2Fdocker.sock/v1.38/version: 
    dial unix /var/run/docker.sock: connect: `permission denied`
# 当前用户直接操作docker时, 权限不够, 需要做下面的第4不操作

4.将当前用户添加到docker组

#将用户加入该 group 内。然后退出并重新登录就生效啦。
$ sudo gpasswd -a ${USER} docker
 #重启docker服务
$ systemctl restart docker
#当前用户切换到docker群组

$ newgrp - docker
$ docker version
	Client:
         Version:           18.06.1-ce
         API version:       1.38
         Go version:        go1.10.3
         Git commit:        e68fc7a
         Built:             Tue Aug 21 17:24:51 2018
         OS/Arch:           linux/amd64
         Experimental:      false

    Server:
         Engine:
         Version:          18.06.1-ce
         API version:      1.38 (minimum version 1.12)
         Go version:       go1.10.3
         Git commit:       e68fc7a
         Built:            Tue Aug 21 17:23:15 2018
         OS/Arch:          linux/amd64
         Experimental:     false

5.安装docker-compose

#安装依赖工具
$ sudo apt-get install python-pip -y
#安装编排工具
$ sudo pip install docker-compose
#查看版本
$ sudo docker-compose version

1.2 安装go

# 安装包下载地址:
https://golang.org/dl/  - 
https://studygolang.com/dl - 国内镜像源

# 1. 使用wget工具下载安装包
$ wget https://dl.google.com/go/go1.11.linux-amd64.tar.gz
# 2. 解压tar包到/usr/local
$ sudo tar zxvf go1.11.linux-amd64.tar.gz -C /usr/local
# 3. 创建Go目录
$ mkdir $HOME/go
# 4. 用vi打开~./bashrc，配置环境变量
$ vim ~/.bashrc
# 5. 增加下面的环境变量，保存退出
	export GOROOT=/usr/local/go
    export GOPATH=$HOME/go
    export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
# 6. 使环境变量立即生效, 一些命令二选一
$ source ~/.bashrc  
$ . ~/.bashrc
# 7. 检测go是否安装好
$ go version

1.3 安装Node.js

1.官方下载地址

https://nodejs.org/en/download/

1. 下载二进制源码包

   $ wget https://nodejs.org/dist/v8.11.4/node-v8.11.4-linux-x64.tar.xz
   

2. 解压并安装

   # 指定压缩包解压到/opt目录下
   $ sudo tar xvf node-v8.11.4-linux-x64.tar.xz -C /opt
   	- 在/opt目录下得到 node-v8.11.4-linux-x64 目录
   

3. 将node.js设置为全局可用

   # 打开系统级别的配置文件 /etc/profile
   $ sudo vim /etc/profile
   # 添加如下配置项, 保存退出
       export NODEJS_HOME=/opt/node-v8.11.4-linux-x64
       export PATH=$PATH:$NODEJS_HOME/bin
   # 重新加载配置文件
   $ . /etc/profile
   

4. 测试

$ node -v

1.4 部署hyperledger Fabric

1.下载并执行fabric的引导脚本bootstrap.sh

# 创建放置的目录，然后进入该目录，用curl下载脚本。
$ cd ~ # 这里在家目录下创建放置目录
$ mkdir hyperledger-fabric # 创建放置目录
$ cd hyperledger-fabric
# 下载并执行脚本, [ ***语法格式*** ] - 
# 下边是具体的执行命令 - 看我
# 下边是具体的执行命令 - 看我
# 下边是具体的执行命令 -- 重要的事情说三遍, 使用下边不的命令
$ curl -sSL http://bit.ly/2ysbOFE | bash -s   
	- fabric: fabric的版本
	- fabric-ca: fabric-ca的版本
	- thirdparty: 第三方库的版本
# 下载并执行脚本, [ ***需要, 需要, 需要, 需要, 需要,*** ]
$ curl -sSL http://bit.ly/2ysbOFE | bash -s 1.2.0 1.2.0 0.4.10
	- http://bit.ly/2ysbOFE: 该地址必须才能访问
# ***不的方式***
$ curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash -s 1.2.0 1.2.0 0.4.10
# 该脚本启动之后会下载两个压缩包和一些镜像文件, 整个过程会比较长, 耐心等待...
# 温馨提示: 这个过程会让你产生想要砸电脑的冲动, 控制好你的情绪!!!!
# 上述命令刚开始会下载以下两个压缩包, 这两个包下载速度特别慢慢慢慢慢慢慢.......
# 	1. hyperledger-fabric-linux-amd64-1.2.0.tar.gz
# 	2. hyperledger-fabric-ca-linux-amd64-1.2.0.tar.gz
以上两个压缩包下载下来之后会被解压, 解压目录:
~/hyperledger-fabric/fabric-samples
可以将事先下载好的两个压缩包放到该目录下, 提高下载速度 (强烈建议), 放好之后再重新执行上边的curl命令
``

**通过上述操作拉取的docker镜像为:**

> hyperledger/fabric-peerpeer   模块镜像文件
> hyperledger/fabric-ordererorderer  节点库镜像文件
> hyperledger/fabric-ccenv   Go语言chaincode运行环境库镜像文件hyperledger/fabric-tools   相关工具镜像文件包含了cryptogen,
> configtxgen等工具 hyperledger/fabric-caCA  模块镜像文件
> hyperledger/fabric-couchdbcouchdb数据库镜像文件
> hyperledger/fabric-kafkakafka   库镜像文件
> hyperledger/fabric-zookeeper    zookeeper库镜像文件


**2.设置全局访问**
````shell
# 进入到 ~/hyperledger-fabric/fabric-samples/bin 目录
$ cd ~/hyperledger-fabric/fabric-samples/bin
itcast@ubuntu:~/hyperledger-fabric/fabric-samples/bin$ tree
    .
    ├── configtxgen
    ├── configtxlator
    ├── cryptogen
    ├── discover
    ├── fabric-ca-client
    ├── get-docker-images.sh
    ├── idemixgen
    ├── orderer
    └── peer
# 将这些二进制文件拷贝到 /usr/local/bin 目录下
$ sudo cp * /usr/local/bin
# 执行完上述操作之后, fabric的这些可执行程序就可以在全局范围内使用了

1.5 First-Network 环境测试

1.5.1 生成相应文件

执行 ./byfn.sh generate 命令生成相应的文件

$ cd ~/hyperledger-fabric/fabric-samples/first-network/
$ ./byfn.sh generate	

Generating certs and genesis block for channel ‘mychannel’ with CLI
timeout of ‘10’ seconds and CLI delay of ‘3’ seconds Continue? [Y/n] y
proceeding …
/home/zoro/hyperledger-fabric/fabric-samples/first-network/…/bin/cryptogen

Generate certificates using cryptogen
tool

• cryptogen generate --config=./crypto-config.yaml org1.example.com org2.example.com
• res=0
• set +x

/home/zoro/hyperledger-fabric/fabric-samples/first-network/…/bin/configtxgen

Generating Orderer Genesis block

• configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block 2018-09-23 11:03:32.183 CST [common/tools/configtxgen] main -> WARN 001 Omitting
  the channel ID for configtxgen is deprecated. Explicitly passing the
  channel ID will be required in the future, defaulting to
  ‘testchainid’. 2018-09-23 11:03:32.183 CST
  [common/tools/configtxgen] main -> INFO 002 Loading configuration
  2018-09-23 11:03:32.190 CST [common/tools/configtxgen/encoder]
  NewChannelGroup -> WARN 003 Default policy emission is deprecated,
  please include policy specificiations for the channel group in
  configtx.yaml 2018-09-23 11:03:32.191 CST
  [common/tools/configtxgen/encoder] NewOrdererGroup -> WARN 004 Default
  policy emission is deprecated, please include policy specificiations
  for the orderer group in configtx.yaml 2018-09-23 11:03:32.191 CST
  [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 005
  Default policy emission is deprecated, please include policy
  specificiations for the orderer org group OrdererOrg in configtx.yaml
  2018-09-23 11:03:32.192 CST [msp] getMspConfig -> INFO 006 Loading
  NodeOUs 2018-09-23 11:03:32.192 CST
  [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 007
  Default policy emission is deprecated, please include policy
  specificiations for the orderer org group Org1MSP in configtx.yaml
  2018-09-23 11:03:32.193 CST [msp] getMspConfig -> INFO 008 Loading
  NodeOUs 2018-09-23 11:03:32.193 CST
  [common/tools/configtxgen/encoder] NewOrdererOrgGroup -> WARN 009
  Default policy emission is deprecated, please include policy
  specificiations for the orderer org group Org2MSP in configtx.yaml
  2018-09-23 11:03:32.193 CST [common/tools/configtxgen] doOutputBlock
  -> INFO 00a Generating genesis block 2018-09-23 11:03:32.194 CST [common/tools/configtxgen] doOutputBlock -> INFO 00b Writing genesis
  block
• res=0
• set +x

Generating channel configuration
transaction ‘channel.tx’

• configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel 2018-09-23 11:03:32.238 CST [common/tools/configtxgen] main -> INFO 001 Loading configuration
  2018-09-23 11:03:32.252 CST [common/tools/configtxgen]
  doOutputChannelCreateTx -> INFO 002 Generating new channel configtx
  2018-09-23 11:03:32.253 CST [common/tools/configtxgen/encoder]
  NewApplicationGroup -> WARN 003 Default policy emission is deprecated,
  please include policy specificiations for the application group in
  configtx.yaml 2018-09-23 11:03:32.253 CST [msp] getMspConfig -> INFO
  004 Loading NodeOUs 2018-09-23 11:03:32.254 CST
  [common/tools/configtxgen/encoder] NewApplicationOrgGroup -> WARN 005
  Default policy emission is deprecated, please include policy
  specificiations for the application org group Org1MSP in configtx.yaml
  2018-09-23 11:03:32.254 CST [msp] getMspConfig -> INFO 006 Loading
  NodeOUs 2018-09-23 11:03:32.254 CST
  [common/tools/configtxgen/encoder] NewApplicationOrgGroup -> WARN 007
  Default policy emission is deprecated, please include policy
  specificiations for the application org group Org2MSP in configtx.yaml
  2018-09-23 11:03:32.257 CST [common/tools/configtxgen]
  doOutputChannelCreateTx -> INFO 008 Writing new channel tx
• res=0
• set +x

Generating anchor peer update for
Org1MSP

• configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP 2018-09-23 11:03:32.298 CST [common/tools/configtxgen] main -> INFO 001 Loading
  configuration 2018-09-23 11:03:32.307 CST [common/tools/configtxgen]
  doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
  2018-09-23 11:03:32.307 CST [common/tools/configtxgen]
  doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer update
• res=0
• set +x

Generating anchor peer update for
Org2MSP

• configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP 2018-09-23 11:03:32.350 CST [common/tools/configtxgen] main -> INFO 001 Loading
  configuration 2018-09-23 11:03:32.362 CST [common/tools/configtxgen]
  doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
  2018-09-23 11:03:32.363 CST [common/tools/configtxgen]
  doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer update
• res=0
• set +x

1.5.2 启动网路

执行 ./byfn.sh up 启动网络

# byfn == build your first network
$ ./byfn.sh up

当我们看到START的时候，表示启动成功。 Starting for channel ‘mychannel’ with CLI
timeout of ‘10’ seconds and CLI delay of ‘3’ seconds Continue? [Y/n] y
proceeding … LOCAL_VERSION=1.2.0 DOCKER_IMAGE_VERSION=1.2.0 Creating
network “net_byfn” with the default driver Creating volume
“net_peer0.org2.example.com” with default driver Creating volume
“net_peer1.org2.example.com” with default driver Creating volume
“net_peer1.org1.example.com” with default driver Creating volume
“net_peer0.org1.example.com” with default driver Creating volume
“net_orderer.example.com” with default driver Creating
peer1.org1.example.com … done Creating peer0.org1.example.com …
done Creating peer0.org2.example.com … done Creating
orderer.example.com … done Creating peer1.org2.example.com …
done Creating cli … done

​
START

Build your first network (BYFN) end-to-end test

Channel name : mychannel Creating channel…

• 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/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
• res=0
• set +x 2018-09-23 03:03:55.350 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:03:55.420 UTC [cli/common] readBlock -> INFO 002 Got status:
  &{NOT_FOUND} 2018-09-23 03:03:55.422 UTC [channelCmd] InitCmdFactory
  -> INFO 003 Endorser and orderer connections initialized 2018-09-23 03:03:55.629 UTC [cli/common] readBlock -> INFO 004 Received block: 0
  ===================== Channel ‘mychannel’ created =====================

Having all peers join the channel…

• peer channel join -b mychannel.block
• res=0
• set +x 2018-09-23 03:03:55.699 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:03:55.807 UTC [channelCmd] executeJoin -> INFO 002 Successfully
  submitted proposal to join channel ===================== peer0.org1
  joined channel ‘mychannel’ =====================
• peer channel join -b mychannel.block
• res=0
• set +x 2018-09-23 03:03:58.874 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:03:58.976 UTC [channelCmd] executeJoin -> INFO 002 Successfully
  submitted proposal to join channel ===================== peer1.org1
  joined channel ‘mychannel’ =====================
• peer channel join -b mychannel.block
• res=0
• set +x 2018-09-23 03:04:02.058 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:04:02.169 UTC [channelCmd] executeJoin -> INFO 002 Successfully
  submitted proposal to join channel ===================== peer0.org2
  joined channel ‘mychannel’ =====================
• peer channel join -b mychannel.block
• res=0
• set +x 2018-09-23 03:04:05.231 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:04:05.339 UTC [channelCmd] executeJoin -> INFO 002 Successfully
  submitted proposal to join channel ===================== peer1.org2
  joined channel ‘mychannel’ =====================

Updating anchor peers for org1…

• peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --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
• res=0
• set +x 2018-09-23 03:04:08.406 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:04:08.422 UTC [channelCmd] update -> INFO 002 Successfully
  submitted channel update ===================== Anchor peers updated
  for org ‘Org1MSP’ on channel ‘mychannel’ =====================

Updating anchor peers for org2…

• peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx --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
• res=0
• set +x 2018-09-23 03:04:11.503 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized 2018-09-23
  03:04:11.519 UTC [channelCmd] update -> INFO 002 Successfully
  submitted channel update ===================== Anchor peers updated
  for org ‘Org2MSP’ on channel ‘mychannel’ =====================

Installing chaincode on peer0.org1…

• peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
• res=0
• set +x 2018-09-23 03:04:14.610 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc 2018-09-23
  03:04:14.610 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002
  Using default vscc 2018-09-23 03:04:15.000 UTC [chaincodeCmd]
  install -> INFO 003 Installed remotely response: payload:“OK” > ===================== Chaincode is installed on
  peer0.org1 =====================

Install chaincode on peer0.org2…

• peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
• res=0
• set +x 2018-09-23 03:04:15.069 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc 2018-09-23
  03:04:15.069 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002
  Using default vscc 2018-09-23 03:04:15.203 UTC [chaincodeCmd]
  install -> INFO 003 Installed remotely response: payload:“OK” > ===================== Chaincode is installed on
  peer0.org2 =====================

Instantiating chaincode on peer0.org2…

• peer chaincode instantiate -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 mycc -l golang -v 1.0 -c ‘{“Args”:[“init”,“a”,“100”,“b”,“200”]}’ -P ‘AND
  (’’‘Org1MSP.peer’’’,’’‘Org2MSP.peer’’’)’
• res=0
• set +x 2018-09-23 03:04:15.284 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc 2018-09-23
  03:04:15.284 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002
  Using default vscc ===================== Chaincode is instantiated
  on peer0.org2 on channel ‘mychannel’ =====================

Querying chaincode on peer0.org1…
===================== Querying on peer0.org1 on channel ‘mychannel’… ===================== Attempting to Query peer0.org1 …3 secs

• peer chaincode query -C mychannel -n mycc -c ‘{“Args”:[“query”,“a”]}’
• res=0
• set +x

100
===================== Query successful on peer0.org1 on channel ‘mychannel’ ===================== Sending invoke transaction on
peer0.org1 peer0.org2…

• 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 mycc --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
  -c ‘{“Args”:[“invoke”,“a”,“b”,“10”]}’
• res=0
• set +x 2018-09-23 03:05:17.876 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful.
  result: status:200 ===================== Invoke transaction
  successful on peer0.org1 peer0.org2 on channel ‘mychannel’
  =====================

Installing chaincode on peer1.org2…

• peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
• res=0
• set +x 2018-09-23 03:05:17.966 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc 2018-09-23
  03:05:17.966 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002
  Using default vscc 2018-09-23 03:05:18.340 UTC [chaincodeCmd]
  install -> INFO 003 Installed remotely response: payload:“OK” > ===================== Chaincode is installed on
  peer1.org2 =====================

Querying chaincode on peer1.org2…
===================== Querying on peer1.org2 on channel ‘mychannel’… ===================== Attempting to Query peer1.org2 …3 secs

• peer chaincode query -C mychannel -n mycc -c ‘{“Args”:[“query”,“a”]}’
• res=0
• set +x

90
===================== Query successful on peer1.org2 on channel ‘mychannel’ =====================

========= All GOOD, BYFN execution completed ===========

​
END

执行结束，显示END
1.通过docker ps命令可以查看到节点的启动情况。

$ docker ps

2.如果我们要停止网络，可以执行./byfn.sh down 命令来停止

$ ./byfn.sh down

Stopping for channel ‘mychannel’ with CLI timeout of ‘10’ seconds and
CLI delay of ‘3’ seconds Continue? [Y/n] y proceeding … Stopping cli
… done Stopping orderer.example.com … done Stopping
peer1.org2.example.com … done Stopping peer1.org1.example.com …
done Stopping peer0.org2.example.com … done Stopping
peer0.org1.example.com … done Removing cli …
done Removing orderer.example.com … done Removing
peer1.org2.example.com … done Removing peer1.org1.example.com …
done Removing peer0.org2.example.com … done Removing
peer0.org1.example.com … done Removing network net_byfn Removing
volume net_peer0.org3.example.com WARNING: Volume
net_peer0.org3.example.com not found. Removing volume
net_peer1.org3.example.com WARNING: Volume net_peer1.org3.example.com
not found. Removing volume net_orderer.example.com Removing volume
net_peer0.org2.example.com Removing volume net_peer0.org1.example.com
Removing volume net_peer1.org1.example.com Removing volume
net_peer1.org2.example.com 80510c01c3e8 3625e4ce1b01 43b4b0dfb14f
Untagged:
dev-peer1.org2.example.com-mycc-1.0-26c2ef32838554aac4f7ad6f100aca865e87959c9a126e86d764c8d01f8346ab:latest
Deleted:
sha256:3c7cf25f6520e39afe9ca0770821bcf8892c398ffa8fafaa4d39d4b18bf9a7af
Deleted:
sha256:ac116d2c1fbb503f766149a2acf422b754d59ba4be58902981d03b2969ef21c1
Deleted:
sha256:3e07d57882218fc26936d29deefba9e3bb0230d63b5e82d727ddbc92c59d942d
Deleted:
sha256:9c88b5b791167d2d37be1fc39886e5efa00d522aad7df03869b8eb30aa564b5f
Untagged:
dev-peer0.org1.example.com-mycc-1.0-384f11f484b9302df90b453200cfb25174305fce8f53f4e94d45ee3b6cab0ce9:latest
Deleted:
sha256:16229f944e6c2e665587638a47c80d9594693aede0d25d736d7225370efc67ae
Deleted:
sha256:6a5c627fbc23a646b17a493a6b7df67a2535501b8d77915aab6ac2c1ba97b1b3
Deleted:
sha256:4d0d3e96c80a3e0ee4c3553a125c99bbaffe6f1b487348f87ffb3059d6eb7f2e
Deleted:
sha256:a9600d47e71d3abb5f5afcbf56b6b21955e1bbe7fcb92040f1349667cf712bc0
Untagged:
dev-peer0.org2.example.com-mycc-1.0-15b571b3ce849066b7ec74497da3b27e54e0df1345daff3951b94245ce09c42b:latest
Deleted:
sha256:5f7c63593550d018ab28312c3d040b27a53f2d1e844ddd7d50a2fcf63454594b
Deleted:
sha256:a00c5883309d6a80aaf22f8b704b594c6129150c5048fd00d742077f212b28f7
Deleted:
sha256:71fae53aba930c88450ff286a5e54bceece45ea7aee465a8f2806aa967ab2b21
Deleted:
sha256:08fe44e007fd3d5377b44cca32e8f78d2249b0a1d9ce9312c68636fdacda2edc

到此Hyperledger Fabric环境搭建成功