►
From YouTube: Container Runtime and Image Format Standards - What it Means to be “OCI-Certified” [I] - Jeff Borek
Description
Container Runtime and Image Format Standards - What it Means to be “OCI-Certified” [I] - Jeff Borek, IBM & Stephen Walli, Microsoft
With the proliferation and rapid growth of container-based solutions over the past few years— including container-based solutions from almost all major IT vendors, cloud providers, and emerging start-ups—the industry needed a standard on which to support container image formats and runtimes while also ensuring interoperability and neutrality. The Open Container Initiative (OCI) was launched with the goal of developing common, minimal, open standards and specifications around container technology without the fear of lock-in. OCI has recently issued v1.0 of its container image format and runtime specifications, which enable a consistent and stable platform for running containerized applications.
The next phase in ensuring broad adoption of common container image format and runtime specifications is the OCI Certification program, which will be launching soon. This session will provide an overview and goals of the program, factors to consider if becoming OCI-certified makes sense for your container project, how to get your container project OCI-certified, and how you might be able to gain interoperability benefits from OCI-certified solutions. This session will also include a demo of the OCI Image validator being run against container images from container image registries from multiple vendors.
About Jeff Borek
Jeffrey Borek is a senior technology and communications executive with over twenty years of leadership and technical experience in the Software, Telecommunications, and Information Technology/Consulting industries. He is currently a WW Program Director for the Open Technologies and Developer Advocacy team - working with developers, business partners, leading industry analysts, and various open source community initiatives including; the Cloud Native Computing Foundation (CNCF) initiative, the Open Container Initiative (OCI), and the Open API Initiative (OAI) to ensure rapid response to changes in the open source ecosystem.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
All
right
well
good
morning
and
welcome
everyone.
I
hope,
you're
here
for
the
container
runtime
an
image
format,
standards,
update
I
want
to
start
by
just
welcoming
you
all
here
and
I'm,
going
to
turn
it
over
to
my
esteemed
colleague,
Stephen
Walley
and
who
I'm
in
awe
of
Stephens
a
sage
open
source
professional
been
doing
this
longer
than
me,
but
not
by
much.
B
I'm,
not
hot
I
told
you
I
could
break
anything
like
that
mic
up
now,
I'm
hot
there
you
go.
Thank
you
I'd,
better
step
in
before
Jeff
gets
too
carried
away
here.
My
name's
Steve
Wally
I
work
in
the
azure
engineering
team
and
I've
just
recently
gone
back
to
work
for
Microsoft
after
a
dozen
years
away,
just
to
kind
of
get
a
sense
of
folks
in
the
audience
to
folks
know
what
OCI
is
show
hands.
B
A
A
So
we
want
this
to
be
very
interactive,
I'm,
going
to
cover
the
kind
of
the
first
half
in
a
little
bit
of
the
background
and
Steven's
going
to
jump
in
on
the
organization
and
what's
going
on
with
certification
and
then
we're
going
to
have
time
for
Q&A
and
with
that,
how
many
have
heard
of
a
little
startup
called
docker
raise
your
hands.
That
ought
to
be
everybody
in
the
room
cuz.
It
was
really
interesting.
A
If
you
turn
the
clock
back
to
around
2014
in
the
spring,
I
was
at
an
openstack
conference
and
there
they
weren't
presenting
at
that
point,
but
the
buzz
in
the
room
was
all
about.
You
know:
hey
this
company
docker
and
have
you
seen
what
they've
done
with
container
technology
and
so
I
got
plugged
in
pretty
quickly.
But
the
point
I
want
to
make
on
this
first
slide
is
that
containers
have
been
around
for
a
while
and
I
don't
represent.
This
slide
is
exhaustively
complete
right.
A
So
if
I've
left
off
something
that's
a
favorite
of
yours,
I
want
to
apologize
right
out
of
the
gate,
but
you
can
see
that
you
know
freest
freebsd
started
with
the
concept
of
jails.
Early
on
you
had
linux
get
involved.
Sun
was
certainly
a
player
with
what
they
did
with
their
zones.
Technology
Google
started
leveraging
the
heck
out
of
containers
back
in
the
oh
six
time
frame
and
obviously
did
a
tremendous
amount
with
that
technology
to
be
able
to
scale
out
their
global
ad
platform.
A
Red
Hat
and
yours
truly
IBM
got
involved
with
container
technology
and
that
all
of
that
led
to
the
point
where,
if
you've
seen
Solomon
Cakes
talking
about
this,
you
know
he's
used
the
phrase
in
the
past
standing
on
the
shoulders
of
giants
right
because,
while
hats
off
to
what
docker
did
in
terms
of
enabling
to
make
containers
more
approachable
and
usable
by
the
typical
developer,
it
really
is
a
cumulative
effect.
That's
got
us
to
where
we
are
today.
A
So
when
I
met
the
docker
team
back
in
14,
it
was
still
early
days
and
yet
there
was
a
little
bit
of
confusion
in
the
ecosystem.
If
you
will,
because
you
had
this
very
viral
open
source
project,
around
containers
called
docker,
and
then
you
had
the
company
docker
as
well,
and
so
is
it
an
open
source
project?
Is
it
a
company?
A
A
single
open
container
specification
that
everyone
could
collaborate
on,
and
everyone
could
agree
that
would
help
create
some
of
the
foundation
of
this
technology,
and
you
can
see
the
concepts
around
not
being
bound
to
a
high-level
construct
not
tightly
associated
with
any
particular
commercial
vendor
or
project.
But
a
multi
vendor,
open
governance
structure
and
the
intent
for
this
was
to
help
enable
portability
across
multiple
platforms
that
principles
associated
with
getting
this
spun
up
when
we
worked
on
the
original
documentation
for
it,
content,
agnostic,
infrastructure,
agnostic
designed
for
automation
and
industrial
grade
delivery.
A
So
there
were
quite
a
few
companies
that
got
involved
early
on
and
one
of
the
big
players.
In
addition
to
docker
early
on
was
the
guys
at
core
OS
and
the
folks.
There
had
a
solid
team
that
was
working
on
this
collaboratively
and
they
also
had
a
vision
of
how
to
execute.
They
came
up
with
the
rocket
project.
A
This
has
been
picked
up
tremendously
beyond
the
initial
activities
by
docker
and
core
OS
maysa,
the
CN
CF,
with
kubernetes
cloud
foundry.
All
of
them
look
to
the
OCI
as
a
fundamental
in
of
the
basic
technology
and
in
in
terms
of
who's,
been
involved.
To
date,
the
contributors
hats
off
to
Red,
Hat,
no
pun
intended
they've,
been
a
major
participant
in
helping
to
develop
the
initiative.
A
A
Well,
where
we
gonna
go
when
this
becomes
firm,
how
are
we
going
to
try
and
create
some
sort
of
a
certification
process
around
this,
and
what
was
that
was
that,
like
a
year
and
a
half
ago,
time
flies
when
you're
having
fun
absolutely
so,
we've
got
a
high
level
representation
of
how
this
is
structured
and
Steven.
When
you
first
got
involved,
when
did
you
first?
When
did
the
OCI
first
hit
your
radar
so.
B
So
I
was
actually
at
peal
at
Packard
when
this
was
all
happening,
and
it
was
one
of
those
things
where
you
ended
up
in
a
situation
where
containers
and
containerized
workloads
were
gonna,
make
such
a
difference
compared
to
the
kind
of
infrastructure
arguments
that
folks
were
having
in
the
OpenStack
community.
That's
working
for
Hewlett,
Packard
I
thought
we
should
be
involved
in
the
the
frightening
thing
was.
It
was
all
based
on
a
single
company's
technology.
B
At
the
time,
docker
really
made
the
container
echo
system
usable,
and
so
you
know,
I
was
pushing
to
get
HP
involved
at
the
initial
bootstrap
and
Jeff
and
I
have
both
done
enough
standards
work
in
our
careers
that
sooner
or
later
it's
going
to
come
down
to
a
certification
debate.
That's
where
it
doesn't
matter
how
long
the
standard
takes
or
anything
else.
Sooner
or
later,
it's
going
to
become
a
certification
debate,
and
so,
as
I
stepped
out
of
HP
cloud,
I
ended
up
going
to
work
for
docker
for
a
year.
So
yeah,
that's
we've
overlapped.
A
The
in
fact,
how
many
you
have
heard
of
the
docker
governance,
vizor
II,
born
six
or
seven
one
of
the
best-kept
secrets
into
the
industry
all
kidding
aside
in
the
early
days,
docker
was
sort
of
conflicted
because
yeah
they
they
wanted
to
share.
They
obviously
put
that
out
an
open
source,
but
they
also
were
starting
to
think
you
know.
B
I
think
that
that's
a
really
important
point
here
what
the
thing
that's
been
different
about
the
open
container
initiative
from
a
lot
of
traditional
standards
organizations
is
it's
a
group
of
collaborative
open-source
engineers
and
they're
trying
to
build
a
specification
and
those
two
things
are
almost
the
antithesis
of
engineers
collaborating
with
engineered
standards.
You
know
you
kind
of
have
to
get
it
right.
The
this
idea
of
doing
things
on
Internet
time
is
based
on
a
foundation
of
a
group
of
engineers.
B
Thirty
years
ago
took
the
time
to
get
it
right,
so
we
can
be
moving
it
in
at
a
time.
At
the
same
time
when
you're
living
in
an
open-source
world
and
as
we've
watched,
these
projects
evolve
and
well
run.
Projects
are
on
this
cadence
of
releasing
regularly
and
frequently
that's
a
different
kind
of
engineering
collaboration.
So
open
container
initiatives
worked
really
hard
to
try
and
find
that
balance.
The
fact
that
they
kept
the
target
lean.
B
A
And
so
just
a
bit
on
how
the
OCI
is
organized,
there's
a
technical
developer,
community
and
there's
the
organizational
membership
and
we're
not
going
to
go
into
great
detail
on
the
org
structure.
But
we
can
get
into
that
a
bit
during
Q&A.
If
you
like,
the
important
part
is
that
we
really
wanted
to
a
have.
This
be
a
level
playing
field
right
right.
B
Jeff
and
I
are
not
those
engineers
Steve
and
day
in
the
front
row
is
one
of
those
engineers.
So
it's
you
know
it's
one
of
those
things
where
we
were
trying
to
keep
a
very
lightweight
organization.
That's
also
one
of
the
reasons
that
this
didn't
go
to
a
more
traditional
standards
organization.
Those
processes
can
be
very
heavyweight,
and
so
it's
trying
to
find
that
balance
of
creating
useful
specifications
and,
at
the
same
time,
letting
the
engineers
get
it
done
quickly
or
as
quickly
as
possible.
Yeah.
A
If
you're
an
engineer,
that's
worked
on
the
OCI,
raise
your
hand,
I've
got
Steve
Oh
up
in
front
there's
Michael
Brown
we've
got
looks
like
a
half
dozen
of
some
of
the
usual
suspects
here
in
the
room
with
us
again
hats
off
to
them.
It's
it's
taken
a
lot
of
hard
work
to
get
where
to
where
we've
gotten
to
at
this
point.
B
B
You
know
for
on
behalf
of
the
OCI
project,
so
this
is
one
of
those
things
where
you
can't
call
yourself.
Basically,
an
open
container.
Sorry,
a
OCI,
certified,
runtime
or
an
OC
is
certified
image
unless
you've
survived
the
certification
program.
This
this
is
the
point
of
this-
is
to
actually
provide
the
marketplace
information
about
where
we're
to
look
for
things
of
value.
B
That
said,
we're
also
in
this
place
that,
as
we
just
start
to
step
in
there
is
a
draft
of
a
process.
It's
a
process
that
you
would
imagine
it
kind
of
looks
the
way.
You'd
expect
a
process
to
look
like,
and
this,
if
anything,
was
the
easy
part
it's
coming
up
with
this,
because
you
know
really
we're
looking
at
a
process.
That's
normal
for
these
kinds
of
things.
You
start
off
with
the
application
you
basically,
this
is
this
is
who
I
am?
This
is
what
I
want
to
do.
B
I
want
I
want
this
trademark,
you
take
it
through
and
at
that
point
we've
sketched
in
kind
of
the
basic
information
that
we
think
we
want
to
have,
and
the
next
thing
you
do
is
you
test
it?
So
we're
gonna
go
through
and
test
the
products
against
these
two
things.
I'm
sorry
I'm
having
a
hard
time
because
I'm
just
getting
used
to
having
readers
for
the
first
time,
so
I
need
them
to
look
at
the
slides,
but
then
I
have
all
of
you
and
I
look
up
and
I
think
what
happened
to
the
audience.
B
You're
publishing
all
of
the
framework
around
that,
so
that
anybody
else
could
repeat
this
and
that
that's
the
intent
of
this
is
to
make
sure
that
this
is
a
highly
repeatable
system
and
that
can
be
checked
and
validated
by
anybody
else,
and
that's
kind
of
the
peer
review
is
to
finally
get
that
certification
you'd
somebody
within
the
rest
of
the
organization,
as
a
collection
of
peers,
will
validate
that.
Yes,
I
was
able
to
repeat
this,
and
at
that
part
you
know
you,
you
can
actually
claim
the
certification.
B
So
that's
the
easy
bit
so
to
speak.
That
framework
feels,
like
probably
everything
else,
you've
seen
in
many
different
guises,
and
you
know
on
the
back
end
of
that
is
this
whole
idea
that
you'd,
you
know,
then
want
to
promote
your
brands
that
you've
earned
to
the
marketplace.
Some
of
some
of
the,
where
the
debate
still
lies,
though,
is
there's
two
places.
One
of
them
is
the
test.
Harnesses
work
is
still
ongoing
on
the
test
harnesses
and
it's
there's
good
work
has
been
done
and
it's
evolving
right
now,
so
these
are.
B
When
you
look
at
it
from
an
application
perspective
is
if
you're,
the
vendor
you're,
probably
not
going
to
certify.
If
that's
a
promise
to
the
marketplace
that
you'll
obviously
run
on.
All
of
these
places
you
haven't
tested
because
that's
the
reality
of
being
an
ISV
you're,
not
gonna,
promise
your
customers,
regardless
of
what
the
the
the
platform
vendors
have
told
you
you're,
not
gonna,
promise
your
customers
that
it's
gonna
run
until
you've
tested
it
there
and
I
think
that
that
tension
needs
to
be
resolved
here.
B
B
That's
a
that's
a
great
piece
of
information
and
having
that
kind
of
toolset
come
out
of
the
certification
work,
so
that
you
know
that
you
have
a
valid
image
and
you
should
have
confidence
that
this
will
run
on
a
certified
platform
is
a
good
thing,
so
I'm
not
saying
that
that
tooling
doesn't
have
value
and
that
we
shouldn't
have
that
kind
of
validation.
I'm.
Just
saying
we
need
to
be
careful
as
you
step
into
the
nuances
of
a
brand
program,
about
exactly
how
you
what
promise
is
being
made
to
customers
on
the
end.
It.
A
Really
can
be
hard
to
strike
that
right
balance,
because
obviously,
if
the
collective
group
came
up
with
this
draconian
certification
process,
have
a
lot
of
overhead
have
a
lot
of
conflict
and
a
lot
of
stress
about
how
to
resolve
that
conflict.
On
the
other
hand,
if
it's
so
lightweight
and
it's
toothless,
then.
A
So,
there's
still
time
to
get
involved,
these
slides
going
to
be
available
up
on
the
Linux
Foundation
website,
so
I'll
post
them
up
just
shortly
after
we
finished
today,
but
there's
the
link
for
the
open
container
site,
as
well
as
for
the
developer
communities
and
with
that,
it's
time
to
start
to
transition
to
QA.
And
whilst
you
guys
are
thinking
of
your
first
original
question,
I'm
gonna
go
to
Steven
and
ask
him
what
was
the
biggest
surprise
that
he
thought
he
ran
into
you
over
the
last
15
16
months.
A
It
looks
like
we
have
a
question
over
there
and,
while
he's
getting
the
the
mic,
Mike
I
people
run
a
just
say
that
I
think
the
other
thing
that
we
tried
to
help
Shepherd
the
engineers,
along
with
on
this,
was
that
how
do
you
try
and
structure
this
in
such
a
way
that
you
don't
stifle
future
innovation
right?
I
mean
the
other
thing
about
this
o
CI
process.
That
was
of
a
concern
is
that
you
know
if
this
locks
it
down.
You
know
in
such
a
way
that
it
prevents
future
innovation.
C
All
you're
gonna
certify
the
runtime
processing
tools
that
container
runtimes
that
kind
of
stuff
and
format-
maybe
images,
but
it
was
more
of
the
format
right.
But
to
me,
the
image
format
should
barely
be
verified
at
the
tooling
area,
as
opposed
to
you
know
each
image
itself.
For
example,
you
know
a
build
tool
that
builds
these
images.
You
might
want
to
make
sure
that
it
does
build
OCI
images
correctly
right,
yep.
D
I'm
kind
of
been
following
the
standardization
process
at
one
remove
from
the
time
when
I
worked
at
core
OS
I
was
in
the
Pro
Services
Department,
so
I
wasn't
like
a
developer
or
anything.
I
have
not
read
through
the
spec,
but
I
was
wondering.
Does
the
spec
say
things
that
container
runtimes
or
images
must
not
do
or
if
it
doesn't,
is
that
something
that
you've
ever
considered
or
thought
about?
Are
there
things
that
we
should
say?
No,
you
should
never
do
this.
D
B
We
aren't
saying
anything
here,
and
so
it's
actually
very
helpful
when,
when
you
start
in
a
specifications
organization
that
you're
able
to
do
that,
the
marketplace
couldn't
have
allowed
it
in
that
situation,
because
there
was
just
when
you're
trying
to
bring
together
dozens
of
products
in
a
marketplace
worth
billions.
Sometimes
you
have
to
leave
things
unsaid,
whereas
in
this
situation,
because
this
is
still
a
relatively
new
space,
we
were
in
a
good
position
to
actually
build
up
and
and
make
the
claims
you
know.
Don't
do
this
other
questions.
A
E
I'm,
a
software
engineer,
DEP
Sarah
I
have
looked
at
the
runtime
expect
for
awhile,
and
it
only
includes
what
you
should
specify
it
to
run
your
image
like
CPU
and
other
stuff,
but
it
does
not
describe
anything
about
the
API
itself
like
how
the
runtime
should
expose
its
API.
And
do
you
have
anything
in
mind
for
including
API
also
or
is
just
gonna,
be
just
how
you
specify
the?
A
The
image
yeah
we
had
a
philosophy
of
kind
of
crawl
walk
run,
and
we
didn't
you
know
collectively.
Companies
that
were
involved
in
supporting
this
to
varying
degrees
were
worried
about
over
driving
our
headlights,
so
we
tried
intentionally
to
start
with
the
very
basics,
and
there
are
next
version
topics
that
I
think
are
getting
teed
up
and
that's
certainly
one
of
them
distribution.
The
other
things
right.
A
The
other
thing
that
we
really
are
also
trying
to
do
with
the
OCI
is
think
of
the
you
know,
if
you
think
of
the
Asian
yin-yang
symbol
of
black
and
white
and
synergy
we're
trying
to
keep
the
OCI
focused
on
the
fundamental
container
technology,
where
we're
not
trying
to
take
it.
You
know
across
the
line,
if
you
will
into
the
orchestration
in
space
we're
trying
to
be
very
complementary,
obviously
to
what
the
CNC
F
is
looking
to
do
with
container
orchestration
Stephen
yeah.
B
And
that
question
is
it's
frustrating
for
me,
because
that
would
have
made
certifications
so
much
easier
if
we
had
a
had
that
and
and
so
that
that
exact
question
has
been
an
active
debate
for
a
long
time,
but
at
the
end
of
the
day
there
was
also
the
we
we
were.
The
engineers
building
the
spec
were
in
a
position
that
they
could
actually
claim
victory
at
that
point,
and
that
was
a
good
thing
to
do
at
the
two-year
mark.
F
F
B
A
G
Top
the
topic
has
been
like
it
was
just
said
a
second
ago
up
for
debate,
since
even
before
OSI
I
was
a
thing
and
the
very
first
steps
were
the
the
image,
the
actual
image
format,
something
that
could
be
distributed
and
the
runtime.
So
now
that
the
v1
is
out
for
the
image
and
the
runtime
spec
and
a
light
sabbatical
for
all
the
people
that
were
involved
for
the
last
two
years,
everybody's
teeing
up
what
we're
gonna
be
working
on
for
2018.
There
is
an
OSI
I
face
to
face
tomorrow.
G
A
H
If
you
can
distribute
a
content,
addressable
blob,
you
can
distribute
an
OCI
image,
so
it's
it's
all
about
figuring
out
how
we
distribute
those
like
it
like.
Once
you
have
the
content
IDs,
you
can
distribute
it
over
any
medium
that
can
do
those
content,
IDs
and
figuring
out
how
to
do.
That
is
the
problem.
So
does
that
mean
we
should
have
an
distribution
spec,
probably
but
also
right
now,
it's
pretty
open
and
how
you
can
distribute
an
image,
because
once
you
get
to
that
ID
space,
you
can
be
really
creative.
B
B
Of
things
that
we
get
to
debate
in
this,
and
so
that
that's
why
I
like
the
work
is,
they
are
starting
to
ramp
up
again
for
what
the
effort
will
look
like
for
the
next
phase
of
specifications
in
2018.
So
if
you're
interested
in
your
company
has
a
perspective
or
you
want
to
share
your
expertise,
I
would
encourage
you
to
participate,
see.
A
A
B
That
was
really
it
is
I
would
encourage
you
to
come
and
participate
if
this
is
something
that
affects
the
way
you
want
to
start
thinking
about
things
at
scale.
It's
not
just
a
game
for
vendors.
There's
lots
of
bleeding
edge
users
out
there
that
have
real
experience
with
how
they're
doing
things
like
deployment
today,
and
so
your
opinions
are
valuable.
My
initial
step
into
the
standards
world
a
very
long
time
ago,
I
was
on
the
user
side
of
the
house.
B
I
was
working
for
EDS
in
a
General,
Motors
Factory
and
we
cared
about
the
standard
and
thought
we'd
go
find
out.
You
know
what
it
was
all
about,
and
that
was
a
very
fruitful
number
of
years
in
my
career,
so
from
even
just
a
understanding
how
specifications
happen
is
always
good
in
this
industry
and.
A
Thanks
for
that
seriously,
how
many
got
something
out
of,
or
enjoyed
today's
session,
just
a
quick
show
of
hands,
if
all
of
you
would
take
a
moment,
provide
that
feedback
to
the
Linx
foundation,
Stephen
and
I
would
greatly
appreciate
it
if
you
found
it
a
little
lackluster.
Well,
you've
got
better
things
to
do
with
your
time
than
to
respond
to
those
surveys.
So,
oh.