2

When running hyperledger fabric sample, the orderer container gets exited within 1 sec. When logging the container I get the following error:

Orderer capability V1_4_4 is required but not supported

The image below shows that the binary, images and orderercapacities are based on version 1.4.4.

enter image description here

What am I doing wrong?

M Yil
  • 877
  • 1
  • 14
  • 35
  • Can you replace the image with a plain-text description of what behavior you're seeing, and provide a [mcve] including any relevant code? – David Maze Dec 30 '19 at 17:27
  • It's almost the same problem as this post "https://stackoverflow.com/questions/52787139/channel-capability-v1-3-is-required-but-not-supported-making-my-first-network-i" – M Yil Dec 30 '19 at 18:49
  • But the problem with mine, versions seem to be fine. Everything is 1.4.4 based. – M Yil Dec 30 '19 at 18:50
  • I had to face the similar issue when my images, binaries and fabric samples were not in sync. Please make sure once more if this is not the case for you. – Pandit Dec 31 '19 at 12:02
  • @Pandit What I tried using images and binaries based on 1.4.4. I also modified the configtx.yaml, in the capabilities I said, as the image shows: V_1_4_4: true. What more can I do, did I forget something? – M Yil Dec 31 '19 at 14:28
  • Can you share your orderer config file, the only things we see from this image is that you've defined the Orderer capabilities pointer, never that it's been consumed and that the structure of the file is correct – lindluni Dec 31 '19 at 23:40

1 Answers1

0

There is no v1_4_4 for orderer capabilities.

Only v1_4_2 and v1_1 are supported by Fabric v.1.4.4

refer sample configtx.yaml file

https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/configtx.yaml

Santhosh S
  • 782
  • 5
  • 17