Re: Deprecation of Docker Runtime in Kubernetes - No access to local docker socket #docker #hyperledger-fabric #fabric

Alexandre Pauwels

HLF 2.x introduced external chaincode builders and chaincode as an external service. With minimal changes to your chaincode package, you can deploy your chaincode as a separate pod within a k8s cluster exposing a port that your peer is then instructed to communicate with for chaincode execution. No more need to build and run chaincode with a dind container. We just made the switch and it was fairly painless.


On Tue, Jan 19, 2021, 12:56 <chintanr97@...> wrote:
Hi Team,

With us marching slowly towards end-of-life for Docker as a runtime environment in Kubernetes, and containerd turning out to be default for latest Kubernetes version on most cloud providers, I am thinking about the process of "chaincode image building and container creation" using the HLF peer. 

For HLF v1.4.x and HLF v2.x with internal builders, the chaincode containers could no longer be simply created with the help of /var/run/docker.sock file - as the access to it will be denied with the new "containerd" runtime in Kubernetes. 

I wanted to learn about how are we planning in supporting chaincode instantiation through peer (both, in HLF v1.4 or in HLF v2), once the old versions of Kubernetes reach end-of-life and existing users will be looking to upgrade to these latest Kubernetes versions.

Chintan Rajvir 

Join { to automatically receive all group messages.