CRI: The Second Boom of Container Runtimes
Containers did have a boom when Docker Inc bring this concept to industry for the fist time. We then had Docker and rkt, we witnessed the start of runC and OCI. And then with the rise of Kubernetes co …
| Talk Title | CRI: The Second Boom of Container Runtimes |
| Speakers | Xu Wang (Senior Staff Engineer, Ant Financial), Lei Zhang (Staff Engineer, Alibaba) |
| Conference | KubeCon + CloudNativeCon Europe |
| Conf Tag | |
| Location | Copenhagen, Denmark |
| Date | Apr 30-May 4, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Containers did have a boom when Docker Inc bring this concept to industry for the fist time. We then had Docker and rkt, we witnessed the start of runC and OCI. And then with the rise of Kubernetes community, all those container runtimes begin to become quite and hidden behind the orchestration layer, which is expected. But in 2017, we begin to hear more voice of container runtimes again. cri-o, containerd, Kata. But why? In this talk, we would like to say something about technical details of CRI, the killer weapon which brought new energy to “boring” container runtimes. We will introduce what is CRI spec and shim, how they are designed, how they work with CNI and CSI, also, what’s the difference between those shims and why Kata is special. We will also demo how to write a CRI shim from zero. The second boom of containers is around, while this time it happens in Kubernetes community.
