OCI image¶
An OCI image is a standardized specification for a containerized artifact, designed to ensure interoperability across different container runtimes and tools.^[400-devops-03-containerization-kpack.md]
The format serves as the foundational building block for containerization technologies, allowing applications and their dependencies to be packaged into portable, self-contained units.^[400-devops__03-Containerization__kpack.md]
Key Characteristics¶
- Standardization: The OCI (Open Container Initiative) image format provides a vendor-neutral standard, distinct from proprietary formats, facilitating broad ecosystem support.^[400-devops-03-containerization-kpack.md]
- Portability: Because the format adheres to open standards, OCI images can run on any compliant platform or [[Container runtime]], supporting hybrid and multi-cloud environments.
- Structure: Typically composed of a manifest, file system layers, and configuration data, the image defines exactly what is required to execute a specific application.
Use Cases¶
- Build Tools: Tools like kpack are designed to automate the creation of OCI images directly on Kubernetes clusters, streamlining the path from source code to deployment^[400-devops__03-Containerization__kpack.md].
- Deployment: OCI images are the standard unit of deployment in modern cloud-native architectures.
Related Concepts¶
- Kubernetes
- [[Containerization]]
- [[Docker]]
Sources¶
400-devops-03-containerization-kpack.md400-devops__03-Containerization__kpack.md