1.6 Compare and contrast containerization concepts.
Containers package an application and its dependencies. At scale they need orchestration, networking, storage and trusted image sources.
Concepts
- Stand-alone
- Containers run individually on one host (e.g. docker run). Fine for development; no automatic healing or scaling.
- Workload orchestration
- Platforms like Kubernetes schedule containers across nodes, restart failures, scale and roll out updates.
- Networking
- Containers get virtual network interfaces; orchestrators add service networking and policies.
- Port mapping
- Exposing a container port on a host port (e.g. host 8080 to container 80). Only map what must be reachable.
- Storage types
- Containers are disposable, so storage choices determine what survives.
- Persistent volumes
- Storage that outlives a container, for databases and uploads.
- Ephemeral storage
- Storage that disappears when the container stops; fine for caches and temp files.
- Image registries
- Repositories that store container images. Use private registries, signed images and vulnerability scanning.
Check your understanding
Loading quiz…
Original CoreQ Academy material, mapped to objective 1.6 of the publicly available CompTIA Cloud+ CV0-004 exam objectives (Exam objectives V4, document version 5.0). Not affiliated with or endorsed by CompTIA. Contains no exam questions.