Deploy Peer with Default Configuration


How to Deploy the Peer Docker Image with the Default Configuration?



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)
version: '2'

    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

$ docker rm

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
  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:
[peer] func1 -> INFO 007 Host is , falling back to auto-detected address:
[peer] func1 -> INFO 008 Auto-detected peer address:
[peer] func1 -> INFO 009 Host is , falling back to auto-detected address:
[nodeCmd] computeChaincodeEndpoint -> INFO 00a Entering computeChaincodeEndpoint with peerHostname:
[nodeCmd] computeChaincodeEndpoint -> INFO 00b Exit with ccEndpoint:
[nodeCmd] createChaincodeServer -> WARN 00c peer.chaincodeListenAddress is not set, using
[sccapi] registerSysCC -> INFO 00d system chaincode lscc( registered
[sccapi] registerSysCC -> INFO 00e system chaincode cscc( registered
[sccapi] registerSysCC -> INFO 00f system chaincode qscc( registered
[sccapi] registerSysCC -> INFO 010 system chaincode (+lifecycle,,true) disabled
[gossip.service] func1 -> INFO 011 Initialize gossip with endpoint and bootstrap set []
[gossip.gossip] NewGossipService -> INFO 012 Creating gossip service with self membership of Endpoint: , \
   InternalEndpoint:, 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 started
[sccapi] deploySysCC -> INFO 015 system chaincode lscc/( deployed
[cscc] Init -> INFO 016 Init CSCC
[sccapi] deploySysCC -> INFO 017 system chaincode cscc/( deployed
[qscc] Init -> INFO 018 Init QSCC
[sccapi] deploySysCC -> INFO 019 system chaincode qscc/( deployed
[sccapi] deploySysCC -> INFO 01a system 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=[]
[nodeCmd] serve -> INFO 01f Started peer with ID=[name:"jdoe" ], network ID=[dev], address=[]

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

Setting Up Ledger Peer Manually

⇑⇑ Hyperledger Tutorials

2019-05-10, 192👍, 0💬