Containers and Images: The Big Picture
Containers revolutionize how software is used, and images revolutionize how software is distributed. This course will demystify both so you're well prepared to exploit the benefits in your own work.
What you'll learn
I'm sure you've heard of containers, but have you heard of images? In this course, Containers and Images: The Big Picture, you'll delve into both images and containers. First, you'll explore containers and why they're useful. Next, you'll learn why containers wouldn't be a big deal if it weren't for images, and how both have revolutionized software development, distribution and use. Finally, you'll discover how to foster adoption by starting outside of production. By the end of this course, you'll be well equipped to benefit from containers and images effectively in practice.
Table of contents
- Containers Are Processes 3m
- Containers Are Isolated Processes 2m
- A Lack of Isolation Causes Many Problems 2m
- A Process Is a Means of Isolation 2m
- Virtual Memory Isolation 4m
- Default Isolation 1m
- Opt-in Isolation 3m
- chroot Isolation 2m
- Plan 9: Per-process Namespaces and Union Directories 1m
- Capabilities Isolate Privileges 2m
- Mount Namespaces 4m
- Isolating Resource Usage with Control Groups 2m
- Limit CPU Usage with a cgroup 2m
- Grouping Processes: Namespaces vs. Control Groups 2m
- What Is a Mount Namespace? 4m
- Isolating the Hostname with a UTS Namespace 2m
- IPC Namespaces 2m
- Network Namespaces 4m
- Isolating Process IDs with PID Namespaces 4m
- User Namespaces 1m
- Containers Coalesce Process Isolation 3m
- Simplifying Software Distribution 2m
- Filesystems Do Not Come from Thin Air 5m
- Images Provide Pre-built Filesystems 5m
- Isolated Filesystems in Milliseconds with Images 3m
- Docker Runs Software from a Pre-built Filesystem 4m
- Images Are Layered for Reuse and Efficiency 5m
- It Is Incredibly Easy to Create New Images 2m
- Image Registries Provide the Infrastructure for Image Trust 2m
- From OCI Image Format to Runtime Filesystem Bundle 3m
- Runtime config.json 5m
- OCI Proves the Importance of Images 2m
- Docker Image Manifest V2 Schema 2 3m
- Multi-architecture Image Index and Manifest List 1m
- runc Is Everywhere 2m
- VMs Can Use OCI Images Too 2m
- Running a Container with containerd and runc 2m
- Kata VMs Are Nearly as Fast as Containers 2m
- Images Simplify Software Distribution and Installation 3m
- Physical Resources Are the Biggest Constraint 4m
- Nothing Inherently Wrong with the Single Machine Model 1m
- It Would Be Nice to Have One Giant Machine 1m
- Boundary between Provisioning Nodes and Running Apps 2m
- Picking a Container Runtime 3m
- Schedulers 2m
- Resource Definitions via Desired State Configuration 1m
- Service Connectivity 2m
- Single Node Networking 4m
- Multi-node Networking Is a Cluster Service 3m
- Storage Challenges Aren't New 4m
- Cloud Native Lanscape 1m
About the author
Wes Higbee is passionate about helping companies achieve remarkable results with technology and software. He’s had extensive experience developing software and working with teams to improve how software is developed to meet business objectives. Wes launched Full City Tech to leverage his expertise to help companies delight customers. Although his primary focus is on outcomes, implementation often includes technical competency. Wes frequently speaks about impactful aspects of software developm... more