Tools, FAQ, Tutorials:
Deploy Peer with Default Configuration
How to Deploy the Peer Docker Image with the Default Configuration?
✍: FYIcenter.com
You can follow this tutorial to deploy the Peer Docker Image with the Default Configuration.
1. Create a new Docker Compose YAML file, docker-compose-peer.yaml:
$ cd fabric-peer $ vi docker-compose-peer.yaml # Copyright (c) FYIcenter.com version: '2' services: peer: container_name: peer image: hyperledger/fabric-peer:amd64-1.4.0 command: peer node start
2. Stop and remove any existing Peer container:
$ docker stop peer.example.com peer.example.com $ docker rm peer.example.com peer.example.com
3. Deploy a new Peer container with the default configuration:
$ docker-compose -f docker-compose-peer.yaml up -d Creating network "fabric-peer_default" with the default driver Creating peer ... done
4. Verify the Peer container status:
$ docker ps IMAGE STATUS NAMES hyperledger/fabric-peer:amd64-1.4.0 Up 9 seconds peer
5. Review the log file of the Orderer container:
$ docker logs peer [nodeCmd] serve -> INFO 001 Starting peer: Version: 1.4.0 Commit SHA: d700b43 Go version: go1.11.1 OS/Arch: linux/amd64 Chaincode: Base Image Version: 0.4.14 Base Docker Namespace: hyperledger Base Docker Label: org.hyperledger.fabric Docker Namespace: hyperledger [ledgermgmt] initialize -> INFO 002 Initializing ledger mgmt [kvledger] NewProvider -> INFO 003 Initializing ledger provider [kvledger] NewProvider -> INFO 004 ledger provider Initialized [ledgermgmt] initialize -> INFO 005 ledger mgmt initialized [peer] func1 -> INFO 006 Auto-detected peer address: 172.20.0.2:7051 [peer] func1 -> INFO 007 Host is 0.0.0.0 , falling back to auto-detected address: 172.20.0.2:7051 [peer] func1 -> INFO 008 Auto-detected peer address: 172.20.0.2:7051 [peer] func1 -> INFO 009 Host is 0.0.0.0 , falling back to auto-detected address: 172.20.0.2:7051 [nodeCmd] computeChaincodeEndpoint -> INFO 00a Entering computeChaincodeEndpoint with peerHostname: 172.20.0.2 [nodeCmd] computeChaincodeEndpoint -> INFO 00b Exit with ccEndpoint: 172.20.0.2:7052 [nodeCmd] createChaincodeServer -> WARN 00c peer.chaincodeListenAddress is not set, using 172.20.0.2:7052 [sccapi] registerSysCC -> INFO 00d system chaincode lscc(github.com/hyperledger/fabric/core/scc/lscc) registered [sccapi] registerSysCC -> INFO 00e system chaincode cscc(github.com/hyperledger/fabric/core/scc/cscc) registered [sccapi] registerSysCC -> INFO 00f system chaincode qscc(github.com/hyperledger/fabric/core/scc/qscc) registered [sccapi] registerSysCC -> INFO 010 system chaincode (+lifecycle,github.com/hyperledger/fabric/core/chaincode/lifecycle,true) disabled [gossip.service] func1 -> INFO 011 Initialize gossip with endpoint 172.20.0.2:7051 and bootstrap set [127.0.0.1:7051] [gossip.gossip] NewGossipService -> INFO 012 Creating gossip service with self membership of Endpoint: , \ InternalEndpoint: 172.20.0.2:7051, PKI-ID: 0d46737a45894d123895671221dbad..., Metadata: [gossip.gossip] NewGossipService -> WARN 013 External endpoint is empty, peer will not be accessible outside of its organization [gossip.gossip] start -> INFO 014 Gossip instance 172.20.0.2:7051 started [sccapi] deploySysCC -> INFO 015 system chaincode lscc/(github.com/hyperledger/fabric/core/scc/lscc) deployed [cscc] Init -> INFO 016 Init CSCC [sccapi] deploySysCC -> INFO 017 system chaincode cscc/(github.com/hyperledger/fabric/core/scc/cscc) deployed [qscc] Init -> INFO 018 Init QSCC [sccapi] deploySysCC -> INFO 019 system chaincode qscc/(github.com/hyperledger/fabric/core/scc/qscc) deployed [sccapi] deploySysCC -> INFO 01a system chaincode (+lifecycle,github.com/hyperledger/fabric/core/chaincode/lifecycle) disabled [nodeCmd] serve -> INFO 01b Deployed system chaincodes [discovery] NewService -> INFO 01c Created with config TLS: false, authCacheMaxSize: 1000, authCachePurgeRatio: 0.750000 [nodeCmd] registerDiscoveryService -> INFO 01d Discovery service activated [nodeCmd] serve -> INFO 01e Starting peer with ID=[name:"jdoe" ], network ID=[dev], address=[172.20.0.2:7051] [nodeCmd] serve -> INFO 01f Started peer with ID=[name:"jdoe" ], network ID=[dev], address=[172.20.0.2:7051]
As you can, we have a ledger peer up and running. See next tutorial on how to verify its status.
⇒ Default core.yaml in Peer Docker Image
⇐ Pull Hyperledger Fabric Peer Image
2019-05-10, 1204🔥, 0💬
Popular Posts:
How to add request URL Template Parameters to my Azure API operation 2017 version to make it more us...
How to Build my "sleep" Docker image from the Alpine image? I want the container to sleep for 10 hou...
How to create a new API on the Publisher Dashboard of an Azure API Management Service? If you are ne...
How to extend json.JSONEncoder class? I want to encode other Python data types to JSON. If you encod...
How To Move Uploaded Files To Permanent Directory in PHP? PHP stores uploaded files in a temporary d...