Hyperledger fabric Docker container error Error response from daemon Container is not running

Question

I am running the bash file like this: 

docker-compose -f docker-compose.yml up -d ca.example.com orderer.example.com peer0.org1.example.com couchdb

I am getting this error:

Error response from daemon: Container 9338fh518d4158f29f0800c8bbef1c2b3749ffnsjqde34190fh2375e415b44it9f is not running

When i run this command

docker rm -f $(docker ps -aq)

and rerun bash file everytime I get the same error but the container is different.

Here is bash file:

#!/bin/bash
#
# SPDX-License-Identifier: Apache-2.0
# This code is based on code written by the Hyperledger Fabric community. 
# Original code can be found here: https://github.com/hyperledger/fabric-samples/blob/release/fabcar/startFabric.sh
#
# Exit on first error

set -e

# don't rewrite paths for Windows Git Bash users
export MSYS_NO_PATHCONV=1

starttime=$(date +%s)

if [ ! -d ~/.hfc-key-store/ ]; then
mkdir ~/.hfc-key-store/
fi

# launch network; create channel and join peer to channel
cd ../basic-network
./start.sh

# Now launch the CLI container in order to install, instantiate chaincode
# and prime the ledger with our 10 tuna catches
docker-compose -f ./docker-compose.yml up -d cli

docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode install -n tuna-app -v 1.0 -p github.com/tuna-app
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n tuna-app -v 1.0 -c '{"Args":[""]}' -P "OR ('Org1MSP.member','Org2MSP.member')"
sleep 10
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode invoke -o orderer.example.com:7050 -C mychannel -n tuna-app -c '{"function":"initLedger","Args":[""]}'

printf "\nTotal execution time : $(($(date +%s) - starttime)) secs ...\n\n"
printf "\nStart with the registerAdmin.js, then registerUser.js, then server.js\n\n"

Please help

Answer 1

I had to update the version of fabric samples to solve this error. Nothing else worked. To get the new version, you can use the following command:

$ git clone https://github.com/hyperledger/fabric-samples.git

Answer 2

Use this command to run bash file:

docker-compose -f ./docker-compose.yml up cli

Don't use -d

Answer 3

Hello, did someone solve the problem ?

Comments

Yes, this solve my problem:

docker-compose -f ./docker-compose.yml up cli

Answer 4

Maybe your docker container is not staying awake for more time. For me, I had to keep the docker container at least for 15 seconds. After a lot of research I found this command that actually worked for me:

$ ls -la /; sleep 10m

Answer 5

Remove the containers that are not being used and then try to run the fabric.

To stop and delete the containers, use the following command:

$ docker stop$(docker ps -aq)
$ docker rm $(docker ps -aq)

This will remove all the containers, so do not use it if you have any important containers running.

Comments

Hi @Sunny. I have some containers that are not being used and some containers that I require and so cannot remove them. How can I remove only the unused containers?

---

Hey, @sunny, there is no direct command for this. You will have to do it manually. First, find the containers that are running.

$ docker ps -aq

Then see which containers are not being used and note their container ID. Next, to stop and remove the containers, run the following command:

$ docker stop <docker id>
$ docker rm <docker id>

Answer 6

Open the startFabric.sh file and find the line:

docker-compose -f "${DOCKER_FILE}" down

Comment this line, save the file and try running your command again. It worked for me.