►
From YouTube: Containers 101
Description
In this lightboard talk, Massimo Re Ferre provides a high-level introduction to containers.
A
Hi,
my
name
is
Massimo
de
ferran
I'm,
a
technical
project
manager
with
the
cognitive
application
business
unit
at
VMware.
Well,
I
would
like
to
talk
about
in
the
next
few
minutes.
In
this
short
presentation
is
a
very
high-level
introduction
to
containers
and
the
title
of
this
session
is
in
fact,
container
101,
so
very
basic
information
about
containers.
A
Before
we
start
it's
funny
to
mention
that
containers
per
se
do
not
exist
right.
If
you
think
about
Linux,
there
isn't
really
a
container
first-class
citizen
object
inside
the
operating
system.
Whenever
we
talk
and
refer
to
the
word
containers,
what
we
basically
mean
is
a
collection
of
operating
system
technologies,
but
like
C
groups
and
namespaces
and
leader
Phi
system,
that
collectively
allows
you
to
implement
you
being
the
end
user.
A
This
concept
of
the
container
right,
so
what
a
container
is,
is
basically
an
aggregation
of
these
different
technologies
that
exist
in
the
operating
system
that
allows
you
to
run
an
application,
usually
a
single
process
inside
a
an
operating
system
right.
So
if
we,
if
we
take
an
operating
system
like
Linux,
for
example,
then
Windows
has
been
introducing
containers.
More
recently,
containers
leaves
inside
these
operating
system
as
object.
A
They
are
defined
by
those
technologies
that
I
refer
to
well
I'm,
not
going
to
discuss
in
this
brief
presentation
is
the
is
the
leg-up
model
of
that
operating
system.
So
everything
that
you
will
see
here
is
a
stirry
for
both
operating
systems,
running
on
bare
metal
directly
on
the
hardware
or
on
top
of
an
AI
provider.
Whether
you
run,
those
containers
in
an
operating
system
on
an
AI
provider
or
on
bare
metal
is
a
totally
orthogonal
discussion
that
we're
not
going
to
talk
in
this
presentation.
A
A
notion
of
containers
so
basically,
as
I
alluded
to
containers,
has
been
around
for
a
number
of
years,
but
only
in
the
last
three
four
years
we
have
seen
a
surge
in
the
adoption
of
these
concept
and
underlying
technology,
and
the
reason
for
that
is
because
a
continual
darker
came
out
and
the
technology
that
they
have
built.
It
was
very,
very
difficult
and
surely
not
for
the
masses
to
be
able
to
drown
containers,
particularly
at
scale,
in
a
very
efficient
way.
So
what
docker
did
is?
A
Basically,
they
introduced
a
technology,
a
software
technology
that
made
the
consumption
of
the
notion
of
containers
much
easier,
pretty
much
for
everyone,
so
docker
is
and
the
entire
container
ecosystem
is
exploding
in
terms
of
complexity,
but
whenever
I
do
a
101
talk
about
containers
and
docker,
I,
usually
start
from
the
beginning
and
the
atomic
and
the
atomic
functions
that
docker
introduced
in
May
containers
easy
easy
to
consume.
There
are
four,
in
my
opinion,
four
very
important
atomic
operations
that
make
doctors
so
widely
use.
They
are
the
build
that
push
the
pool
and
the
run.
A
These
are
the
four
critical
operations
that
you,
as
a
user,
can
be
on
a
docker
host
that
I'm
representing
here
to
manage
containers
all
right.
So,
let's
start
with
the
build
process,
so
the
build
process
is
really
very
much
the
process
that
takes
you
from
defining
what
that
container
is
included
in
terms
of
the
stack
that
the
container
is
going
to
represent
all
the
way
to
building
it,
what
we
refer
to
as
a
docker
image
right.
A
So
basically,
the
idea
is
that
you
start
with
the
so
called
docker
file,
which
is
basically
a
list
of
instruction
that
or
a
codified
version
of
what
you
would
do
to
basically
package
your
application,
so
think
about
being
able
to
say,
I
want
to
use
a
particular
OS
version.
That
is
usually
the
very
first
statement
inside
the
docker
file,
and
then
you
go
through
a
number
of
typically
shell
instructions
that
basically
add
all
the
dependencies
that
your
application
needs
and
your
application.
A
A
Once
you
have
a
docker
image
and
imagine
that
you're
running
on
your
personal
laptop
or
a
single
instance
of
an
operating
system
where
docker
is
running
doctor
being
a
set
of
binary
that
are
running
inside
this
operating
system,
what
you
can
do
at
that
point
is
basically
you
can
instantiate
that
docker
image
as
a
container
inside
this
operating
system.
So
basically,
this
is
what
the
run
command
allows
you
to
do.
A
A
The
other
thing
that
is
important
to
understand
here
and
again
I'm,
just
touching
some
of
the
concepts
at
the
very
high
level,
is
that
the
way
that
you
manage
the
container
at
this
point
is
not
like
you'd
manage
a
traditional
virtual
machine
right.
So
it's
additional
virtual
machine
has
a
you
know,
a
very
lean
networking
model
where
you
connect
these
these
entity
onto
a
network
and
it
will
get
an
IP
address
and
everything
is
working.
Fine.
A
Similarly,
for
storage,
virtual
machine
usually
has
persistent
storage
by
default,
so
you
can
move
them
around
and
you
can
perceive
the
data
that
are
in
those
built
role
in
those
virtual
machines.
We
container
this
is
very
different
right.
So,
for
example,
the
networking
model,
particularly
in
the
doctor
context,
is
such
that
these
container
has
an
internal
IP
address
that
only
exists
inside
this
operating
system
and
the
way
that
this
container
gets
to
the
outside
world
is
through
a
number
of
Naturals
that
exist
inside
this
docker
image,
so
either
from
going
out
or
going
in.
A
The
other
important
thing
to
remember
is
that
containers
are
ephemeral
by
definition
right.
So
when
you
deploy
a
container
that
container
has
storage
associated,
that
is
ephemeral.
So
if
you
save
a
file
inside
that
container
and
for
some
reason
you
destroyed
that
container
and
you
restart
another
container,
maybe
because
you
are
updating
your
application.
New
docker
image,
you're
going
to
lose
that
content
alright.
A
A
You
update
the
docker
file
to
point
to
the
new
application
on
you
rebuild
that
docker
image
so
that
you
have
a
new
version
of
the
image
that
represent
your
new
version
of
the
application
and
the
way
that
it
works
with
containers
is
that
you
do
not
update
the
containers
at
runtime.
The
way
that
you
manage,
containers
and
application
running
in
containers
is
that
you
destroy
this
container
and
you
recreate
a
new
container,
starting
from
the
new
version
of
the
of
the
docker
image
that
you
just
created.
A
So
that's
why
it
is
important
to
understand
very
well
the
relationship
between
the
persistency
of
the
container
and
the
known
persistency
part
of
the
container.
The
last
thing
that
I
want
to
mention-
and
these
pretty
much
covers,
like
the
basics
of
of
how
containers
work
on
top
of
an
ape
on
April
an
operating
system.
A
Concept
that
we
have
just
discussed,
we
have
seen
a
surge
in
the
last
few
years
of
container
orchestration
framework
right.
So
whatever
thing
that
we
have
discussed
here
is
very
very
much
a
basic
darker
concept,
but
as
it
gets
into
production,
as
you
get
a
scale,
you
will
start
to
see
and
hear
terms
like,
for
example,
swarm
or
kubernetes.
A
Which
are
basically
technology
that
are
used
to
manipulate
a
number
of
different
docker
host,
as
you
can
see
here
and
manipulate
some
of
the
complexity
and
networking
and
storage.
So
basically,
these
are
concept
that
a
lot
in
technologies
that
allows
you
to
treat
this
as
a
single
entity
and
basically
do
all
of
those
operations
in
an
automated
way.
Thanks
for
watching.