Hi all, I am creating a network with CA roots and CA intermediates using fabric CA and docker compose. So far I have been able to correctly create the roots, intermediates, perform registration and en

#docker-compose #docker #fabric-ca

Hi Kavin, From what I can see, you commented out the docker configuration files, going to directly edit the server configuration files. This way it actually works but what I was trying to do was to us

#fabric-ca #docker

Hi, I encounter this error when I tried to start Orderer in docker-compose(CA and Peer nodes are started and has no error). 2022-03-04 07:24:40.036 UTC [orderer.common.server] initializeServerConfig -

#docker #x509

Hi, You must compile your own ARM64 images. You may want to follow instructions I prepared for this task and which are published here: https://github.com/maciejjedrzejczyk/hlf-arm64 Kind Regards, Maci

#docker #fabric-peer

Hello, I'm currently working on a project with three organizations and an orderer. So in order to do this, I created a new network, with its own configuration files and with a script that sets up ever

#docker #fabric-ca #fabric-orderer #orderer #organizations

Hello everyone, I am training on this example simple enough to deploy on two machines : https://www.rapidqube.com/hyperledger-fabric-2-0-on-multiple-hosts/ I'm trying to test it on two machines, I do

#docker

From what I have found so far in a limited bit of looking into the effects of the deprecation when it actually happens is that it will cause a breaking change to the Dind container. Although there is

#docker #hyperledger-fabric #fabric

I have actually solved the problem by adding the DNS (org.example.com, peer0.org1.example.com, etc) in the application's /etc/hosts. Thanks!

#docker #docker-compose #fabric

Hi Team, I have a kubernetes setup of HLF2.2 with Golang Chaincode and Nodejs SDK. I am performing load test on the network, when i try with 250 Concurrent thread, it shows unexpectedly chaincode inst

#fabric-sdk-node #fabric-chaincode #docker #fabric-kubernetes #network

Hi, I'm working with fabric docker containers to build an example and trying to avoid making a client application. What we need to do has to put a tag (e.g. a keyed hash of it) of the transaction in t

#hyperledger-fabric #docker

traffic can go out out does not mean that traffic can come in, so ping google does not really mean your necessary ports are open. as I have indicated earlier in this doc, https://github.com/litong01/m

#docker

There is no support for authenticating to a Docker registry within the peer. Iy your private registry requires authentication, then you will need to pull the images on the host where the Docker daemon

#fabric-chaincode #docker #hyperledger-fabric

Oh, my bad. I had downloaded fabric samples binaries, images, etc a few months back and also downloaded a new one last week only via git clone (so I think only the sample codes changed?). That probabl

#couchdb #docker #fabric

Hello, I would like to know what is the fastest way of developing chaincode and fabric-node-sdk with fabric v2 at the same time? For now we are using `fabric-samples/test-network` but it's starting ov

#fabric #docker

Hi David, thanks for the reply, I've recreated the network and now it seems to work, I'll save save your hint for possible future problems. Mattia IFIN SISTEMI S.R.L. a socio unico Via G. Medici 9/a 3

#couchdb #docker #fabric #fabric-questions

Is there anyway to increase the wait time on a chaincode instantiation? The default seems to be about 10 minutes but I have a peer with low bandwidth and the docker image download combined with the co

#fabric #docker #fabric-chaincode #fabric-questions #hyperledger-fabric

I have installed hyperledger fabric 2.0.0. When I try to run the fabcar example, I am getting an error like this "Error: error getting endorser client for channel: endorser client failed to connect to

#fabric-questions #hyperledger-fabric #docker #fabric-chaincode #couchdb

BatchSize actually falls under the Orderer group and not the Application group. Therefore, you need a majority of the orderer admins to sign the config update. Given you state this is a simple network

#fabric #docker #fabric-ca

We are not using CLI. We are creating channel using Node SDK and creating infrastructure using shell script. We are using Raft consensus with 5 orderer and Raft cluster is working fine. Orderers elect

#fabric-sdk-node #docker #raft #consensus #cal-notice

Hi Team, While pulling the orderer image i am getting the below issue . Any idea ? Environment - Azure - Ubuntu VM - 16.04 LTS ``` Pulling orderer3 (hyperledger/fabric-orderer:1.4.3)... ERROR: Get htt

#fabric #docker