1

I am trying to configure hyperledger composer with multi peer. But when I have started the hyperledger fabric, getting following response. 

amandai@ubuntultop:~/block chain/fabric-samples V1/ess-multipeer-sample      /network$ ./byfn.sh -m up
Starting with channel 'essplchannel' and CLI timeout of '10000' seconand CLI delay of '3' seconds
Continue (y/n)? y
proceeding ...
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
Creating network "network_amsnetwork" with the default driver
Creating orderer.esspl.com ... 
Creating peer0.ezone.esspl.com ... 
Creating peer0.essbbsr.esspl.com ... 
Creating ca_peerEssbbsr ... 
Creating ca_peerezone ... 
Creating peer0.ezone.esspl.com
Creating orderer.esspl.com
Creating ca_peerezone
Creating peer0.ezone.esspl.com ... done
Creating ca_peerEssbbsr ... done
Error response from daemon: No such container: cli
amandai@ubuntultop:~/block chain/fabric-samples V1/ess-multipeer-sample/network$
chinmaya.mahunta
  • 133
  • 2
  • 10

5 Answers5

2

I have used COMPOSE_FILE=docker-compose.yaml instead of COMPOSE_FILE=docker-compose-cli.yaml due to this error came. After modifying it working as expected.

chinmaya.mahunta
  • 133
  • 2
  • 10
0

Is it possible your error may be captured by the answers posted here -> Error when try to instantiate chain-code on Hyperledger Fabric - perhaps making sure there's no 'space' in your directory name (as shown above) may help / setting the variable explicitly?

Paul O'Mahony
  • 6,740
  • 1
  • 10
  • 15
0

I had a similar error recently and it related to having some conflicting containers already active. In a section of the following it explains how to remove potentially conflicting containers which I followed to remove my occurrence of this issue. https://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html

user3596628
  • 41
  • 3
0

upgrade the docker-compose or reinstall it

sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

It solves the problem for me.

Julian
  • 33,915
  • 22
  • 119
  • 174
Suman Das
  • 1
0

In my case, docker-composer was missing. Installing it solved the issue.

ShunShirou
  • 9
  • 1
  • 4