OCI BoF
summary
Status update on OCI certification research: a third party (Kinvolk) audits existing test suite repos and finds many failing runtime tests (seccomp crashes, delete/propagation mismatches) and CI limitations (Travis can’t run create+start). Runtime tests focus on runC but higher-level engines (containerd, Docker, CRI-O) need a proxy approach to be testable. Image work favors validation not certification, and the new distribution spec just landed — no firm rollout date yet. Decision: useful if you want gritty test failures and tooling gaps.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:25OCI certification updates
- 5:37OCI specs and tests
- 6:11Runtime monthly activity
- 6:29Image monthly activity
- 6:43Distribution monthly activity
- 7:25Testing OCI runtimes
- 9:21Testing runc
- 11:23Testing other implementations
- 15:32Scope of OCI runtime certification
- 25:46Updates in runtime-tools since March 2018
- 25:57Updates: TAP
- 26:29Updates: misc foxes & refactoring
- 27:34Updates: updated tests
- 28:11Scope of OCI Image certification
related talks
33mContainer Runtime and Image Format Standards - What it Means to be “OCI-Certified” [I]
35mPanel: The Open Container Initiative (OCI) and the Future of Container Standardization
06mLightning Talk - OCI: Container Standards and Certification
37mOpen Standards - Empowering Cloud-Native Innovation
18mExploration of Compliance Governance Based on Operating Systems
30mSuccess Stories in Open Source: Security Audits with OSTIF
46mSCA for Containers: The Good, the Bad, and the Truth
05mWelcome