In latest commits you added support for fabric in raspberry as
described here.
I am trying so many days to build fabric-chaincode-java without
success (the help in the chats or the list was almost zero). So I
decide to check the test-network in GO. Thus the steps are:
1) In latest fabric folder: make docker, make native
2) I ignored the fabric-ca
3) copy bin/ from fabric folder to samples folder, same for the
config/
4) In latest fabric-samples/test-network folder: ./network down,
./network up
Starting nodes with CLI timeout of '5' tries
and CLI delay of '3' seconds and using database 'leveldb' with
crypto from 'cryptogen'
LOCAL_VERSION=2.4.0
DOCKER_IMAGE_VERSION=
Local fabric binaries and docker images are out of sync. This
may cause problems.
/home/ubuntu/fabric-samples/test-network/../bin/cryptogen
Generating certificates using cryptogen tool
Creating Org1 Identities
+ cryptogen generate
--config=./organizations/cryptogen/crypto-config-org1.yaml
--output=organizations
org1.example.com
+ res=0
Creating Org2 Identities
+ cryptogen generate
--config=./organizations/cryptogen/crypto-config-org2.yaml
--output=organizations
org2.example.com
+ res=0
Creating Orderer Org Identities
+ cryptogen generate
--config=./organizations/cryptogen/crypto-config-orderer.yaml
--output=organizations
+ res=0
Generating CCP files for Org1 and Org2
Creating network "fabric_test" with the default driver
Creating volume "docker_orderer.example.com" with default
driver
Creating volume "docker_peer0.org1.example.com" with default
driver
Creating volume "docker_peer0.org2.example.com" with default
driver
Creating orderer.example.com ... done
Creating peer0.org2.example.com ... done
Creating peer0.org1.example.com ... done
Creating cli ... done
CONTAINER ID IMAGE
COMMAND CREATED
STATUS
PORTS NAMES
fb943546dc4f hyperledger/fabric-tools:latest
"/bin/bash" 3 seconds ago Up Less than a
second
cli
d0a9bed586c3 hyperledger/fabric-peer:latest "peer
node start" 6 seconds ago Exited (139) 2 seconds
ago
peer0.org1.example.com
a2bd075ecac5 hyperledger/fabric-orderer:latest
"orderer" 6 seconds ago Up 2
seconds 0.0.0.0:7050->7050/tcp,
0.0.0.0:7053->7053/tcp orderer.example.com
67f4a76afb85 hyperledger/fabric-peer:latest "peer
node start" 6 seconds ago Exited (139) 1 second
ago
peer0.org2.example.com
DOCKER_IMAGE_VERSION is empty, and the peer containers are
exiting with code 139.
Is this a bug?
--
Nikos Karamolegkos
R & D engineer at ICS-FORTH
Telecommunications and Networks Lab (TNL)
