Pregunta de Containerization #019e3a4f

The Open Container Initiative (OCI) defines standards for container formats and runtimes. The native OCI-compliant runtime is runC, a lightweight, portable container runtime that directly implements the OCI runtime specification. It is the default runtime used by Docker and other container engines.

How it Works

runC creates and runs containers by leveraging Linux kernel features such as namespaces and cgroups. It reads an OCI bundle (a filesystem root and a config.json file) and launches the container process with the specified isolation and resource constraints.

Why runC is Correct

runC is the reference implementation of the OCI runtime specification. It is maintained by the OCI community and is designed to be minimal and secure, providing the core functionality for running containers according to OCI standards.

Why Other Options are Incorrect

• runV is a hypervisor-based container runtime that uses a virtual machine for isolation, not a native OCI runtime. It is not OCI-compliant by default.
• kata-containers is also a hypervisor-based runtime that provides VM-level isolation. While it can be integrated with OCI-compliant tools, it is not itself a native OCI runtime.
• gvisor is a user-space kernel that provides a sandboxed environment for containers. It implements a portion of the Linux syscall interface but is not a native OCI runtime; it is an alternative runtime that can be used with OCI-compliant container engines.