liveBook · Manning

Container image

As explained in Software Security for Developers

A container image is an immutable package containing an application and the files, metadata, and runtime components needed to execute it in a container.

A container image packages an application for execution in a container, including the files, metadata, and runtime components it needs. In Kubernetes, it is the deployable application artifact that must be created securely before deployment. section 3.2

Creating an application container is straightforward, but common examples can produce insecure images. Secure image creation is a developer responsibility, while platform engineers provide and secure the Kubernetes cluster. section 3.2 section 3.5

Secure image work connects to the surrounding Kubernetes workflow:

  • Create the image with secure Dockerfile or cloud-native buildpack practices. section 3.2
  • Deploy it with Kubernetes manifests that follow security best practices. section 3.2
  • Treat the image and deployment configuration as separate responsibilities from cluster installation and security. section 3.5

How Software Security for Developers covers it

How deep it goes
Identifies insecure image examples and points to Dockerfiles and cloud-native buildpacks, without detailing image-building procedures.
Examples
Uses Dockerfiles, cloud-native buildpacks, secure Kubernetes clusters, and deployment manifests as practical artifacts.
What it assumes
Assumes basic Kubernetes knowledge while teaching that developers own application packaging and platform teams own cluster security.
What you can do after
Build secure container images and pair them with Kubernetes manifests that follow security best practices.
How it connects
Connects container images with Kubernetes, Dockerfiles, cloud-native buildpacks, deployment manifests, and platform engineering.

Also explained in

Compare how 25 books explain container image →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Security for Developers. The section links point to the parts of the book it draws on.