Things I Wish I Had Learned Earlier About Containers: Lessons from a Seasoned Linux...
summary
Explains that containers are just isolated Linux processes and shows which kernel features make them work: cgroups and namespaces control CPU, memory and visibility; images are immutable templates; runtimes (runc, containerd) set up namespaces; engines (podman, Docker) provide the user CLI. Demonstrates port mappings and bind mounts versus engine volumes with examples like nginx and Ghost, uses commands like podman run -d --network mynet -v /host/path:/container/path, and notes systemd integration and occasional live-demo flakiness.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:55Why this talk
- 12:52Kernel features behind containers
- 24:32Persistent data and volumes
- 30:49Container networking
- 39:29Orchestration and next steps
- 41:57Q&A
related talks
33mLinux Container Internals
01h 32mContainers – A Look Under the Hood
23mLife of a Container
50mUnderstanding Linux Containers by Building One from Scratch
39mContainers are Linux - but what does it mean?
48mUnderstanding Container Engines by Demo™
01h 31mTutorial: Using Linux Primitives to Build Your Own Containers
29mLinux containers 102: beyond the basics