Which container engine is used by Docker according to the material?

Which container engine is used by Docker according to the material?

• A. runc
• B. containerd
• C. LXC
• D. systemd-nspawn

Answer: (B)

Docker uses containerd as its container runtime engine. containerd sits as the daemon that coordinates container lifecycle, image management, storage, and other related tasks, providing a stable API for higher-level tools. The actual process creation and execution inside the container are handled by a lower-level runtime that containerd delegates to, typically runc. So containerd is the main engine referenced for Docker’s runtime stack, while runc is the underlying component that does the execution work. The other options, such as LXC and systemd-nspawn, are separate container technologies not used by Docker in its standard runtime architecture.

Docker uses containerd as its container runtime engine. containerd sits as the daemon that coordinates container lifecycle, image management, storage, and other related tasks, providing a stable API for higher-level tools. The actual process creation and execution inside the container are handled by a lower-level runtime that containerd delegates to, typically runc. So containerd is the main engine referenced for Docker’s runtime stack, while runc is the underlying component that does the execution work. The other options, such as LXC and systemd-nspawn, are separate container technologies not used by Docker in its standard runtime architecture.