rkt and the Open Container Initiative: Promoting Industry Standards
summary
rkt is already pulling Docker images and converting them into ACI format and has OCI support since last summer but that support is a translation layer, not full compliance. Work in progress includes adding a runC stage1 so the runtime behavior matches the OCI runtime spec, and extending acbuild to produce either ACI or OCI images. Storage and fetching semantics differ (ACI uses a single-layer chain, Docker/OCI use layered graphs), so rkt must store and query two image models simultaneously.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:421972: IBM Introduces VM/370
- 5:34Docker Introduces Container Images
- 9:26How do we solve this?
- 11:30OCI: Setup and Structure
- 12:36The Runtime Spec
- 15:45The Image Spec - Fetching
- 17:00The Image Spec - Storing
- 18:07The Image Spec - Building
related talks
37mOpen Standards - Empowering Cloud-Native Innovation
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
46mCRI-O: All the Runtime Kubernetes need
28mCNI, CRI, and OCI - Oh My! [I]
29mCRI-O: All the Runtime Kubernetes Needs, and Nothing More
32mFive things you need to know about your container runtime
04mCRI-O: Container Runtime Intensifies
