What are Docker images and Docker containers?

Option B correctly defines the relationship: a Docker image is a lightweight, standalone, executable package (archive file) that contains all code, dependencies, and runtime needed to run an application. A Docker container is a running instance of that image—a live execution environment combining the OS, datafiles, libraries, and application. Options A and D reverse these definitions. Option C incorrectly describes containers as files rather than executable runtime instances.

Step-by-step Derivation:
Docker architecture follows this model: (1) A Docker image is a blueprint/template stored as layers in a file archive format. (2) A Docker container is created by instantiating/running that image, creating an isolated process environment. The relationship is analogous to a class (image) and its object instance (container). Option B is the only one that correctly assigns 'archive file' to images and 'units of OS/datafiles/applications' to containers.