Running Containers and the Container Runtime: Engines, runc and the Lifecycle | Containers Ep 11

When you type docker run, a lot happens behind the scenes. This lesson peels back the layers between your command and the process that actually starts. We begin with the dependency matrix from hell and how containers escape it, then step into the container itself as a lightweight, isolated environment. Next we map the runtime landscape: container engines, container managers, and the low-level runtimes underneath, including how tools like Docker, containerd, CRI-O and Podman relate to each other. We trace how data and commands flow through the container stack, walk the full build, upload and execute lifecycle, and close by looking at what happens when a container blows past its memory limit and the OOM killer steps in. In this lesson you will learn: Engines vs managers vs low-level runtimes Where Docker, containerd, CRI-O, runc and Podman fit Single container vs orchestrated sets The build, upload and execute lifecycle Memory limits and the OOM killer Chapters: 0:00 Introduction: Running Containers and the Runtime 0:49 Lesson roadmap 1:02 Section 1: Escaping dependency hell 2:47 Section 2: Enter the container 3:47 Containers isolate environments 4:37 Fast startup and portability 5:15 Section 3: The runtime landscape 5:59 The container manager 7:13 Engines vs managers 8:01 Section 4: Inside the container stack 9:56 Section 5: Managing the lifecycle 12:37 What happens when a container exceeds memory limits? 13:05 The OOM killer 14:07 Wrap up: What abstractions come next? This is episode 11 of the containers series. Watch the full playlist in order to build your container skills from the ground up, and subscribe so you do not miss the next lesson. Cybersecurity Masterclass by Joshua Moses | CyberTrace Foundation. #Course Lab Guide: https://github.com/joshuanmoses/Cyber...