SysTutorials

Installing Hyperledger Fabric 2.5 on Ubuntu 24.04 LTS

· Eric Ma · updated April 11, 2026

Hyperledger Fabric is a modular, enterprise-grade consortium blockchain platform. While its official documentation is comprehensive, deploying a test network from scratch requires configuring multiple dependencies and tools—a process that’s time-consuming for new users. This guide covers both automated and manual setup approaches to get a working Fabric network running quickly.

Prerequisites

You’ll need:

Quick Installation

The fastest way to get started is using the official bootstrap script:

git clone https://github.com/hyperledger/fabric-samples
cd fabric-samples/test-network
curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/main/scripts/install-fabric.sh | bash -s
./network.sh up

If you prefer understanding each step or need to customize your installation, follow the manual steps below.

Manual Installation Steps

1. Install System Dependencies

Update your system and install required packages:

sudo apt update
sudo apt install -y git curl wget docker.io docker-compose nodejs npm build-essential python3

Add your user to the Docker group to avoid needing sudo for every Docker command:

sudo usermod -aG docker $USER
newgrp docker

Alternatively, log out and log back in for the group change to take effect.

2. Install Go

Fabric requires Go 1.21 or later. Download and install the latest stable version:

wget https://go.dev/dl/go1.23.linux-amd64.tar.gz
sudo rm -rf /usr/local/go
sudo tar -C /usr/local -xzf go1.23.linux-amd64.tar.gz
rm go1.23.linux-amd64.tar.gz

Add Go to your PATH by appending to ~/.bashrc:

export PATH=$PATH:/usr/local/go/bin
export GOPATH=$HOME/go
export PATH=$GOPATH/bin:$PATH

Reload your shell:

source ~/.bashrc

Verify the installation:

go version

3. Clone Fabric Samples

Create the directory structure and clone the repository:

mkdir -p $GOPATH/src/github.com/hyperledger
cd $GOPATH/src/github.com/hyperledger
git clone https://github.com/hyperledger/fabric-samples.git
cd fabric-samples
git checkout main

To use a specific release tag instead of main (e.g., v2.5.0):

git checkout v2.5.0

4. Bootstrap Fabric Binaries and Docker Images

Navigate to the test-network directory and run the bootstrap script:

cd test-network
curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/main/scripts/install-fabric.sh | bash -s

This downloads:

Verify binaries are available:

ls ../bin/

You should see: peer, orderer, fabric-ca-client, configtxgen, cryptogen, and others.

5. Start the Test Network

In the test-network directory, bring up the network:

./network.sh up

This command:

Verify the network is running:

docker ps

You should see three containers: one orderer node (orderer.example.com) and two peer nodes (peer0.org1.example.com and peer0.org2.example.com).

6. Create a Channel

./network.sh createChannel -c mychannel

Wait for the output confirming “Channel ‘mychannel’ created.” Verify by checking the peer logs:

docker logs peer0.org1.example.com

7. Deploy Chaincode

Deploy the sample FabCar chaincode:

./network.sh deployCC -l go -ccn fabcar -ccv 1

Supported languages:

The deployment process includes:

This can take 1-2 minutes depending on system resources. Monitor progress with:

docker logs peer0.org1.example.com -f

8. Interact with the Chaincode

Before running peer commands, set environment variables to point to the correct organization:

export PATH=${PWD}/../bin:$PATH
export FABRIC_CFG_PATH=${PWD}/../config
export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=localhost:7051

Query the ledger:

peer chaincode query -C mychannel -n fabcar -c '{"Args":["queryAllCars"]}'

Expected output: a JSON array of cars (initially empty for a new chaincode).

Invoke a transaction to create a new car:

peer chaincode invoke -C mychannel -n fabcar \
  -c '{"Args":["createCar","CAR10","Honda","Civic","white","Alice"]}'

Query the car you just created:

peer chaincode query -C mychannel -n fabcar \
  -c '{"Args":["queryCar","CAR10"]}'

To switch to Org2, update the environment variables:

export CORE_PEER_LOCALMSPID=Org2MSP
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=localhost:9051

Stopping and Cleaning Up

To bring down the network without removing generated artifacts:

./network.sh down

To perform a complete cleanup, including removing generated certificates and channel artifacts:

./network.sh down -c

To remove all Docker containers and volumes associated with Fabric:

docker-compose down -v
docker volume rm $(docker volume ls -f label=com.docker.compose.project=test-network -q)

Troubleshooting

Docker permission denied errors

Ensure your user is in the docker group and you’ve relogged or run newgrp docker. Verify with:

groups $USER

Port already in use

If ports 7050, 7051, 9051, or 9052 are in use, either stop the conflicting services or modify the docker-compose.yaml file to use different ports. Check which process is using a port:

sudo lsof -i :7051

Chaincode installation failures

Verify Go is properly installed and $GOPATH is set correctly:

go env GOPATH
which peer

Check that the chaincode directory structure is valid. For Go chaincodes, ensure go.mod exists in the chaincode directory and dependencies are resolvable.

Container startup failures

Review Docker logs to diagnose issues:

docker logs orderer.example.com
docker logs peer0.org1.example.com

Ensure you have sufficient disk space and RAM:

df -h
free -h

Module resolution errors during chaincode deployment

When deploying Go chaincodes, verify go.mod exists in the chaincode directory and contains correct dependency versions. If using external modules, ensure they’re publicly accessible.

Network connectivity issues

If bootstrap fails, verify internet connectivity and that GitHub is accessible:

curl -I https://github.com

Next Steps

← All posts