A container image is a frozen, executable package of an application, its runtime, and its dependencies. Like a standardized shipping container, it gives software a predictable box to travel in: containers launched from the same image are identical. section 9.4.2
That consistency comes with practical tradeoffs:
- Portability: package only what the application needs, so an image built on a laptop can run the same way on an AWS server. section 9.4.2
- Operations: running containers still incur costs, and large fleets need an orchestrator such as Kubernetes to place and restart them. section 9.4.2
One build, matching servers
An automated pipeline can package code into one immutable image and deploy it across the fleet. This avoids forgotten servers running a different, older version. section 13.9.3































