A container image packages an application as an executable artifact for local Kubernetes development and cloud-native release workflows. OCI image and container image are used interchangeably; the OCI image format is widely adopted by Docker, Podman, and other container runtimes. section 1.3.9 section 3.2
Treat image construction as a developer workflow concern:
- Build the image after validating a change, while accounting for build time and the external services needed to run the application. section 1.3.5
- Use a Dockerfile to define the packaging recipe, recognizing that production-ready images require more care than a basic recipe. section 3.2.1
- Arrange application content and libraries across OCI layers so unchanged content can be cached locally and reused by registries and runtimes. section 3.2.1
- Keep frequently changing application code separate from stable dependencies when possible; otherwise, a small code change can rebuild an entire layer. section 3.2.1
A small application change
For a Java service, copying the JAR into a top image layer means adding one HTTP endpoint can rebuild that whole layer, even when libraries and dependencies remain unchanged. section 3.2.1































