Skip to content

Instantly share code, notes, and snippets.

@Role911
Created September 4, 2019 15:05
Show Gist options
  • Save Role911/18599277bcca73591b5a78f4cfef1963 to your computer and use it in GitHub Desktop.
Save Role911/18599277bcca73591b5a78f4cfef1963 to your computer and use it in GitHub Desktop.
Configuration for peers
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
peer-base:
image: hyperledger/fabric-peer
environment:
- 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/
# NOTE: NAME OF NETWORK ARE DEFINE FROM FOLDER WHERE ARE DEFINED AND _NAME (network_default)
# ALSO CHECK THE DOCKER NETWORK THAT NETWORK ARE UNIQE with command (docker network ls)
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=network_default
- FABRIC_LOGGING_SPEC=DEBUG
- CORE_LOGGING_LEVEL=DEBUG
- CORE_PEER_GOSSIP_USELEADERELECTION=true
- CORE_PEER_GOSSIP_ORGLEADER=false
- CORE_LEDGER_STATE_STATEDATABASE=CouchDB
- CORE_CHAINCODE_EXECUTETIMEOUT=300s
- CORE_CHAINCODE_DEPLOYTIMEOUT=300s
# The following setting skips the gossip handshake since we are
# are not doing mutual TLS
- CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
- CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto/peer/msp
- CORE_PEER_TLS_ENABLED=true
- CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/crypto/peer/tls/server.key
- CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/crypto/peer/tls/server.crt
- CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto/peer/tls/ca.crt
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: peer node start
volumes:
- /var/run/:/host/var/run/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment