Docker images for Hyperledger fabric peer.
latest
(latest/Dockerfile): Default to enable pbft as consensus.noops
(noops/Dockerfile): Use noops as consenus.pbft
(pbft/Dockerfile): Use pbft as consensus.
For more information about this image and its history, please see the relevant manifest file in the yeasy/docker-hyperledger-peer
GitHub repo.
If you want to quickly deploy a local cluster without any configuration and vagrant, please refer to hyperledger-compose-files.
Docker image with hyperledger fabric peer deployed.
The docker image is auto built at https://registry.hub.docker.com/u/yeasy/hyperledger-peer/.
FROM yeasy/hyperledger-peer:latest
The peer command is already there, add your sub command and flags at the end.
E.g., see the supported sub commands with the help
command.
02:10:10.359 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
Usage:
peer [command]
Available Commands:
node node specific commands.
network network specific commands.
chaincode chaincode specific commands.
help Help about any command
Flags:
--logging-level="": Default logging level and overrides, see core.yaml for full syntax
Use "peer [command] --help" for more information about a command.
Hyperledger relies on a core.yaml
file, you can mount your local one by
$ docker run -v your_local_core.yaml:/go/src/github.com/hyperledger/fabric/peer/core.yaml -d yeasy/hyperledger-peer node start help
The storage will be under /var/hyperledger/
, which should be mounted from host for persistent requirement.
Your can also mapping the port outside using the -p
options.
- 5000: REST service listening port (Recommened to open at non-validating node)
- 30303: Peer service listening port
- 30304: CLI process use it for callbacks from chain code
- 31315: Event service on validating node
Start your docker daemon with
$ sudo docker daemon --api-cors-header="*" -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock
Pull necessary images, notice the default config require a local built openblockchain/baseimage
. We can just use the yeasy/hyperledger
image instead.
$ docker pull yeasy/hyperledger:latest
$ docker tag yeasy/hyperledger:latest hyperledger/fabric-baseimage:latest
$ docker pull yeasy/hyperledger-peer:latest
$ docker pull yeasy/hyperledger-peer:noops
$ docker pull yeasy/hyperledger-peer:pbft
Check the docker0
bridge ip, normally it should be 172.17.0.1
. This ip will be used as the CORE_VM_ENDPOINT=http://172.17.0.1:2375
.
$ ip addr show dev docker0
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:f2:90:57:cf brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:f2ff:fe90:57cf/64 scope link
valid_lft forever preferred_lft forever
Start a validating node.
$ docker run --name=vp0 \
--restart=unless-stopped \
-it \
-p 5000:5000 \
-p 30303:30303 \
-e CORE_PEER_ID=vp0 \
-e CORE_VM_ENDPOINT=http://172.17.0.1:2375 \
-e CORE_PEER_ADDRESSAUTODETECT=true \
-e CORE_NOOPS_BLOCK_TIMEOUT=10 \
yeasy/hyperledger-peer:noops peer node start
PBFT requires at least 4 nodes, so please refer to hyperledger-compose-files.
After the cluster starts up, enter into the container
$ docker exec -it vp0 bash
Inside the container, deploy a chaincode using
$ peer chaincode deploy -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02 -c '{"Function":"init", "Args": ["a","100", "b", "200"]}'
13:16:35.643 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
5844bc142dcc9e788785e026e22c855957b2c754c912702c58d997dedbc9a042f05d152f6db0fbd7810d95c1b880c210566c9de3093aae0ab76ad2d90e9cfaa5
Query a
's current value, which is 100.
$ peer chaincode query -n 5844bc142dcc9e788785e026e22c855957b2c754c912702c58d997dedbc9a042f05d152f6db0fbd7810d95c1b880c210566c9de3093aae0ab76ad2d90e9cfaa5 -c '{"Function": "query", "Args": ["a"]}'
13:20:07.952 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
100
Invoke a transaction of 10 from a
to b
.
$ peer chaincode invoke -n 5844bc142dcc9e788785e026e22c855957b2c754c912702c58d997dedbc9a042f05d152f6db0fbd7810d95c1b880c210566c9de3093aae0ab76ad2d90e9cfaa5 -c '{"Function": "invoke", "Args": ["a", "b", "10"]}'
13:20:31.028 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
ec3c675b-a2fe-4429-ab44-7f389e454657
Query a
's value now.
$ peer chaincode query -n 5844bc142dcc9e788785e026e22c855957b2c754c912702c58d997dedbc9a042f05d152f6db0fbd7810d95c1b880c210566c9de3093aae0ab76ad2d90e9cfaa5 -c '{"Function": "query", "Args": ["a"]}'
13:20:35.725 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO
90
More examples, please refer to hyperledger-compose-files.
The image is built based on hyperledger base image.
Install required libsnappy-dev, zlib1g-dev, libbz2-dev.
Install required rocksdb 4.1.
Install hyperledger and build the peer
This image is officially supported on Docker version 1.7.0.
Support for older versions (down to 1.0) is provided on a best-effort basis.
- N/A.
Be sure to familiarize yourself with the repository's README.md
file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You can also reach many of the official image maintainers via the email.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.