Let’s break the workflow :
✅ When a request comes to start a #container, #kubelet calls the CRI that invokes the internal CRI-O daemon in the #kernel
✅ The daemon uses a compliant storage and image library on disk
✅ The CRI-O interacts with a remote registry to pull the image if not present on disk while the daemon exposes a [#grpc] server with endpoints to create, start, stop (and many more other actions) on the #containers.
✅ Under the hood, cri-o can use any OCI-compliant [low-level] runtimes to work with containers
✅ However the default one is again #runc that interacts with #linux kernel to invoke processes in namespace & #Cgroup context!
Latest posts by Rajesh Kumar (see all)
- What is ZooKeeper? - April 29, 2024
- What is Mobile Virtual Network Operator? - April 18, 2024
- What is Solr? - April 17, 2024