►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
And
off
we
go
thanks
for
joining
us.
Welcome
to
today's
live
cncf
live
webinar.
Let's
talk
about
Innovation
and
open
source
container,
developing
developer,
tooling
I'm,
Libby,
Schultz
and
I'll
be
moderating
today's
webinar
I'm
going
to
read
our
code
of
conduct
and
then
hand
over
to
Phil
sc's
principal
at
Amazon
web
services.
A
few
before
we
get
started
during
the
webinar
you're,
not
not
able
to
talk
as
an
attendee,
but
you
can
pop
all
your
questions
and
comments
into
the
chat
box
when
we'll
get
to
them
as
soon
as
we
can.
A
This
is
an
official
webinar
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
of
all
your
fellow
participants
and
presenters.
Please
also
note
that
the
recording
and
slides
will
be
posted
later
today
to
the
cncf
online
programs,
page
at
community.cncf.io,
under
online
programs
they're
also
available
via
your
registration
link.
You
use
to
join
us
today
and
we'll
be
on
our
online
programs.
B
B
You
know
people
were
building
for
a
Linux
platform
and
so
the
the
concepts
that
that
make
up
containers
again,
if
we
ignore
windows
for
a
minute
are
all
all
about
Linux
Technologies,
like
namespaces
and
c
groups,
and
these
were
pieces
of
the
of
the
Linux
kernel
and
I
just
saw
Chris
disappear,
which
means
our
slides
have
disappeared.
So,
hopefully,
he'll
come
back
in
a
minute.
Yeah.
B
So
I
assume
we
get
those
slides
back
into
second
yeah.
So
if
we
go
into
the
next
slide,
you
know
we've
been
building
containers
for
Linux,
and
it's
not
just
that
these
kernel
features
are
critical
to
you
know
the
even
the
concept
of
what
a
container
is
this
process:
that's
isolated
in
very
specific
ways,
but
there's
other
Technologies
we've
added
to
that
around
security
like
SC,
Linux
or
app
armor
or
setcom
profiles.
B
How
images
are
even
constructed
this
idea
of
layers
and
these
these
file
system
constructs
of
Copier
on
on
right
file
systems
and
the
Linux
capability
system.
These
are
all
very
integrated
into
our
concept
of
what
containers
are,
and
so
we're
used
to
building
and
operating
containers
in
the
context
of
Linux
next
slide.
B
But
you
know
the
interesting
question
is
what
what's
that
system
that
you
sit
in
front
of
every
day?
Is
it
Linux
or
is
it
a
Windows
machine?
It's
many
times
dependent
on
your
employer,
and
you
know
the
the
machine
that
they
have
is
a
common
bill
that
developers
get
in
your
company
or
a
preference
that
you
have
for
you
know
having
a
Macbook
like
many
people.
Do
these
days
next
slide.
B
If
you
try
and
look
for
data,
it's
it's
pretty
tricky.
So
I,
you
know
distilled
a
lot
of
my
rabbit,
trailing
down
to
some
some
averages:
Mac,
OS
and
windows.
You
know
again,
you
can
quibble
about
specific
percentages,
but
potentially
up
to
80
percent
of
developers
aren't
using
Linux
at
work,
and
so
when
we
marry
these
two
things,
we've
discussed.
B
So
you
know
we
are
now
we're
struck
with
this
problem.
I
want
to
work
with
Linux
containers,
but
I'm,
not
on
Linux
and
a
very
easy
solution
that
many
people,
including
myself,
used
for
for
years,
was
well
I.
Can
you
know
just
have
Linux
in
a
VM
somewhere
I
can
I
can
use
it
in
the
cloud
I
can
run.
You
know
a
software
like
parallels
on
my
MacBook
or
on
my
Windows
system
or
I
can
use
VMware
and,
and
yes,
I
mean
this.
This
is
definitely
a
possibility.
B
Now,
I'm
running
you
know,
whatever
that
container
software
is
the
docker
engine
or
container
D
or
Creo
on
a
Linux
system
and
I
interact
with
it.
By
having
this
VM-
and
you
know,
maybe
there's
some
complexity
around
now,
I
have
to
ssh
in
or
I
have
to
share
file
systems
across
this
boundary
and
it
it
becomes
a
little
less
easy
to
do
my
work
next
slide
and,
of
course
you
know
once
we've
added
this
solution
so
to
speak.
B
We've
brought
new
problems
to
ourselves
because
we
we
now
don't
only
have
our
laptop
or
our
our
workstation
and
all
the
management
that's
either
required
by
my
employer
or
the
fact
that
I'm
just
trying
to
keep
it
up
to
date.
But
now
I
have
another
OS
image
that
has
its
own
cves
and
flow
of
updates
and
I
have
to
you
know.
If
I
get
my
system
replaced,
you
know
I
either
have
to
preserve
my
VM
image
or
configure
it
back.
B
The
way
I
wanted
it,
and
then
I've
already
mentioned,
there's
the
whole
issue
around
VM
boundaries.
You
know,
I
I
have
a
IDE
on
my
Windows
or
Mac
system,
but
I
want
to
share
those
files,
I'm
editing
into
the
VM,
so
I
can
build
it.
You
know
in
my
Docker
file
into
a
container
and
then
networking
and
all
kinds
of
other
complexities
of
having
essentially
two
systems
yeah.
So
the
all
this
boils
down
to
I
I
potentially
inhibit.
B
B
B
Don't
worry
about
the
where
there's
a
VM
and
who's
managing
what's
inside
the
VM
and
how
the
pass-through
magic
happens,
it
also
it
gives
them
a
chance
to
bundle
relevant
or
related
tooling,
so
Cube
CTL
and
a
local
kubernetes
cluster
and
Docker
compose
and
all
the
other
pieces
that
may
be
valuable
to
your
workflow.
Are
there
within
this
collection
of
projects
that
manage
this
on
your
behalf?
B
Next
slide,
so
that's
great,
you
know
again,
if
you're,
if
the
docker
ecosystem
is,
is
where
you
work
and
operate.
Meanwhile,
you
know
across
the
last
seven
eight
nine
years
additional
ideas
around
how
we
assemble
container
run
times,
what
they
look
like,
what
they
contain
I'm
a
maintainer
of
the
cncf
containerd
project.
B
So
you
know
again,
as
I
said,
as
a
maintainer
of
container
D,
that's
where
I
spend
most
of
my
time.
It's
now
a
graduated
project
with
a
mature
user
base
and
there's
a
lot
of
sub
projects
around
it.
It's
not
just
the
one
runtime
there's
custom
file
system
support,
there's
an
image
encryption
project.
B
There
are
people
who
now
you
know,
want
to
integrate
container
D
with
pieces
and
and
software
platforms
built
around
rust,
and
so
there's
rust
crates
to
tie
into
container
D,
either
as
a
runtime
or
via
the
grpc
API
other
C
group
projects,
and
then
one
that
I
really
want
to
highlight.
That's
going
to
play
into
the
our
discussion
today
is
nerd.
B
Now,
additionally,
it's
important
at
this
point
to
mention
build
kit,
because
containerd
also
wasn't
created
with
the
idea
of
encapsulating
the
whole
concept
of
assembling
a
container
again,
the
traditional
way
being
using
a
Docker
file
running
it
through
Docker
build
and
getting
a
container
that
you
can
push
to
a
registry
and
so
build
kit
is
that
project
that
came
out
of
docker
as
its
own
open
source
project
has
expanded
its
capabilities.
It
can
build
around
run.
C
it
can
build
on
container
d
and
so
together.
B
So
we're
kind
of
back
to
where
we
started
in
that.
Well,
that's
great
container
D
is
a
Linux
project.
Buildkit
is
a
Linux
project,
but
what's
the
solution
when
I'm
back
on
my
Mac
or
potentially
on
Windows
and
I,
still
want
to
use
these
projects
to
build
and
run
containers
in
my
local
development
environment,
so
I've
already
mentioned,
nerd
CTL
provides
that
Docker
compatible
command
line.
It
also
has
compose
support.
B
His
own
use
case
was
I,
have
container
D
I
want
to
put
it
inside
a
VM
and
on
my
Mac
just
get
this
simple
pass
through
both
for
file
sharing
and
handling
the
commands
of
the
flags
all
passing
through
to
nerd,
CTL
and
container
D,
and
build
kit
inside
the
VM.
Now
you
can
use
Lima
for
a
lot
of
other
use
cases.
But
again
his
personal
use
case
was
around
this
idea
of
similar
to
Docker
machine
or
Docker
desktop,
providing
the
same
pass-through
experience.
B
The
cool
thing
is
that,
because
containerdy
as
I
mentioned,
has
other
sub
projects,
Lima
plus
nerd,
CTL
plus
container
d,
has
allowed
that
specific
set
of
components
to
expose
other
experimental
features
that
are
part
of
container-d
the
the
engine,
the
runtime,
so
lazy.
Loading
snapshotters
is
a
big
area
of
investment
and
Innovation,
as
well
as
some
of
the
other
projects
like
image
encryption
that
I
mentioned,
you
also
get
out
of
the
box.
B
If
you
use
Lima,
plus
nerd
CTO
and
container
D,
you
get
rootless,
unprivileged
mode,
and
if
anyone
has
worked
with
ruthless
unprivileged
container
run
times,
it
can
get
a
bit
complex
to
set
that
up
yourself.
You
have
to
have
some
other
scripts
that
handle
the
rootless,
networking
and
other
pieces,
and
so
Lima
packages.
This
for
you
by
default
and
gives
it
to
you
out
of
the
box
and
so
there's
two
other
popular
projects
that
are
built
on
the
same
stack.
One
is
Colima.
B
B
So
that
brings
me
to
another
open
source
project
that
was
just
founded
and
launched
last
November,
and
so
we
have
a
team
here
at
AWS
who
were
who
contribute
to
container
D,
because
we
use
containerdy
heavily
in
our
cloud
services
at
AWS
and
looking
for
solutions
for
the
same
same
problem,
we
started
talking
about
right
from
the
beginning.
You
know
thousands
of
developers
using
MacBooks.
B
B
But
we
are
planning
and
would
love
community
help
to
also
look
at
adding
windows
and
Linux
support,
so
that's
kind
of
the
the
core
of
what
we
launched
late
last
year.
We
continued
to
develop
it
in
the
open.
It's
an
open
source
project
with
a
team
here,
AWS
working
on
it
full
time
and
we're
even
looking
and
hoping
for
external
contributors
who
even
want
to
become
maintainers
of
the
project.
B
So
yeah
at
this
point,
I
was
going
to
show
off
some
commands
now
if
you've
used
Docker
at
all,
maybe
you'd
say
well,
it's
not
all
that
exciting,
because
you're
just
typing
the
same
commands
but
putting
Finch
where
you
would
put
Docker.
So
you
know
finish
images
to
see
the
list
of
images
or
you
know,
run
a
container
with
a
command
pull
a
new
image
from
a
registry
like
pulling
the
MySQL
latest
container
image
from
Docker
Hub.
So
you
know,
there's
there's
not
the
the
magic
is
not
that
you
you
get.
B
B
Yeah
Chris,
you
know
I
I'm,
trying
to
think
I
I
had
a
a
little
compose
file
that
I
was
going
to
show.
But
again
you
know
maybe
we'll
just
continue
and
then
if
people
have
questions
and
want
to
see
anything
specific,
you
can
hop
into
your
terminal
and
we
can.
We
can
try
some
things
out,
but
for
now,
let's
we
can
go
on
to
the
next
next
slide.
B
So,
as
I
mentioned,
Finch
is
not
is
not
a
replacement
for
any
of
these
projects.
We
we
created
it
because
we
were
already
working
Upstream
in
container
D,
as
we
started
to
think
about
assembling
a
tool
like
this.
We
made
some
contributions
to
Lima
we've
been
actively
working
in
nerd,
CTL
and
again,
you
know.
B
Build
kit
is
not
part
of
the
containerdy
project,
but
it's
a
very
key
project
that
is
important
to
the
build
subsystem
of
not
just
Finch
but
many
other
projects,
including
the
docker
engine,
now
uses
toolkit,
and
we
also
work
in
the
oci
specs
on
features
that
are
important
to
Future
capabilities
like
attaching
signatures
and
s-bombs
to
your
container
images,
and
so
when
we
think
about
collaborating
with
others
on
Finch.
It's
not
just
our
Finch
repo
that
we
care
about.
B
B
You
know
one
of
the
values
is
being
able
to
add
other
capabilities
without
having
to
change
the
underlying
project
itself,
so,
for
example,
allowing
Aqua
security
or
any
or
datadog
to
have
an
extension
to
plug
in
some
of
their
capabilities.
They
don't
want
to
add
that
directly
into
container
D
or
the
finch
project.
They
want
to
be
able
to
have
an
extension
that
works
for
Finch
or
for
podman
or
for
docker,
and
so
that's
another
key
feature
that
we
think
will
unlock
a
lot
of
extensibility
for
Finch.
B
The
GitHub
project
is
here
should
be
simple
to
find.
We
also
have
a
finch
channel
on
cncf
slack,
where
we've
had
some
good
Community
discussion
with
others,
but
it's
still
very
early
days
and
would
love
others
to
drop
in
there
and
give
us
feedback.
I.
Think
we
have
is
the
next
slide,
just
sort
of
a
wrap
up
with
some
links:
yeah,
okay,
so
there's
a
few
more
links
here
that
Chris
put
together
on
again
getting
to
the
finch
organization.
B
We
have
a
blog
post
that
explains
more
that
Chris
and
I
participated
in
writing
about
why
we
created
it.
That's
easy
to
find,
and
then
again
a
lot
of
this
is
based
around
our
existing
work
in
container
D,
not
just
myself,
but
we
have
a
container
runtime
team
here
at
AWS
that
works
Upstream
in
containerdy
in
some
of
the
sub
projects
and
I'm
easy
to
find
online
as
well.
If,
if
there
are
future
questions
or
are
interested
to
reach
out
on
any
of
these
topics,
so
I
will
stop
there.
B
Yeah
so
great
question
Gerardo,
hopefully
I
got
your
name
correctly,
so
you
know
they're.
There
are
well
I,
think
the
the
one
of
the
ways
to
to
start.
This
answer
is
to
recognize
that
you
know
people
have
favorite
Ides
or
you
know,
there's
the
classic
VI
versus
emacs,
which
maybe
is,
is
less
of
an
exciting
War
as
it
used
to
be.
When
we
have
fancy,
you
know
vs
code
and
cloud-based
Ides
these
days,
so
we
don't
see
Finch
as
a
as
necessarily.
B
You
should
pick
Finch,
because
you
know
item
bullet
points,
one
two
or
three.
There
are
people
for
whom
the
docker
ecosystem
is
perfectly
fitted
for
what
they
want
to
accomplish
for
us,
specifically,
you
know,
AWS
has
has
I'm
sure
many
know
a
fairly
massive
customer
base,
who
you
know,
pay
to
run
their
workloads
on
AWS
and
many
of
those
workloads
today
now
run
in
containers
and
if
they're
running
it
on
fargate
or
eks.
B
It's
probably
running
in
container
d
as
the
the
container
runtime
and
so
Finch
gives
us
that
ability
for
those
companies
who
also
have
a
significant.
You
know
developer
base,
who
all
have
laptops
and
are
you
know,
building
their
applications
and
containers.
Finch
gives
them
a
way
to
use
the
same
technology
that
AWS
is
using
when
they
run
their
workloads
in
production,
and
it
also
you
know,
potentially
for
some
of
those
customers.
B
They
would
like
to
make
sure
that
if
they
have
a
problem
talking
to
ECR
Public,
aws's
public
container
registry
or
their
ECR
private
registries,
they
know
that
if
AWS
are
experts
in
Finch,
because
we
collaborate
with
others
in
the
project,
then
we
can
help
them.
We
can
debug
their
issue
if
they're,
using
Docker
or
podman,
they
have
to
go,
seek
out
help
from
those
communities,
and
so
that's
kind
of
our
natural
bet
to
have
a
tool.
B
That's
built
using
a
lot
of
the
same
components,
but
it's
one
that
we
have
expertise
in
and
it
uses
the
same
container
run
time
that
we
use
in
production
and
have
expertise
in
and
so
debugging.
You
know
complex
problems
and
you
know
giving
developers
a
similar
stack
so
that
hopefully,
if
there's
some
Corner
case
issue,
they
can
even
see
a
locally
as
well
as
seeing
it
may
be
in
one
of
our
Production
Services.
B
B
For
the
same,
you
know
eight
or
nine
years
that
I
have
you
know
they've
created
a
set
of
tools
that
make
a
lot
of
sense,
because
they're
very
well
integrated
with
Rel
and
Fedora
and
openshift,
and
so
you
know
that
it
also
can
work
for
people
who
aren't
in
those
communities,
but
maybe
there's
a
more
natural
affinity
in
those
communities
because
again
there's
a
similarity.
Openshift
is
using
Creo,
which
is
the
same
core
libraries
that
podman
uses
as
well.
B
So
you
know,
that's
kind
of
this
I
think
my
answer:
around
affinity
for
the
communities
you're
in
you
also
mentioned
so
no
Docker,
Loops
or
binaries
will
be
used.
Yes,
that's
correct
in
the
sense
that
when
you
install
Finch
you're,
getting
a
Lima
VM
with
container
d
installed
inside
on
top
of
a
lightweight
Fedora
Linux
OS
image
with
build
kit,
the
only
reason
I'm
being
very
precise,
is
the
docker.
A
B
B
So
it
supports
both
architectures
and
a
cool
added
benefit
of
the
qmu
static
support
in
the
kernel
is
that
you
can
essentially
cross
build
to
either
architecture.
So
you
know
if
you
have
arm64
mac,
but
your
company,
you
know
targets
Intel,
based
CPUs
in
your
production
Cloud
scenarios,
then
you
can
build
Intel
based
64-bit
images
and
test
them
out.
You
can
run
them
locally,
but
obviously
then
they
would
run
naturally
in
a
Linux
Intel
environment.
In
the
cloud.