Closed ravinayag closed 8 months ago
Can you please confirm the below,
kubectl exec -it -n {NAMESPACE} {PEER_NAME} -c dind-daemon -- sh
docker images
docker ps -a
The fabric version i'm using the latest 2.5 over EKS cluster. The dind container was running with no issues and i was able to see the CC container was up inside the dind service.
Unfortunetly im not able to reproduce the above and i strategically moved to CCAAS service methods and its perfectly working now.
we can close this issue.
I Appreciate and Thank you for all your efforts.
thanks @ravinayag for your response. You are welcome to contribute the CCAAS support to the existing version as well.
Sure i add up the CCAAS service.
After following the documentation, Chaincode container were not able to start after the commit procedure. Stuck with troubleshooting the current issue.. Could you share/upload the Dockerfile for dind image that used in the peers. Do i need modify the core.yaml for the external chaincode container instantiation ?
Ref Error: