Terminology: Container Engine vs container runtime
Hello,
want to get my terminology right. Could someone clarify the difference between container engine and container runtime? And examples of each?
From the official documentation I read:
"All nodes run the kubelet and kube-proxy, as well as the container engine, such as Docker or cri-o, among several options. Other management daemons are deployed to watch these agents or provide services not yet included with Kubernetes."
And from RedHat page I read:
A container engine is a piece of software that processes user requests, including command line options and image pulls. The container engine uses a container runtime, also called a lower-level container runtime, to run and manage the components required to deploy and operate containers. You likely will not need to interact with the container engine or container runtime.
So ok....cri-o is a container engine, which seems to take care of requests and leverage container runtimes like containerd to do the actual container instantiation? When I list nodes I can see what my kubernetes nodes use containerd as the container runtime. How can I know what container engine is being used?
Now, what is crictl ? Just a tool to interact with the container runtime?
ubuntu@master:~$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
master Ready control-plane 17h v1.27.1 192.168.122.186 Ubuntu 20.04.6 LTS 5.4.0-165-generic containerd://1.6.24
worker1 Ready 16h v1.27.1 192.168.122.131 Ubuntu 20.04.6 LTS 5.4.0-165-generic containerd://1.6.24
worker2 Ready 16h v1.27.1 192.168.122.99 Ubuntu 20.04.6 LTS 5.4.0-165-generic containerd://1.6.24
The reason for my question is that when i asked chat gpt it says otherwise:
I apologize for any confusion. CRI-O is indeed a container runtime, not a container engine. It is designed specifically to serve as a container runtime for Kubernetes. CRI-O is an implementation of the Kubernetes Container Runtime Interface (CRI), which allows Kubernetes to interact with container runtimes to create and manage containers on nodes within a cluster. While CRI-O performs the low-level tasks of running containers, it is not a high-level service like Docker, which can be considered more of a container engine.
To clarify:
A container engine (like Docker) is a higher-level tool that often includes features for managing container images, building containers, and more. A container runtime (like CRI-O) is a lower-level component responsible for the core tasks of creating and running containers.
In Kubernetes, CRI-O is used as the container runtime to handle the execution of containers, and it interacts with Kubernetes through the CRI to ensure container orchestration within the cluster.
Comments
-
Take my comment with a grain of salt as I am still a student. If I am wrong anywhere, please do tell me.
I think the line between container engine and container runtime is very blurry right now. It depends on how you define each and so it depends on who you ask. I think it is more important to understand the stack, what each component does, what you can plug-in/out and some key definitions like CRI, OCI-compliant runtime, etc.
From top-down, in Kubernetes you need to plug-in anything that implements/satisfies CRI (Container Runtime Interface). This interface was created by Kubernetes to standardize and off-load container creation/management. Kubernetes specifically defines these components as container runtimes and lists some examples such as containerd, cri-o.
These "CRI container runtimes"/container engines, such as containerd and cri-o, use, in turn, OCI (Open Container Initiative) compliant runtimes to run the containers. OCI was created to define standards/specs for containers. OCI-compliant runtimes are low-level runtimes that effectively run the containers. Containerd, by default, uses runc (an OCI-compliant runtime) and spawns instances of runc for each container. On cri-o you can plug in any OCI runtime.
crictl, initially developed for debugging, is a tool that interacts with anything that implements the CRI (containerd, cri-o, etc). Given that Docker itself uses containerd, theoretically you could use crictl to interact with/manage containers created with Docker, as long as you provide the correct runtime endpoint (e.g. unix:///var/run/docker/containerd/containerd.sock).
On the labs we have:
Kubernetes -----CRI----> containerd -----> runc (for each container)On the internet and some documentation I've seen containerd defined as a container engine (example Podman docs). RedHat, as per the definition you showed, defines containerd as a container engine and runc a container runtime as "you likely will not need to interact" directly with both (you can interact with containerd with Docker, nerdctl, cri-o). Some (or most, don't know which) also define anything to the left of containerd as a container engine (Kubernetes, Docker). Basically container runtime=OCI-compliant runtime only.
On the other hand Kubernetes, on its docs, defines anything that implements CRI, a container runtime. To add more to the confusion, Kubernetes lists Docker Engine as a CRI compatible container runtime.
So, given all of this, the exact answer to your question might be "complicated". Personally, when specifying container runtime I would always prefix OCI/CRI to avoid any confusion.
0 -
but runc is a container runtime as well isnt it? I thought out it would do the same function as containerd. Head spinning.
On the labs we have:
Kubernetes -----CRI----> containerd -----> runc (for each container)0 -
@CarlosValencia said:
but runc is a container runtime as well isnt it? I thought out it would do the same function as containerd. Head spinning.On the labs we have:
Kubernetes -----CRI----> containerd -----> runc (for each container)Oh now that I read more closely on containerd and runc:
containerd supports the OCI container image specification and the OCI runtime specification by utilizing runc as its low level OCI runtime with the possibility to extend it with plugins to support the Kubernetes’ Container Runtime Interface (CRI) as well. containerd adds implementation for some missing, yet desired, capabilities of runc, such as support for container image pull and push operations, and network interfaces and network namespaces management operations.
0
Categories
- All Categories
- 206 LFX Mentorship
- 206 LFX Mentorship: Linux Kernel
- 732 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 165 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 131 Cloud Native Developer IT Professional Program
- 119 Express Training Courses
- 119 Express Courses - Discussion Forum
- 5.9K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 219 LFD103 Class Forum
- 16 LFD110 Class Forum
- 32 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 2 LFD237 Class Forum
- 23 LFD254 Class Forum
- 680 LFD259 Class Forum
- 109 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 92 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 2 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 10 LFS158 Class Forum
- 4 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 111 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 49 LFS241 Class Forum
- 43 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 44 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 143 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 114 LFS260 Class Forum
- 151 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 199 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 2 LFW111 Class Forum
- 257 LFW211 Class Forum
- 176 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 753 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 350 Ubuntu
- 464 Linux System Administration
- 39 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 365 Off Topic
- 113 Introductions
- 171 Small Talk
- 20 Study Material
- 522 Programming and Development
- 291 Kernel Development
- 213 Software Development
- 1.1K Software
- 211 Applications
- 180 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 Installation
- 79 All In Program
- 79 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)