liveBook · Manning

Container

As explained in Azure Security

A software container is an isolated executable environment that packages an application and its runtime requirements while sharing the host operating system.

A software container packages an application with its code, dependencies, configuration files, and runtime environment into an executable unit. A container image acts as a reusable blueprint, while the container is a running instance of that image. section 4.3.1

Containers support portable, efficient application delivery:

  • Build an image on a local machine, then move the same image through development, testing, staging, and production environments. section 4.3.1
  • Run multiple containers on one operating system, allowing applications to share the host OS and start quickly. section 4.3.1
  • Store and retrieve images through a container registry before deploying them. section 4.3.1
  • Use Kubernetes to automate container deployment, management, visibility, scaling, load balancing, networking, and desired configuration. section 4.3.3

Container security differs from server security because containers are lightweight, short-lived, and immutable. Updating or patching a running container is not supported; rebuild the image and redeploy it instead. Their dynamic behavior also requires monitoring that can observe pods and containers, rather than relying only on traditional server tools. section 4.4

Figure 4.6 Multiple containers can run on a single OS hosted on a virtual machine.

Visualize multiple containers running on a single operating system hosted by a virtual machine. section 4.3.1

How Azure Security covers it

How deep it goes
Explains images, portability, shared operating systems, orchestration, immutability, and monitoring, but stops short of configuration commands.
Examples
Uses shipping containers as an analogy and illustrates multiple containers running on one operating system hosted by a virtual machine.
What it assumes
Assumes basic familiarity with applications and operating systems while defining container images and runtime contents directly.
What you can do after
Evaluate container deployments and choose image rebuilding, redeployment, orchestration, and container-aware monitoring practices.
How it connects
Connects container images with container registries, operating systems, virtual machines, Kubernetes, pods, and monitoring.

Also explained in

Compare how 27 books explain container →

Related concepts

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