liveBook · Manning

Container

As explained in Google Anthos in Action

A containerized application is an application packaged to run inside one or more containers with its required dependencies.

A container packages an application with the runtime, system tools, libraries, code, configuration, and settings required for execution. Containerized applications can modernize VM workloads without requiring a complete rewrite. section 15.0 section 16.6

A containerized deployment typically separates application responsibilities from platform responsibilities:

  • Application artifacts hold user-mode system content and application services. section 15.3.2
  • Kubernetes manages networking, logging, monitoring, OS kernels, drivers, and persistent-volume integration. section 15.3.2
  • Container density can exceed VM density because multiple containers share underlying infrastructure and avoid duplicating operating-system resources. section 15.1.1
  • Security depends on correct platform configuration: shared host kernels create breakout risk, while hypervisors also have exploitable vulnerabilities. section 13.2

Migrating a VM workload

A migration workflow can produce a Docker image, Dockerfile, deployment YAML, user services, and persistent-volume definitions from a virtual machine. The resulting artifacts can run on Anthos or another Kubernetes-conformant distribution. section 15.3.2 section 15.3

Figure 15.2 Anthos Migrate: From virtual machines to containers
15-02

Use the architecture figure to trace how a virtual machine becomes application containers, deployment artifacts, and Kubernetes-managed storage. section 15.3.2

How Google Anthos in Action covers it

How deep it goes
Explains migration artifacts, storage, platform delegation, density, and security risks, but does not detail application-specific container construction.
Examples
Uses VM migration, Docker images, Dockerfiles, deployment YAML, system containers, and Kubernetes persistent volumes as concrete artifacts.
What it assumes
Assumes familiarity with virtual machines and Kubernetes while emphasizing that secure operation requires understanding platform security fundamentals.
What you can do after
Evaluate and plan VM-to-container migrations with portability, density, storage, operational, and security implications in view.
How it connects
Connects containers with virtual machines, Kubernetes, persistent volumes, microservices, service meshes, and CI/CD.

Also explained in

Compare how 27 books explain container →

Related concepts

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