fabric-tools | Some scripts for configuring and deploying the fabric | Continuous Deployment library

The process can be really straightforward but it is not possible to avoid the inherent greater complexity of kubernetes (compared to swarm) which results, in turn, to a more complex configuration.

My advise is to start using kompose tool, which both gives you the yaml files corresponding to you original docker-compose.yml but also warn you regarding possible issues that may arise.

After following kompose installation steps, naming orderer.yaml your first file and peer.yaml your second file it's only a matter of executing

according to your describe,in the tourial ,fabric version is v1.4.X,and the fabric you now use is v2.x.x,so in v1.4.x the test script is byfn.sh and in v2.x.x the test script is network.sh,these two scripts are different.

if you want to backup a fabric network and restore,you need just backup crypto-config(organizations in v2.x.x),ledger data which obtain from /var/hyperledger/fabric of docker container,and start your orderer and peer container ,you need not create channel or join channel ,you can query and invoke chaincode.

I have answer another question about restore fabric network,you can reference it In Hyperledger Fabric, is there a way to reuse the data of previous network?

--------------new answer-------------------------------

if you exec you peer chaincode invoke command in terminal,you should add this env,and you can invoke success.

try it:

You can check the Dockerfile from the official fabric Github. In this line you see the tools, which are build inside the fabric-tools image.

Like in this post mentioned Difference between fabric-tools and fabric-ca-tools images it includes the tools:

configtxgen configtxlator cryptogen discover idemixgen osnadmin peer

The fabric-tools Container is a helper Container, which you can use to make things easier. For example creating a channel, joining it etc. You can do the operations without it. In production you would use f.e. a CA instead of creating the crypto-config artifacts with the cryptogen tool. Also the fabric-tools container is usually used to mount the whole channel-artifacts folder and the crypto-config folder. This would not be very practical for productive use. You might have to make a modification depending on the intended use.

According to Nikhil Gupta's post, this error indicates that "the MSP ID that was passed as a parameter with the request was not recognized by the ordering service."

Actually, this isn't true. If you read this post carefully, you will see that the error

The issue is in your channel configuration file (configtx.yaml). You have defined the same ports for Anchors peers on both Organization.

Org2 (Presently):

You can simply read from file, save into the wallet and continue the same way as before.

Declare or replace variables suitably:

You can add a new orderer in your RAFT consensus protocol setup by following these steps. It’s a lengthy process so I will also add a script later but for now you can follow these steps. Here, I am using first-network from the fabric samples for starting the network with 5 orderers.

1. First of all in crypto-config under OrdererOrgs: Specs: create a new hostname for your orderer (using the same domain and name as your other).

2. Then, run the command cryptogen extend --config=./crypto-config.yaml NOTE: the 'extend' part so it generates what you need and not regenerate everything.

3. Now first we will add orderer to the system channel and then when it has all the blocks of the system channel then we will move it into application channel so please make sure you are doing it properly.

4. Enter into your cli container by using docker exec -it cli bash and bootstrap it with an active orderer information as you will need the OrdererMSP to sign off this change.

Here are some of the environment variables that you will need to bootstrap cli with orderer:

The issue was resolved after giving complete access to the folders using : sudo chmod -R 777 .