#fabric-chaincode-evm #fabric-chaincode #fabric #fabric #fabric-chaincode-evm #fabric-chaincode


李东旭
 

version of peer ,order, fabric-ca image is  1.4 ,but I got Fabric network is  1.1 。

question:

 the relationship between peer order, fabric-ca‘s version and  Fabric network?


some log :

daronlee@daronlee-virtual-machine:~/learning/experiment/IBM_tutorial/blockchain-application-using-fabric-java-sdk/network$ ./build.sh 
 
Stopping the previous network (if any)
Stopping peer0.org1.example.com ... done
Stopping peer1.org1.example.com ... done
Stopping peer1.org2.example.com ... done
Stopping peer0.org2.example.com ... done
Stopping ca_peerOrg1            ... done
Stopping orderer.example.com    ... done
Stopping ca_peerOrg2            ... done
Removing peer0.org1.example.com ... done
Removing peer1.org1.example.com ... done
Removing peer1.org2.example.com ... done
Removing peer0.org2.example.com ... done
Removing ca_peerOrg1            ... done
Removing orderer.example.com    ... done
Removing ca_peerOrg2            ... done
Removing network network_custom
 
Setting up the Hyperledger Fabric 1.1 network
Creating network "network_custom" with the default driver
Creating ca_peerOrg2            ... done
Creating orderer.example.com ... done
Creating ca_peerOrg1         ... done
Creating peer0.org1.example.com ... done
Creating peer1.org1.example.com ... done
Creating peer1.org2.example.com ... done
Creating peer0.org2.example.com ... done
 
Network setup completed!!
 
daronlee@daronlee-virtual-machine:~/learning/experiment/IBM_tutorial/blockchain-application-using-fabric-java-sdk/network$ docker ps 
CONTAINER ID        IMAGE                            COMMAND                  CREATED             STATUS              PORTS                                            NAMES
4bae8f3ba5ba        hyperledger/fabric-peer:1.4      "peer node start"        4 hours ago         Up 4 hours          0.0.0.0:8056->7051/tcp, 0.0.0.0:8058->7053/tcp   peer1.org2.example.com
30cc6e510c6f        hyperledger/fabric-peer:1.4      "peer node start"        4 hours ago         Up 4 hours          0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp   peer0.org2.example.com
d12a490efc2f        hyperledger/fabric-peer:1.4      "peer node start"        4 hours ago         Up 4 hours          0.0.0.0:7056->7051/tcp, 0.0.0.0:7058->7053/tcp   peer1.org1.example.com
ce33840c091a        hyperledger/fabric-peer:1.4      "peer node start"        4 hours ago         Up 4 hours          0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp   peer0.org1.example.com
f464ebc0d1d2        hyperledger/fabric-ca:1.4        "sh -c 'fabric-ca-se…"   4 hours ago         Up 4 hours          0.0.0.0:7054->7054/tcp                           ca_peerOrg1
ae5cb13f9690        hyperledger/fabric-ca:1.4        "sh -c 'fabric-ca-se…"   4 hours ago         Up 4 hours          0.0.0.0:8054->7054/tcp                           ca_peerOrg2
49f89894c88f        hyperledger/fabric-orderer:1.4   "orderer"                4 hours ago         Up 4 hours          0.0.0.0:7050->7050/tcp                           orderer.example.com
b6a52e0ded9d        gliderlabs/logspout              "/bin/logspout"          4 days ago          Up 22 hours         127.0.0.1:8000->80/tcp                           logspout2
daronlee@daronlee-virtual-machine:~/learning/experiment/IBM_tutorial/blockchain-application-using-fabric-java-sdk/network$ 
 

Join fabric@lists.hyperledger.org to automatically receive all group messages.