Questão de Container Orchestration #019e3a4f

The Open Container Initiative (OCI) is the project within the Cloud Native Computing Foundation (CNCF) responsible for developing specifications for industry standards around container formats and runtimes. The OCI maintains two key specifications: the Image Specification (defining the container image format) and the Runtime Specification (defining how to run a container filesystem bundle). These standards ensure interoperability across different container runtimes (e.g., runc, crun) and image builders (e.g., Buildah, Docker).

How it works: The OCI works through a collaborative governance model under the Linux Foundation. Its runtime specification defines the lifecycle of a container (create, start, stop, delete) and the configuration format (JSON-based config.json). The image specification defines the layers, manifest, and index formats. Compliance with OCI specifications allows any OCI-compliant runtime to run any OCI-compliant image, promoting portability.

Why the other options are incorrect:

• The Linux Foundation Certification Group (LFCG) is not a real entity; the Linux Foundation offers certifications like LFCS and LFCE, but does not have a group named LFCG that develops container standards.
• The Container Network Interface (CNI) is a specification and libraries for configuring network interfaces in Linux containers, focusing on networking, not container formats or runtimes.
• The Container Runtime Interface (CRI) is a plugin interface that enables kubelet to use a variety of container runtimes without needing to recompile, but it does not define container formats or runtime standards; it is a Kubernetes API.

Thus, only the Open Container Initiative (OCI) develops the specifications for container formats and runtimes within CNCF.