Docker has become the dominant containerization platform in enterprise IT. Whether you are new to containers or a seasoned DevOps engineer, it pays to have a solid mental model of how Docker’s individual components fit together. The questions and explanations below walk through the key building blocks of the Docker ecosystem.
This article is based on a quiz originally published on TechTarget. The quiz format has been replaced with a question-and-explanation guide that is more useful for self-study and reference.
What Operating Systems Does Docker Support?
Answer: Linux, Windows, and macOS — all of the above.
Docker Engine runs natively on Linux. On Windows and macOS, Docker Desktop provides an integrated environment that runs a lightweight Linux virtual machine under the hood. Since Docker’s kernel-level features (namespaces, cgroups) are Linux primitives, Windows and macOS hosts rely on this VM layer. Docker also has native Windows container support on Windows Server for running Windows-based container images.
What Does containerd Manage?
Answer: The container lifecycle on its Linux or Windows host system.
containerd is an industry-standard core container runtime. It is responsible for the full lifecycle of a container on the host: image transfer and storage, container execution and supervision, low-level storage, and network attachments. Docker Engine uses containerd as a core dependency, but containerd is also used independently by Kubernetes and other container orchestration systems. It was donated to the Cloud Native Computing Foundation (CNCF) to ensure vendor-neutral governance.
What Does Docker Swarm Mode Do?
Answer: All of the above — it clusters container nodes, integrates orchestration capabilities, and exists natively within Docker Engine.
Docker Swarm mode is Docker’s built-in clustering and orchestration feature. When you initialise a swarm, Docker Engine nodes are grouped into manager and worker nodes. Managers handle scheduling and cluster state; workers execute containers. Swarm mode provides service definitions, rolling updates, load balancing across nodes, and secret management — without requiring a separate orchestration tool. Because it is built into the Docker Engine binary, no additional installation is needed.
What Can You Do With Docker Compose and Swarm Mode Together?
Answer: Construct and define multi-container applications.
Docker Compose uses a YAML file (docker-compose.yml) to define multi-container applications — specifying services, networks, and volumes in a single declarative file. When combined with Swarm mode via docker stack deploy, the same Compose file can be used to deploy and manage a multi-container application across a cluster of Docker nodes. This makes Compose a natural bridge between local development and production-grade orchestration.
version: "3.8"
services:
web:
image: nginx:alpine
ports:
- "80:80"
api:
image: myapp:latest
depends_on:
- db
db:
image: postgres:15
environment:
POSTGRES_PASSWORD: exampleCode language: CSS (css)What Is Docker Hub?
Answer: A centralized repository of container images.
Docker Hub is Docker’s hosted image registry. It provides a large library of official and community-contributed container images that developers can pull and use as base images. Docker Hub supports both public (free) and private repositories. It also offers automated builds linked to source code repositories, image scanning for known vulnerabilities, and webhooks to trigger downstream workflows. Teams can use Docker Hub as a central distribution point for their own application images.
Where Does Docker Datacenter Store Container Registries?
Answer: On-premises.
Docker Datacenter (now represented by Docker Enterprise / Mirantis Kubernetes Engine after Docker’s enterprise business was acquired by Mirantis) was designed to give organisations a self-hosted, on-premises container management platform. Its integrated registry, Docker Trusted Registry (DTR), stores container images on-premises, giving enterprises full control over image storage, access control, and compliance requirements — without relying on an external cloud registry.
Which Feature Is NOT Part of Docker Cloud?
Answer: Automated legacy application code conversion into microservices.
Docker Cloud (which has since been discontinued as a standalone service, with features folded into Docker Hub) provided build and testing pipelines for Dockerized images, tools to manage cloud host infrastructure, and swarm provisioning across cloud providers. It did not offer any automated conversion of legacy monolithic applications into microservices — that architectural transformation requires deliberate design decisions by engineering teams.
What Is a Dockerfile?
Answer: A text file that describes how to build a Docker image.
A Dockerfile is a plain-text script containing a series of instructions that Docker Engine executes in sequence to assemble an image. Common instructions include FROM (base image), RUN (execute a command), COPY (add files), EXPOSE (document ports), and CMD or ENTRYPOINT (define the default process). The resulting image is immutable and can be versioned, shared via a registry, and used to start containers consistently across environments.
FROM python:3.12-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY . .
EXPOSE 8000
CMD ["python", "main.py"]Code language: JavaScript (javascript)How Does Docker Machine Manage Virtual Hosts?
Answer: Via the command line.
Docker Machine was a CLI tool (docker-machine) used to provision and manage virtual machines running Docker Engine — on local hypervisors such as VirtualBox or on cloud providers. It allowed engineers to create, inspect, start, stop, and upgrade Docker hosts from a single command-line interface. Docker Machine has since been deprecated; its functionality has been largely superseded by Docker Desktop for local development and cloud-native VM provisioning tools (Terraform, cloud CLIs) for remote infrastructure.
Where Does Docker Notary Store Trusted Content Collections?
Answer: In Docker Hub repositories (and any compatible registry that supports Docker Content Trust).
Docker Notary is an implementation of The Update Framework (TUF) that enables publishers to sign container images and consumers to verify those signatures before pulling them. When Docker Content Trust (DCT) is enabled, signed image metadata is stored alongside the image in the registry — including Docker Hub. This protects against image tampering and ensures that only verified, trusted images are used in production deployments.
Summary: Docker Component Quick-Reference
| Component | Primary Role |
|---|---|
| Docker Engine | Core runtime that builds and runs containers |
| containerd | Low-level container lifecycle management on the host |
| Swarm Mode | Built-in clustering and service orchestration |
| Docker Compose | Declarative multi-container application definition |
| Dockerfile | Build instructions for creating a container image |
| Docker Hub | Hosted public/private image registry |
| Docker Trusted Registry | On-premises enterprise image registry |
| Docker Machine | CLI provisioning of Docker-enabled virtual hosts (deprecated) |
| Docker Notary / DCT | Image signing and verification for supply-chain security |
Understanding how these components interact is foundational for anyone working with containers in a professional environment. Docker’s ecosystem has continued to evolve — several components listed here (Docker Machine, Docker Cloud, Docker Datacenter) have been deprecated or rebranded — so always refer to the official Docker documentation for the current state of the platform.