Building the fabric

The following instructions assume that you have already set up your development environment.

To access your VM, run vagrant ssh from within the devenv directory of your locally cloned fabric repository.

cd $GOPATH/src/
vagrant ssh

From within the VM, you can build, run, and test your environment.

cd $GOPATH/src/
make peer

To see what commands are available, simply execute the following commands:

peer help

You should see the following output:

      peer [command]

    Available Commands:
      node        node specific commands.
      network     network specific commands.
      chaincode   chaincode specific commands.
      help        Help about any command

      -h, --help[=false]: help for peer
          --logging-level="": Default logging level and overrides, see core.yaml for full syntax

    Use "peer [command] --help" for more information about a command.

The peer node start command will initiate a peer process, with which one can interact by executing other commands. For example, the peer node status command will return the status of the running peer. The full list of commands is the following:

        start       Starts the node.
        status      Returns status of the node.
        stop        Stops the running node.
        login       Logs in user to CLI.
        list        Lists all network peers.
        deploy      Deploy the specified chaincode to the network.
        invoke      Invoke the specified chaincode.
        query       Query using the specified chaincode.
      help        Help about any command

Note: If your GOPATH environment variable contains more than one element, the chaincode must be found in the first one or deployment will fail.

Running the unit tests

Use the following sequence to run all unit tests

cd $GOPATH/src/
make unit-test

To run a specific test use the -run RE flag where RE is a regular expression that matches the test case name. To run tests with verbose output use the -v flag. For example, to run the TestGetFoo test case, change to the directory containing the foo_test.go and call/excecute

go test -v -run=TestGetFoo

Running Node.js Unit Tests

You must also run the Node.js unit tests to insure that the Node.js client SDK is not broken by your changes. To run the Node.js unit tests, follow the instructions here.

Running Behave BDD Tests

Behave tests will setup networks of peers with different security and consensus configurations and verify that transactions run properly. To run these tests

cd $GOPATH/src/
make behave

Some of the Behave tests run inside Docker containers. If a test fails and you want to have the logs from the Docker containers, run the tests with this option

behave -D logs=Y

Note, in order to run behave directly, you must run ‘make images’ first to build the necessary peer and member services docker images. These images can also be individually built when go test is called with the following parameters:

go test -run=BuildImage_Peer
go test -run=BuildImage_Obcca

Building outside of Vagrant

It is possible to build the project and run peers outside of Vagrant. Generally speaking, one has to ‘translate’ the vagrant setup file to the platform of your choice.


  • Git client
  • Go - 1.6 or later
  • RocksDB version 4.1 and its dependencies
  • Docker
  • Pip
  • Set the maximum number of open files to 10000 or greater for your OS


Make sure that the Docker daemon initialization includes the options

-H tcp:// -H unix:///var/run/docker.sock

Typically, docker runs as a service task, with configuration file at /etc/default/docker.

Be aware that the Docker bridge (the CORE_VM_ENDPOINT) may not come up at the IP address currently assumed by the test environment ( Use ifconfig or ip addr to find the docker bridge.

Building RocksDB

apt-get install -y libsnappy-dev zlib1g-dev libbz2-dev
cd /tmp
git clone
cd rocksdb
git checkout v4.1
PORTABLE=1 make shared_lib
INSTALL_PATH=/usr/local make install-shared

pip, behave and docker-compose

pip install --upgrade pip
pip install behave nose docker-compose
pip install -I flask==0.10.1 python-dateutil==2.2 pytz==2014.3 pyyaml==3.10 couchdb==1.0 flask-cors==2.0.1 requests==2.4.3

Building on Z

To make building on Z easier and faster, this script is provided (which is similar to the setup file provided for vagrant). This script has been tested only on RHEL 7.2 and has some assumptions one might want to re-visit (firewall settings, development as root user, etc.). It is however sufficient for development in a personally-assigned VM instance.

To get started, from a freshly installed OS:

sudo su
yum install git
mkdir -p $HOME/git/src/
cd $HOME/git/src/
git clone
source fabric/devenv/

From this point, you can proceed as described above for the Vagrant development environment.

cd $GOPATH/src/
make peer unit-test behave

Building natively on OSX

First, install Docker, as described here. The database by default writes to /var/hyperledger. You can override this in the core.yaml configuration file, under peer.fileSystemPath.

brew install go rocksdb snappy gnu-tar     # For RocksDB version 4.1, you can compile your own, as described earlier

# You will need the following two for every shell you want to use
eval $(docker-machine env)
export PATH="/usr/local/opt/gnu-tar/libexec/gnubin:$PATH"

cd $GOPATH/src/
make peer


Configuration utilizes the viper and cobra libraries.

There is a core.yaml file that contains the configuration for the peer process. Many of the configuration settings can be overridden on the command line by setting ENV variables that match the configuration setting, but by prefixing with ‘CORE_’. For example, logging level manipulation through the environment is shown below:



Logging utilizes the go-logging library.

The available log levels in order of increasing verbosity are: CRITICAL | ERROR | WARNING | NOTICE | INFO | DEBUG

See specific logging control instructions when running the peer process.