Deploying Java chaincode #docker #fabric-peer
Maciej Jedrzejczyk <matanyahu@...>
Hi,toggle quoted messageShow quoted text
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
The 2.3 release was an interim/development release. 2.2 being the LTS. There wasn't a docker image for farbic-javaenv:2.3 released. The quick way around this is to pul down the fabric-javaenv:2.2 and retag it as 2.3
Hope that helps.
Matthew B White IBM Blockchain Solutions Architect
Email me at WHITEMAT@...
Note: restricted availability for meetings 14:30 to 17:00 UK Tuesday
IBM United Kingdom Limited, Hursley Park, Winchester, Hampshire, SO21 2JN
"The wrong answers are the ones you go looking for when the right answers stare you in the face"
----- Original message -----
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
I am running the fabric test-network on a MacBook with M1 chip. I modified the script that downloads images & binaries in a waythat it gets the amd64 images.
The images run fine. However, when I try to deploy a Java chaincode, I run into following issue:
+ peer lifecycle chaincode install mychaincode.tar.gz+ res=1Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image build failed: docker build failed: Failed to pull hyperledger/fabric-javaenv:2.3: no matching manifest for linux/arm64/v8 in the manifest list entriesChaincode installation on peer0.org1 has failedDeploying chaincode failed
It seems that somewhere a check on system architecture is made, and that docker is trying to pull hyperledger/fabric-javaenv for arm64 which doesn't exist.
I am looking for a way to force a pull of the amd64 image, because I assume that one will work as well. I can't seem to find where/why docker is trying to pull the arm64 image.
Is there a way to do this?
Have a great day.