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, 1323🔥, 0💬
Popular Posts:
How to use the "set-backend-service" Policy Statement for an Azure API service operation? The "set-b...
How to run PowerShell Commands in Dockerfile to change Windows Docker images? When building a new Wi...
How to use the "forward-request" Policy Statement to call the backend service for an Azure API servi...
Can You Add Values to an Array without Keys in PHP? Can You Add Values to an Array with a Key? The a...
How to Build my "sleep" Docker image from the Alpine image? I want the container to sleep for 10 hou...