Closed arunramachandran15 closed 9 months ago
Found solution in Readme if this repo to customise the CA image version.
export PEER_IMAGE=hyperledger/fabric-peer export PEER_VERSION=2.5.0
export ORDERER_IMAGE=hyperledger/fabric-orderer export ORDERER_VERSION=2.5.0
export CA_IMAGE=hyperledger/fabric-ca
export CA_VERSION=1.5.6.
kubectl hlf ca create --image=$CA_IMAGE --version=$CA_VERSION --storage-class=standard --capacity=1Gi --name=org1-ca
Thanks!
What happened?
I installed the beval=operator-fabric using the below command. helm install hlf-operator --version=1.9.0 -- kfs/hlf-operator
When I tried to install the CAs for Org1, Org2 and Orderer suing "kubectl hlf ca create" command, it uses hyperledger/fabric-ca:1.4.9 as docker image and throws imagepullbackoff error.
I also tried to directly pull the docker image to my local m1 laptop and it throws the below error.
docker pull hyperledger/fabric-ca:1.4.9 1.4.9: Pulling from hyperledger/fabric-ca no matching manifest for linux/arm64/v8 in the manifest list entries
Manual docker pull for fabric-ca:1.5.0 works fine.
What did you expect to happen?
CA pods should have been running without image error.
Operator should be customisable to run fabric-ca:1.5.x, so that this error doesn't happen in m1 mac for development and PoC purposes.
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Kubernetes version