Which implementation is the canonical reference for the OCI runtime specification?

Which implementation is the canonical reference for the OCI runtime specification?

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

Answer: (D)

The main idea here is knowing which implementation serves as the official baseline for the OCI runtime spec. runc is the canonical reference because it was created as the official implementation that directly demonstrates how the OCI runtime interface should behave. It embodies the spec in its simplest, standards-compliant form and is used as the baseline for conformance tests and for validating other runtimes. Other options exist to work with OCI standards but aren’t the official baseline: containerd is a higher-level daemon that can drive containers using a runtime like runc; crun is an alternative runtime that aims for performance and space efficiency while staying OCI-compliant; runv was an experimental project exploring virtualization-based container isolation. None of these serve as the official reference the OCI maintains.

The main idea here is knowing which implementation serves as the official baseline for the OCI runtime spec. runc is the canonical reference because it was created as the official implementation that directly demonstrates how the OCI runtime interface should behave. It embodies the spec in its simplest, standards-compliant form and is used as the baseline for conformance tests and for validating other runtimes.

Other options exist to work with OCI standards but aren’t the official baseline: containerd is a higher-level daemon that can drive containers using a runtime like runc; crun is an alternative runtime that aims for performance and space efficiency while staying OCI-compliant; runv was an experimental project exploring virtualization-based container isolation. None of these serve as the official reference the OCI maintains.