Which component serves as the reference implementation for the OCI runtime specification?

Which component serves as the reference implementation for the OCI runtime specification?

• A. runc
• B. containerd
• C. crun
• D. runv

Answer: (A)

The key thing being tested is identifying the official runtime that implements the OCI runtime specification. runc is the canonical reference implementation for this spec. It provides the low-level actions to create, start, stop, and delete a container process, wiring up namespaces, cgroups, and the container filesystem according to the OCI runtime spec. Because of this role, many tooling ecosystems (like containerd and other orchestrators) rely on runc to actually run containers, while runc itself serves as the baseline reference for how the spec should be implemented. Other options exist that are OCI-compatible runtimes (such as crun or runv), and containerd is a higher-level container manager that delegates to a runtime like runc. But the one designated as the reference implementation is runc.

The key thing being tested is identifying the official runtime that implements the OCI runtime specification. runc is the canonical reference implementation for this spec. It provides the low-level actions to create, start, stop, and delete a container process, wiring up namespaces, cgroups, and the container filesystem according to the OCI runtime spec. Because of this role, many tooling ecosystems (like containerd and other orchestrators) rely on runc to actually run containers, while runc itself serves as the baseline reference for how the spec should be implemented.

Other options exist that are OCI-compatible runtimes (such as crun or runv), and containerd is a higher-level container manager that delegates to a runtime like runc. But the one designated as the reference implementation is runc.