OCI: Openness standardizes better
Vincent Batts @vbatts
$> finger $(whoami)
Login: vbatts Name: Vincent Batts
Directory: /home/vbatts Shell: /bin/bash
Such mail.
Plan:
OHMAN
$> id -Gn
devel opencontainers docker appc redhat golang slackwareContainers
(Cite: the internet)
WHEN
WHY
WHo
WHat
WHEN
2013
- Docker launches 🐋
- A number of folks jump in to help
⏰time passes ⏰
- phenomenal amounts of contributions
- loads of integrations with tooling
- post 1.0 changes. EOL of formats. short windows for supporting tooling
WHEN
December 2014
CoreOS launches Appc spec (and rkt 🚀) to rally conformity
June 2015
Docker launches OpenContainerInitiative Specs and donates libcontainer/runc
WHEN
🌼Spring 🌼 2016
opencontainers/specs was split into
runtime-spec and image-spec
Today
Both OCI Runtime and Image are 🙌 v1.0.0-rc5 🙌
WHEN
(cite: the internet)
(cite: the internet)
WHY
(Cite: the internet)
WHY
open
mediated
represented
transparent
WHY
(Cite: the internet)
WHO
So many MAINTAINERS
And a great community
Helping others?
Looking out for each other?
Cross pollinating?
exaggerated stress?
burnout?
Reducing politics
keep passive-aggressiveness in check
Absolutely, and it takes everyone of us to recognize that others want stress-free happiness, just like you.
This is not
"winner takes all [the happiness]"
(cite: the internet)
what
Runtime Specifications
- Opencontainer Runtime-spec (github.com/opencontainers/runtime-spec)
- Started June 2015
- Presently at v1.0.0-rc5
- `runc` is the flagship. Other implementations like runv and oci-runtime-tools
WHAT
Distribute Image Specifications
- Opencontainer image-spec (github.com/opencontainers/image-spec)
- Started April 2016
- Originated from Docker-1.10 and Registry v2 format
- Presently at v1.0.0-rc5
- Support from Amazon ElasticContainerRegistry (ECR), rkt, flatpak, skopeo, cri-o, containerd and more
- pull-requests opened for docker (moby/moby) and docker-registry
!WHAT
Not included:
- Networking
- see CNI
- tools like jessfraz/netns)
- Distribution
- there is a PR for docker-registry
- some are using the image-layout
- Whole service composition (see also pods, deployment configs, compose, etc)
Now
(Cite: the internet)