Hi, I'm currently deploying a network using HLF Fabric 1.4.0 and I've got a problem concerning the instantiation of a chaincode. In fact, the Kubernetes cluster on which I'm deploying it cannot access

#fabric #fabric-kubernetes

Hi I have deployed the fabric-cli in K8s and able to install the go chaincode on peer. But while instantiating the chaincode I am getting below error- Error: could not assemble transaction, err propos

#fabric #fabric-kubernetes

Hi You should attach your orderer and peer logs to give more details because the errors are often blurry in HLF :) You may have an issue inside your configtx.yaml file or in your K8S configuration (e.

#fabric #fabric-kubernetes #fabric-questions

Hi, In Kubernetes, the chaincode container management is currently difficult. You won't be able to easily access it because of the way the container is created. You can access it using two options: 1)

#fabric-kubernetes

Thank you for your insight Prasanth. I'll get a look at my configuration to ensure I didn't do that kind of mistake I'll keep you posted once I solve my problem Thanks again JG

#fabric-kubernetes #fabric

Just wondering if the system can be modified to be able to choose between 1) native docker 2) native k8s 3) simple fork/exec, which would work equally well in ALL environments. I have not looked at th

#fabric-kubernetes

Jk, My attempt at your questions below. Anyone please correct me if wrong. 1. What is the best setup for a resilient network? How many orderers and peers should I have? Are 2 orderer pods and 3 peer p

#fabric-kubernetes #fabric-questions #fabric-sdk-java

What command did you use to install and instantiate it? The answer lies there. Whatever name you have given after -n tag is what the installed chaincode name. In your case, it isn't 'mycc'. So, in you

#fabric #fabric-kubernetes

Hi Experts, I am new to this framework and exploring it everyday. Need some clarifications on deploying an application on a fabric network having peers,orderer created on multiple machines As per my u

#fabric #fabric-questions #fabric-kubernetes

I deployed fabric 1.2 on k8. there are 2 orgs and all the peers successfully joined the channel and installed example chaincode. While running peer chaincode instantiate -o orderer.test:7050 --tls --c

#fabric-kubernetes

Hi, I deployed fabric network in a kubernetes cluster. I'm not able to join a channel that created in a peer cli and consistently getting policies evaluation error. The commands I used are ~/bin/confi

#fabric-kubernetes #fabric

I am trying to deploy a bare minimal peer node on kubernetes: No channel, no chaincode. Just to start the server. Here is output from console INFO 001 Starting peer: Version: 1.2.0 Commit SHA: cae2ad4

#fabric-kubernetes #fabric

Thanks a lot for the suggestions, always open for them. Yes, I agree on your part that one of the crucial aspect of K8s manifests is the resource/mechanism ,since, few days back there was a discussion

#fabric-kubernetes