an error when installing chaincode on peer node

[vanitas92]

an error when installing chaincode on peer node

[vanitas92]

Hi @zhangfuli ,

Please open new issue if you have different request not related from original poster in an already closed issue, otherwise it makes it difficult to track issue requests.

As per your request, this could be due to two possibilities, either the External builder was not correctly mounted on the peer (make sure you have the configmap from the builders-config.yaml file in org1 folder applied) or the External Builder did not detect the external value in the metadata.json file and fellback to original Docker building implementation, which is intentionally avoided in this project.

For the first possibility, if you have been following the tutorial i highly doubt it is the issue since the configmap needs to be deployed previously the deployment of the peer, which in case of absence of it, the peer would not be able to start.

For the second possibility, make sure you had packaged correctly the chaincode format as explained in the tutorial, otherwise the external builder would not be able to detect it and install it as external chaincode. Check the logs of the peer (kubectl logs peer_pod_name -n hyperledger | grep external) and see what message outputs the external builder after executing the install command.

[vanitas92]

This is the first time i see this error. Seems like the genesis block has not been encoded correctly. Can you try to start from the beginning and see if it happens again?

[zhangfuli]

I got an error when installing chaincode on peer node too, but I got this:

Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: cannot connect to Docker endpoint

So it seems it cannot connect to the Docker endpoint. But I cannot find how to fix this.
If you have an idea, it would help a lot!

[zhangfuli]

@vanitas92 Thank you for your reply
I have found the problem that these 3 scripts have no execution permissions in the buildpack/bin folder.

[vanitas92]

I will close this issue due to it seems to be resolved now and inactivity.