genesis | An Attempt to learn Operating System development

I have fixed it. The issue I was facing was because of not setting the CORE_PEER_TLS_ENABLED = true for CLI pod.

One thing I have got learn from this whole model, whenever you see TLS issue, first to check for would be checking CORE_PEER_TLS_ENABLED variable. Make sure you have set it for all the pods or containers you are trying to interact with. The case can be false(for no TLS) or true(for using TLS) depending on your deployment. Other things to keep in mind is using the correct variables of fabric including FABRIC_CFG_PATH, CORE_PEER_LOCALMSPID, CORE_PEER_TLS_ROOTCERT_FILE, CORE_PEER_MSPCONFIGPATH and some others depending on your command.

As I said in the comment, the problem was in your getAge method, it was always returning 0. The return inside the forEach doesn't return the value off of the loop. Please have a look at the following approach

I openned two JIRA to understand this problem. See the links below:

1. https://datastax-oss.atlassian.net/browse/SPARKC-652
2. https://datastax-oss.atlassian.net/browse/JAVA-2945

Try Using this

When you create an initContainer and execute this command:

command: ['sh', '-c', 'tar -xvf /hlf/channel-artifacts/channel-artifacts.tar']

it runs in default for this container path. I checked this by adding pwd and ls -l commands.

Whole line is:

command: ['sh', '-c', 'tar -xvf /hlf/channel-artifacts/channel-artifacts.tar ; pwd ; ls -l']

From an initContainer you can get logs by:

kubectl logs fabric-orderer-01-xxxxxx -c init-channel-artifacts

Output was:

The selfbalance opcode was implemented in the Istanbul chain fork (source).

You need to allow the fork in your genesis.json

Try something like this:

I'm pretty sure you cannot affect a subaccount from the parent like this. If someone deletes the near account, your account would not be affected. and unless the near account itself is holding a FullAccess key to subaccounts, it doesn't control them

This would also be easy to test. On TestNet try creating a subaccount and deleting it from the parent. If you don't have a FullAccess key to an account then your DeleteAccount action will be rejected by the network.

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