Unpacking the Container: A Deep Dive into Virtualized Container Technology
summary
Containers are actual Linux processes isolated by namespaces and limited by cgroups, not magic VMs; docker images are tarballs whose layers map to directories (lowerdir, upperdir, merged) with copy on write so the upperdir is ephemeral data. Market data shows real scale — Sysdig sees ~2 million containers in 2019 with Docker at ~79% and containerd ~18% — and practical tools include runc/OCI runtimes, registries like JFrog Artifactory and scanners like JFrog X‑Ray; note JVMs before java 11 are not fully container aware.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:29THE SWAG
- 3:03THE AGENDA
- 5:53SHARING LIMITED RESOURCES
- 7:01PROGRESS TOWARD VIRTUALIZATION
- 14:14WHAT DO WE ACTUALLY NEED/WANT?
- 16:34DOCKER, THE WHOLE PACKAGE
- 17:56BREAKING UP THE MONOLITH
- 20:51CONTAINER COMPONENTS
- 23:15FILESYSTEM DETAILS
- 28:54CONTAINER GOTCHAS - RUNNING AS ROOT
- 30:46CONTAINER GOTCHAS - NO CONSTRAINTS
- 31:46CONTAINER GOTCHAS - NEVER UPDATING
- 33:57CONTAINER GOTCHAS - JAVA/JVM GOTCHAS
- 36:22MANAGING YOUR IMAGES - ARTIFACTORY
- 38:17MANAGING YOUR IMAGES - XRAY
