1. Messages
  2. CORE_PEER_CHAINCODEADDRESS when peer is not running in a docker container

Re: CORE_PEER_CHAINCODEADDRESS when peer is not running in a docker container

Nye Liu <nye@...>
 

Whatever public IP other peers would use to connect to it. Docker and NAT (in docker's case double or triple NAT) complicate matters, you will have to pay attention to how you will have peers communicating and how you will be deploying TLS certs. Docker supposedly simplifies things for novices but in my experience it makes any rational p2p design a huge pain.


On Tue, Jan 28, 2020, 2:20 PM Siddharth Jain <siddjain@...> wrote:
What should be the CORE_PEER_CHAINCODEADDRESS when the peer is not running in a docker container? E.g., peer is running on the host and listening for chaincode at 0.0.0.0:7052. If we set CORE_PEER_CHAINCODEADDRESS to 127.0.0.1:7051 then for the chaincode container 127.0.0.1 maps to the docker container itself not the host.
Join fabric@lists.hyperledger.org to automatically receive all group messages.