hyperledger-archives / fabric

THIS IS A READ-ONLY historic repository. Current development is at https://gerrit.hyperledger.org/r/#/admin/projects/fabric . pull requests not accepted

Home Page:https://gerrit.hyperledger.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cannot dial to 0.0.0.0:7050, because of grpc: timed out while dialing

mychewcents opened this issue · comments

Description

I built the hyperledger fabric using command "make dist-clean all" in Ubuntu 16.04 environment.
I have run all the steps according to the documentation provided on the Hyperledger Fabric official "readthedocs" page. I also copied the docker-compose file posted on the official hyperledger fabric documentation. It is as follows:

membersrvc: image: hyperledger/fabric-membersrvc command: membersrvc vp0: image: hyperledger/fabric-peer ports: - "7050:7050" - "7051:7051" - "7053:7053" environment: - CORE_PEER_ADDRESSAUTODETECT=true - CORE_VM_ENDPOINT=http://172.17.0.1:2375 - CORE_LOGGING_LEVEL=DEBUG - CORE_PEER_ID=vp0 - CORE_PEER_PKI_ECA_PADDR=membersrvc:7054 - CORE_PEER_PKI_TCA_PADDR=membersrvc:7054 - CORE_PEER_PKI_TLSCA_PADDR=membersrvc:7054 - CORE_SECURITY_ENABLED=true - CORE_SECURITY_ENROLLID=test_vp0 - CORE_SECURITY_ENROLLSECRET=MwYpmSRjupbT links: - membersrvc command: sh -c "sleep 5; peer node start"

I don't understand what went wrong when I run "docker-compose up". I'm running already available hyperledger/fabric-peer image. There has been no change in the ports while running and all the things are run using default ports only.

Describe How to Reproduce

To reproduce the issue, I followed all the steps mentioned in the hyperledger fabric docs. Then I build the fabric through command "make dist-clean all". Then I copied the docker-compose.yml file and run the "docker-compose up" command.