Waiting for chaincodeinstantiate job to be completed ::

[advissor]

The step to point to tcp://docker:2375 was performed

Linux

$ sed -i s#unix:///host/var/run/docker.sock#tcp://docker:2375# configFiles/peersDeployment.yaml

ubuntu@ip-xxxxxxxxxxxxx~/blockchain-network-on-kubernetes$ cat configFiles/peersDeployment.yaml | grep tcp://docker:2375
value: tcp://docker:2375
value: tcp://docker:2375
value: tcp://docker:2375
value: tcp://docker:2375

Client Version: v1.13.8
Server Version: v1.13.8+IKS

NAME READY STATUS RESTARTS AGE
blockchain-ca-54d7b4ddfc-jxrzh 1/1 Running 0 14m
blockchain-orderer-67c9ff777d-mpdqm 1/1 Running 0 14m
blockchain-org1peer1-7bd4879446-mqm52 1/1 Running 0 14m
blockchain-org2peer1-8fc4fbcfc-grk2t 1/1 Running 0 14m
blockchain-org3peer1-6cf5d4875f-jn776 1/1 Running 0 14m
blockchain-org4peer1-68699bdd8f-l5dhp 1/1 Running 0 14m
chaincodeinstall-49nq2 0/4 Completed 0 14m
chaincodeinstantiate-5llqr 0/1 Error 0 14m
chaincodeinstantiate-gnhpg 0/1 Error 0 14m
copyartifacts-dtblm 0/1 Completed 0 15m
createchannel-dwvrl 0/2 Completed 0 14m
docker-dind-545d6b5986-2l7cz 1/1 Running 0 15m
joinchannel-dh8s6 0/4 Completed 0 14m
utils-l6s97 0/2 Completed 0 15m

ubuntu@ip-xxx-xx-x-xx:~/blockchain-network-on-kubernetes$ kubectl logs chaincodeinstantiate-5llqr
2019-07-29 20:36:56.351 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2019-07-29 20:36:56.351 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: cannot connect to Docker endpoint

From what I've seen in other older issues, substitution should have helped. But apparently not in my case.

[advissor]

Chaincode Instantiation Completed Successfully Network Setup Completed !!

Issue :
Docker has released a new version 19.03 https://hub.docker.com/_/docker?tab=tags which enabled TLS by default.

Starting in 18.09+, the dind variants of this image will automatically generate TLS certificates in the directory specified by the DOCKER_TLS_CERTDIR environment variable.

So, solutions for many people here is to fallback to docker:18.09-dind

---Workaround--

File : blockchain-network-on-kubernetes/configFiles/docker.yaml
Line 35 , to be changed to something like : image: "docker:18.09-dind"

[maheshwarishikha]

@advissor , thanks for providing updates. It is really helpful.

[desouzag]

Thanks a lot @advissor

[woodyjon]

Hello,

I changed at line 35 to image: "docker:18.09-dind" but I still have the same error. "Waiting for chaincodeinstantiate job to be completed" repeating indefinitely until it stops with "Chaincode Instantiation Failed".

The logs of the job:
Error: error endorsing chaincode: rpc error: code = Unknown desc = access denied: channel [channel1] creator org [Org1MSP]

My setup:

• locally with minikube
• kubernetes and kubectl v1.15.9 (because of https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/)

Has anyone any idea?

Thank you!