Tools, FAQ, Tutorials:
"byfn.sh up" Error - Container Name in Use
Why am I getting the "Cannot create container for service peer0.org1.example.com: b'Conflict." error when running "byfn.sh up" to start up the BYFN Network?
✍: FYIcenter.com
You are getting "Cannot create container for service
peer0.org1.example.com: b'Conflict." error when
running the "byfn.sh up" command,
because there container name "peer0.org1.example.com" already exists
on the Docker Engine.
This error condition happens frequently on your local test environment, because many test networks are using the same container name "peer0.org1.example.com".
To resolve the issue, you can stop and remove the offending container:
$ docker container ls -a | grep peer0 ... hyperledger/fabric-peer:1.4 "peer node start" peer0.org1.example.com $ docker container stop "peer0.org1.example.com" peer0.org1.example.com $ docker container rm "peer0.org1.example.com" peer0.org1.example.com
Repeat the same steps to remove other containers.
⇒ BYFN Containers Running on Docker
⇐ "byfn.sh down" - Shut Down BYFN Network
2020-05-05, ∼2002🔥, 0💬
Popular Posts:
How to decode the id_token value received from Google OpenID Connect authentication response? Accord...
How to use the "rewrite-uri" Policy Statement for an Azure API service operation? The "rewrite-uri" ...
How to build a test service operation to dump everything from the "context.Request" object in the re...
FYIcenter.com Online Tools: FYIcenter JSON Validator and Formatter FYIcenter JSON to XML Converter F...
How to troubleshoot the Orderer peer? The Docker container terminated by itself. You can follow this...