500 - failed to invoke backing implementation of 'InstallChaincode'
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the Contract deployment tutorial and reproduce the commands from asset-transfer-basic/chaincode-go, including go mod vendor, go build, and peer lifecycle chaincode package. Inspect the ff deploy fabric entry point and the Docker-based peer lifecycle install that reports the protobuf build error; done means the sample chaincode installs successfully without the 500 error.
Written by the indexing model from the issue text.
Description
The error occurs when executing the implantation process described in: Contract deployment.
$ export GOPATH="/opt/go-fabric/go"
$ export GIT_USER_ID="pssilva"
$ mkdir -p $GOPATH/src/github.com/$GIT_USER_ID
$ cd $GOPATH/src/github.com/$GIT_USER_ID
$ git clone https://github.com/hyperledger/firefly-samples.git
$ cd $GOPATH/src/github.com/$GIT_USER_ID/firefly-samples
$ cd asset-transfer-basic/chaincode-go
$ go mod vendor
$ go build
$ bin/peer lifecycle chaincode package -p . --label asset_transfer ./asset_transfer.zip
$ ff deploy fabric acmecorp-erp asset_transfer.zip firefly asset_transfer 1.0
Error: docker run --platform linux/amd64 --rm --network=acmecorp-erp_default
-e CORE_PEER_ADDRESS=fabric_peer:7051
-e CORE_PEER_TLS_ENABLED=true
-e CORE_PEER_TLS_ROOTCERT_FILE=/etc/firefly/organizations/peerOrganizations/org1.example.com/peers/fabric_peer.org1.example.com/tls/ca.crt
-e CORE_PEER_LOCALMSPID=Org1MSP
-e CORE_PEER_MSPCONFIGPATH=/etc/firefly/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp
-v /opt/go-fabric/go/src/github.com/pssilva/fabric-samples/asset-transfer-basic/chaincode-go/asset_transfer.zip:/package.tar.gz
-v acmecorp-erp_firefly_fabric:/etc/firefly hyperledger/fabric-tools:2.3
peer lifecycle chaincode install /package.tar.gz
[1] Error: 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: Error returned from build: 2 "google.golang.org/protobuf/internal/flags
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kube-tarian/sigrun#202 ·
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eugenioenko/ttt#1085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fullsend-ai/fullsend#8688 · 1 comment ·
Maintainers usually reply within 1 day
-
question raised-by:verifier
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
medici-finance/assay#4013 ·
Maintainers usually reply within 1 day