►
From YouTube: Building Specialized Container-Based Systems with Moby: A Few Use Cases [I] - Patrick Chanezon
Description
Building Specialized Container-Based Systems with Moby: A Few Use Cases [I] - Patrick Chanezon, Docker
Moby is an open source project providing a "LEGO set" of dozens of components, the framework to assemble them into specialized container-based systems, and a place for all container enthusiasts to experiment and exchange ideas.
One of these assemblies is Docker CE, an open source product that lets you build, ship, and run containers.
This talk will explain how you can leverage the Moby project to assemble your own specialized container-based system, whether for IoT, cloud or bare metal scenarios.
We will cover Moby itself, the framework, and tooling around the project, as well as many of it’s components: LinuxKit, InfraKit, containerd, SwarmKit, Notary.
Then we will present a few use cases and demos of how different companies have leveraged Moby and some of the Moby components to create their own container-based systems.
About Patrick Chanezon
Patrick Chanezon is Chief Developer Advocate at Docker Inc. He helps to build Docker, the world’s leading software container platform, for developers and sysadmins.
Software developer and storyteller, he spent 10 years building platforms at Netscape & Sun, then 10 years evangelizing platforms at Google, VMware & Microsoft. His main professional interest is in building and kickstarting the network effect for these wondrous two-sided markets called Platforms.
He has worked on platforms for Portals, Ads, Commerce, Social, Web, Distributed Apps, and Cloud.
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
so
maybe
let's
get
started:
hi
everybody,
I'm,
Patrick,
Chan,
azam
from
darker
and
today
we're
going
to
talk
about
the
movie
project
and
we
are
lucky
because
many
of
us
from
docker
came
at
koukin
and
so
we'll
have
Stephen
day
who's
going
to
talk
about
container
G
and
Justin
Cormac
is
going
to
talk
about
Linux
get.
So
let's
talk.
Let's
talk
about
the
mobi
project,
so
darker
itself
is
a
it's
a
platform
that
sits
above
your
infrastructure,
any
type
of
infrastructure
and
then
runs
any
type
of
applications,
both
Linux
and
Windows.
A
It
runs
on
on-premise
in
different
cloud
providers,
so
it
provides
you
that
insulation
and
future-proofing,
allowing
you
to
add
new
type
of
infrastructure
and
have
that
same
layer
of
isolation
on
top
of
it
and
then
run
new
types
of
workloads
on
top
of
it,
as
as
the
way
we
were,
building
applications
evolves.
So
that's
what
docker
is.
If
we
look
in
the
details
of
it,
there
are
four
layers
in
there.
So
on
top
of
infrastructure,
you
have
the
core
container
runtime,
that's
called
container
G.
So
we're
going
to
talk
about
that.
A
That's
one
of
the
key
piece
of
the
mobi
project
and
actually
today
or
yesterday,
was
really
a
great
day
because
after
one
year
working
on
the
continuity
project,
we
announced
container
d1o.
Then,
on
top
of
that,
you
have
orchestration.
So
in
docker,
orchestration
is
done
with
a
component.
That's
called
swarm.
On
top
of
it,
you
have
a
darker
Community
Edition,
which
is
the
developer
tools.
A
The
tool
that
you're
using
to
do
docker,
build
docker,
push
to
build
your
images
and
run
them,
and
then,
on
top
of
it,
we're
building
a
darker
Enterprise
Edition,
which
is
a
full-blown
platforms
for
enterprises
to
be
able
to
run
containers
and
manage
them.
So
the
Enterprise
Edition
and
community
edition
ship
on
different
types
of
distros,
one
of
the
most
common
ones
that
people
are
using
the
Community
Edition.
You
can
find
it
on
Mac
and
Windows
on
your
laptop
for
development.
A
The
Enterprise
Edition
runs
on
any
type
of
infrastructure
that
enterprises
typically
use,
and
one
of
the
use
cases
that
we
see
enterprises
use
docker
for
most
commonly
is
to
modernize
traditional
applications.
So
initially,
when
containers
appeared
four
years
ago,
lots
of
people
were
using
docker
for
CI,
CD
or
micro
service
type
applications.
Nowadays,
all
the
rage
is
to
take
your
old
dotnet
or
java
application
that
are
running
in
VMs
or
on
bare
metal,
containerize
them
and
then
once
you've
containerized
them.
A
So
that
gives
you
the
best
enterprise
container
security
management
with
docker
Enterprise
Edition,
the
best
container
development
workflow
with
docker
Community
Edition,
a
choice
of
two
orchestrators,
and
it's
it's
the
the
native
kubernetes
bits
that
are
in
there.
So
that
means
that
all
the
kubernetes
ecosystem
of
different
projects
can
run
with
it.
And
then
this
is
backed
by
the
container
runtime.
That
is
a
continuity
which
is
now
100
engraven.
Until
so,
in
order
to
do
that,
we
we
followed
the
traditional
darker
innovation
model.
A
We
develop
all
our
components
upstream
in
the
mobi
project,
so
there
we
collaborate
with
9,000
other
open
source
contributors,
there's
eight
thousand
eight
hundred
PRS
per
year.
So
it's
a
very
active
set
of
projects
and
then
based
on
that,
we
use
that
as
the
upstream
for
darker
Community
Edition
targeted
at
developers
and
then
darker
Enterprise
Edition
targeted
at
enterprises.
A
So
the
mobi
project
has
lots
of
different
components
so
swamp.
It
is
for
orchestration
in
frack.
It
is
for
infrastructure
management.
Linux
ket
is
a
toolkit
that
allows
you
to
create
your
own
Linux
distributions
that
are
very
small
and
very
secure.
Container
D
is
the
container
runtime,
which
is
now
100,
and
it
implements
the
OCI
standards
for
image
format
as
well
as
runtime
run.
A
C
is
the
reference
implementation
for
our
CI,
so
it's
used
by
container
g
vp
n
ket
is
a
toolkit
that
used
to
to
do
the
network
management
on
docker
for
mac
registry
live
network.
There
are
tons
of
projects
in
there
so
today,
in
today's
session,
will
focus
on
three
of
them:
continued
ge,
Linux,
ket,
and
if
we
have
time
infrakit,
so
how
did
we
integrate
kubernetes
in
docker?
A
So
it's
a
CN
CF
project
in
April
at
Dhaka
con
we
showed
Linux,
ket
and
kubernetes
working
together
with
the
help
of
Ilya
from
weave
who's
sitting
there
Thank
You
Ilya
and
then
with
what,
with
Google
with
lantau
and
the
Google
team
on
a
CRI
continuity,
which
is
a
kubernetes
here
container
runtime
interface,
implementation
in
terms
of
containers
instead
of
dr.
D
Lib
network,
implemented,
studied
to
implement
C
and
I
in
September.
We
talked
about
that
at
the
open
source
summit.
A
A
So
continuity
and
notary
are
now
CN
CF
projects.
We
really
love
the
CN
CF.
There
are
a
whole
community
of
developers
who
participated
in
that
alia.
Your
picture
is
a
little
bit
small
there
and
then
what
we
are
really
excited
about
a
docker
is
what
will
happen
for
containers
in
terms
of
innovation
when
the
two
largest
open
source
projects
are
on
containers,
mobi
and
kubernetes
joined
forces
to
innovate
further
and
at
the
end
of
the
day,
we
are
one
big
community
trying
to
get
containers
to
be
more
mainstream.
One
of
the
changes
that
happen.
A
That's
pretty
important
that
Michael
Crosby
led
is.
We
had
a
B
DFL
closed
benefit,
benevolent
dictatorship
for
life
in
in
our
governance
for
mobile
projects,
and
the
biggie
FL
was
Solomon
hikes,
the
founder
of
docker,
and
what
BD
FL
means
is
that
when
there
are
technical
disagreements
between
maintainer,
they
can
escalate
that
to
the
BD
FL.
So
we
replaced
that
by
a
technical
steering
committee
that
has
been
elected
last
month,
I
think
so.
Let
us
talk
about
container
G
Linux
get
an
intricate
and
so
for
container
de
Stephen
who's.
B
B
Honestly
didn't
plan
it
to
be
released
with
Cube
Khan.
It
was
just
like,
like
that's
the
way
the
dates
worked
out
so
I
think
that's
it's
great
to
be
having
that
news
here.
So
it
shipped
yes
check
out
the
blog
link.
You
can
read
all
about
the
details.
I'm
not
gonna,
go
into
the
details
of
what
was
and
wasn't
in
the
in
the
1.0
I'll.
B
Just
talk
a
little
bit
about
the
project,
oh
yeah,
if
you're
taking
a
picture
yeah
there,
you
go
alright,
so
early
history
of
container,
D,
1.0
or
sorry
of
container
D
was
the
basics.
So
docker
had
this
thing
called
lib
container
and
that
was
spun
out
into
a
project
called
container
D.
Eventually,
there's
a
few
steps
in
there
that
I'm
gonna,
admit
and
that
was
released
in
docker
111
and
it
acted
as
a
management
or
like
a
supervisor
of
OC
I
run,
run
C
executors.
B
We
then,
over
time
we
decided
due
to
request
from
people
in
the
community
and
based
on
architecture.
We
decided
to
expand
that
the
container
deep
project
was
a
good
place
to
expand
some
of
the
core
functionality
of
docker
that
people
wanted
in
just
kind
of
a
simple
core
container
runtime
that
people
could
rely
on-
and
this
is
this
is
a
docker
with
minimal
features
and
that
it's
it
has
full
capability
of
the
entire
operating
system.
So
this
is
this
is
kind
of
the
timeline
December
2016
is
when
we
first
spun
it
out
of
docker
I.
B
Think
111
came
out
in
the
in
the
spring
of
that
year,
maybe
April
2017.
We
then
donated
it
matte
cloud
native
con
in
March
2017.
We
had
our
first
container
D
summit
in
April
of
this
year,
and
that
was
that
this
is
where
we
kind
of
collected
information
from
the
community,
and
we
brought
a
lot
of
people
together
and
said:
hey
what
do
you
want
if
we
could
turn
if
we
could
expand
the
scope
of
container
D
just
into
a
what's
needed,
as
this
like
single
host
container
runtime?
B
What
would
it
look
like,
and
so
we
took
a
lot
of
feedback
there
and
this
informed
what
became
container
d
1.0
in
November
2017.
We
released
our
first
kubernetes
1.8
integration
so
that
kubernetes,
you
could
try
out
the
betas
with
with
kubernetes
in
use
container
D
as
the
base
runtime
through
the
project,
CRI
container,
D
and
then
I.
Think
yesterday
was
yesterday
flights
extend
time.
You
know.
B
Yesterday
we
released
the
container
d
1.0
and
that's
now
generally
available
a
little
piece
of
trivia
if
you're
running
docker,
17:11
or
1712
RC
on
your
laptop
you're,
already
running
container
d
1.0,
so
you
may
be
running
it
and
not
even
know
so
again.
Why
did
we
do
this?
Why
do
we
do
all
this
work
and
why
the
big,
above
so
the
we
want
to
do,
expand
the
docker
platform
in
well.
B
We
wanted
to
extend
docker
into
a
platform
and
focus
on
develop
developer
experience,
and
we
found
the
goals
of
that
conflicting
with
the
goals
of
a
well
behaved
container
runtime,
and
this
affected
our
engineering
processes,
but
as
the
engineering
processes
of
our
of
our
like
partners
as
well.
So
we
wanted
something
that
could
be
used
beyond
docker
and
kind
of
fulfill
the
role
of
the
like
2014
view
of
docker,
as
this
like
single
host
container
runtime.
B
So
we
donated
it
to
the
CN
CF
and
history
was
made,
so
the
goals
of
the
project
were
to
have
a
very
small
lightweight,
G
RPC,
based
API
and
a
heaven
heavy
client
library
that
that
would
minimize
the
amount
of
abstractions.
So
we
didn't
want
you
to
have
to
plumb
a
single
flag
all
the
way
through
from
the
client
to
the
runtime.
We
wanted
to
make
that
stuff
available
directly
in
the
container
D
client,
making
it
a
lot
easier
to
add
new
features.
B
So,
if
you
upgrade
runs
see
you
don't
need
to
also
upgrade
container
D
to
get
access
to
new
features
and
run
C
the
other.
The
other
part
of
this
was
designing
for
stability
and
performance.
This
means
that
when
we
add
something
we
know
that
we
want
that
to
be
there
forever,
but
also
when
we
do
add
things
we
are
trying
to
design
so
that
they
can
be
stabilized.
And
so,
if
we're
unsure
about
things
we
hold
off
on
putting
them
in
and
and
this
will,
this
will
help
us
to
stabilize
over
time.
B
We
also
have
lots
of
things
that
can
help
us
to
do
this,
such
as
API
based
integration
tests
rather
than
CLI
based
integration
tests
like
aren
docker
and
it
as
well
as
we
take
the
entire
API
and
scan
all
of
our
protobuf
descriptor,
our
protobuf
files,
and
we
take
that
and
put
it
into
a
giant
API
stabilization
file.
So
this
will
help
us
identify
API
changes
over
time,
and
this
is
all
this
is
all
generated
and
automated
so
it'll
prevent
a
lot
of
the
problems
that
that
we
had
with
docker
and
the
other.
B
B
The
other
thing
about
container
D
that
that's
that's
huge,
is
we
focused
on
an
all
cart
design,
so
that,
like,
if
you
don't
want,
if
you
don't
like
the
way,
we
do
image,
storage
or,
if
you
don't
like
the
way,
we
do
push
and
pull
or
anything
you
don't
have
to
use
it
you
can.
You
can
only
use
the
parts
of
container
D
that
you
actually
want
to
use
and
you
cannot.
You
can
actually
disable
most
the
parts
of
container
D
that
you
don't
that
you
don't
need
to
use.
B
We
also
focused
on
using
like
known-good
technology
from
the
CNC
F,
so
as
well
as
the
Linux
Foundation,
so
like
Oh,
CI,
container,
runtime
and
images
we
use
G
RPC
heavily
and
as
well
as
something
a
project
called
prometheus
for
exporting
metrics.
So
and
those
are
great
scenes
diff
projects,
you
should
definitely
check
them
all
out.
B
B
Well,
your
you'll
be
able
to
use
a
container
d
and
in
on
kubernetes
we
also
have
an
experimental
swarm
kit
ex-employee,
it
might
not
compile
anymore
and
then,
but
the
the
other,
the
other
two
big
ones,
are
Linux
kit
and
build
kit.
A
Linux
kit
uses
container
d
to
actually
package
its
system
services
and
build
kit
uses
it
to
control
build,
and
this
is
one
thing
I
actually
highlight
about
container
D.
B
Is
that,
like
it's
meant
as
being
a
critical
piece
of
the
infrastructure,
whether
you're
on
your
dev
machine,
all
the
way
out
to
your
your
cloud
or
your
own
hardware,
so
that
when
you're
running
like
containers
in
container
D,
it's
a
like
there's?
No
there's
no
such
thing
as
like
Oh
works.
For
me,
it's
it's
in
you
use
it
for
the
build.
You
use
it
on
your
dev
machine,
you
use
it
in
production
o
in
the
future
potential
things
like
like.
There
is
an
open,
fast
integration.
B
If
you
I
don't
know,
there's
Alex
Alice
is
using.
It
has
a
talk
where
I
think
he's
integrated
with
CRI
container
D
he's
always
doing
really
cool
stuff.
So
I
don't
know
what
the
current
state
of
that
is
and
then
IBM
cloud
bluemix
will
use
CRA
a
container
d,
and
hopefully
you
will
be
too
you
can
you
know,
integrate
it.
Let
us
know
what
you're
doing.
Let
us
know
if
you're
having
problems
so
a
few
facts
and
figures
about
the
project
we
have.
B
Nineteen
hundred
and
ninety
four
github
stars,
401
Forks
hundred
and
eight
contributors,
I
think
it
was
roughly
87
the
container
d
1.0,
which
is
really
cool
to
see
and
there's
a
lot
of
different
people
contributing.
So
that's
a
I
was
looking
at
the
list
of
the
names
the
other
day
and
it's
really
really
cool
to
have
so
many
people
be
interested
in
this
project
such
that
they're
gonna
do
code
code
contributions.
We
also
have
eight
maintainer
x'
from
Independence
and
member
companies,
including
docker
IBM
ZTE
ZJ
use.
B
That
is,
that
right
as
well
as
33
3030
commits
and
at
28
releases
I
have
28
or
29
anyways.
So
this
is
a
lot
of
links
and
if
you
go
to
that
blog
I
think
we
get
most
of
these,
but
I'll
highlight
the
most
important
ones
that
you
might
be
interested
in
check
out.
The
getting
started
guide
the
getting
started
guide
is,
is
really
cool,
it'll
kind
of
show
you
the
like
what
you
know
what
is
container
to
you?
What
does
do?
What
does
it?
Not
do
that
kind
of
thing,
and
then
you
can.
B
You
can
look
through
the
the
scope
table.
The
road
map
I
see
where
we're
going.
If
there's
stuff
missing
on
there.
You
know
reach
out
to
us
through
an
issue
or
on
our
on
the
docker
community
slack,
and
you
should
be
able
to
kind
of
push
us
in
the
direction
that
you
want
and
we
can
help
you
with
a
proposal
or
or
anything
that
you
need.
B
You
can
also
read
a
little
bit
about
the
architecture
of
container
D
and
the
approach
to
how
we've
implemented
it,
and
that
can
help
you
to
understand
how
to
use
the
API
is
a
little
bit
better
and
then
you
can
learn
more
about
this
by
there's.
Actually
lots
of
talks,
there's
the
Linux
kit
and
kubernetes
talk
at
the
Austin
docker
meetup,
but
that's
already
happened.
Okay,
what
about
so
Phil's
talk
has
already
happened,
but
tomorrow
we
have
the
container
de
salón,
where
I
think
we
have
a
large
slot,
I.
B
Think
it's
70
minutes
or
something
like
that
and
we'll
go
we'll
go
into
details
on
architecture
as
well
as
we'll
show
you
a
little
bit
how
to
use
a
client
and
then
how
to
get
started
with
container
D
I.
Think
just
valiree's
o
has
created
a
great
getting
started
guides,
so
you
shouldn't
shouldn't
be
able
to
it
should
be
low
drama
anyways
now
I'm
going
to
pass
it
over
to
Justin
Cormac
for
a
presentation
and
demo
on
Linux
kit.
C
Okay,
so
I'm
going
to
talk
to
you
about
length,
skirts
and
a
bit
about
kubernetes
as
well,
because
we're
at
cube
con
and
we've
been
doing
a
lot
of
cool
stuff
with
given
it
is
so
kind
of
why
and
what
is
it?
So,
let's
get
the
sort
of
strap
line
is
a
toolkit
for
building
secure
portable
lean
operating
systems
for
containers.
So
it's
about
taking
it's
about
taking
a
kit
that
gives
you
the
ability
to
just
build
Linux
in
exactly
the
way
you
want.
C
We
give
you
a
load
of
pieces
that
help
you
build
Linux
in
the
way
we've
been
using
it
for
docker
users,
but
you
can
totally
replace
all
of
them
with
anything
else.
You
want
and
the
pieces
that
you
build
it
from
our
containers,
so
you
can
build
them
with
your
normal
workflows
for
building
containers
and
you
can
build
Linux
in
just
a
minute
or
so
it's
designed
to
be
built
in
a
CI
pipeline.
C
C
Security
is
designed
to
be
minimal
and
just
run
exactly
what
you
want
and
I
think
the
NIST
applet
container
Security
Guide
recommends
that
you
do
use
I
can
yes
a
custard
container,
specific
OS
for
running
containers
and
that's
one
of
the
important
Hughes
cases
for
learners.
Kids,
how's,
it
work.
It's
got
a
very,
very
simple
architecture.
It's
exactly
the
same
designers,
Kuban
essays
kind
of
coincidentally,
but
it's
also
kind
of
convenient
to
understand
so
there's
the
lifecycle
is
that
you
boosts
a
few.
C
You
start
a
few
containers
you're
on
boot
sequentially
and
which
we
run
through
run
see,
and
then
we
bring
up
container
D
and
run
all
the
services
you
want
at
that
point
in
parallel,
and
so
it's
it's
a
very
simple,
understandable
architecture
and
that
corresponds
to
a
yeah
mo
config
file.
So
you
can
see
here,
you've
got
on
boot,
oops
you've
got
DHCP
and
then
oops.
Then
this
is
running
a
Redis.
C
So
it's
a
really
simple
example:
I'll
show
you
that
in
practice
in
the
demo,
in
a
minute,
other
important
differences
is
that
it's
all
designer
and
immutability
there's
no
package
manager
or
anything
runtime.
You
can
you
just
build
it
and
replace
it.
If
you
want
to
do
dynamic
services,
you
can
run
docker
or
cube
initiatives
on
it,
so
it
makes
life
much
simpler
and
it's
easier,
and
that
gives
you
all
the
advantages
of
building
fast
and
running
fast.
C
We
have
a
very
container
like
build
push
and
run
workflow
with
support
for
pretty
much
every
kind
of
cloud
provider
or
disk
format.
You
can
build
ISOs
or
you
can
build
PhDs
and
we've
had
the
community.
Add
support
for
all
these
different
platforms
that
they
like
to
use
everything
from
OpenStack
to
VirtualBox,
to
KPM
and
so
on.
So
there's
a
really
wide
range
of
platforms.
You
can
run
it
on
and
this
really
simple,
tooling
or
you
can
use
the
native
provider
tooling.
C
So
you
can
just
build
an
ami
using
our
tooling
and
then
run
that
using
the
Amazon
tooling
or
whatever
you
want
to
do
so.
We
we
designed
the
tooling
around
giving
your
starting
point
and
then
for
production
applications.
You
can
obviously
use
more
advanced
tooling
how
it
fits
into
other
CN
CF
projects.
We
use
a
whole
range
of
things.
Obviously,
container
D
is
really
important
because
it's
actually
the
key
bit
that's
running
in
containers.
C
We
use
notary
and
tough
first
image
signing
to
sign
the
packages
we
build
kubernetes
and
see
and
I--we've
I'll
talk
about
in
a
second
and
geo.
Pc
and
Prometheus
are
used
in
container
D
and
you
can
use
that
to
get
system
stats
out
and
so
on
out
of
learners
kit,
just
very
cool,
so
Kay,
it's.
You
know
it's
very
much
a
cloud
native
way
of
doing
things.
It's
now
in
the
CNC
of
landscape
has
off
for
the
new
version
today.
C
Kubernetes
we've
actually
been
working
on.
Kidnet
support
actually
were
yeah
with
earlier,
as
Patrick
mentioned
for
seven
months
now
we
did
odessa's
demo
when
we
first
launched
nurse
kits,
and
it
was
the
first
time
we
showed
kubernetes
and
kind
of
at
Dokic
on,
and
it
was
apart
from
the
original
launch
of
cuban
esters,
which
was
a
docker
con
bit
and
we've
worked.
We've
worked
together
with
the
community
to
build
out
everything.
It's
now
got
its
own
repo.
It's
a
really
straightforward
standard,
understandable
version.
You
know
unmodified
version
of
kubernetes
using
cuba
DM
to
run
it.
C
It
supports
different
write
with
both
the
docker
run
time
and
CRI
containers.
A
we've
been
using
that
for
testing
CRI
container
d.
It's
designed
to
be
customized,
you
can
add
different
networking
whatever,
and
it's
also
the
upstream
for
the
docker
desktop
editions
where
we're
shipping
kubernetes
on
the
desktop
supports
any
day.
Now
you
can
sign
up
for
the
beta
at
beat.com
and
it
will
probably
ship
in
the
next
few
days.
C
C
As
you
know,
it's
all
it's
all
exactly
the
same
code
as
we're
using
in
the
upstream
open
source
project
that
you
can,
if
you
want
to
make
different
customizations
using
the
same
code,
but
it's
just
designed
to
be
really
really
easy
to
use
and
we're
incredibly
excited
that
we're
being
able
to
ship
out
kubernetes
on
the
desktop
for
to
millions
of
users
a
photographer
and
windows.
Just
like
we
think
that's
really
going
to
help
people
get
get
get
their
hands
on
Cuba
nations
to
the
first
time.
C
We
understand
how
to
use
it
and
and
have
a
really
easy
development
experience.
So
I'm
going
to
show
you
a
few
demos,
we've
got
a
few
minutes
for
demos.
I'll
show
you
here:
here's
the
this
is
the
new
docker.
That's
about
to
dock
at
the
Mac.
That's
about
to
ship
with
the
Dockers
running,
communities
are
running
and
the
preference
thing
here,
which
is
enable
communities
which
is
you,
click
that
button
it
takes
a
minute
or
so,
and
it
will
just
restart
with
community
support
and.
C
When
you're
running
it,
you
can
you
you've,
just
got
a
noble.
You
know
normal
communities,
there
cube
kettles
already
installed,
it
tells
you
it's
docker
for
Mac
and
running
kate
kernel,
and
this
is
raucous
1711.
So
it's
all
really
really
straightforward.
You
can
just
use
janessa's
as
you
as
you
normally
would
I'm
going
to
show
you
a
quick
example
of
how
easy
it
is
to
build
something,
a
Linux
kit.
C
So
this
is
a
really
simple
landscape,
Yamma
file
that
we
have
just
at
the
top
of
the
repo
we
say
which
kernel
we
want,
which
version
of
container
D
whatever
we
want,
and
this
apart
from
the
other
thing,
it
just
runs
the
nginx
image
from
docker
hub,
the
our
phone
one,
and
so
it's
really.
It
shows
that
you
can
just
run
services
from
straightforward
upstream
normal
containers.
C
C
Just
thinking
which
we
built
and
there's
known
as
boost
as
you
can
see,
they
were
I've
got
more
quite
big
text
on
this
things,
so
we've
just
booted
up
learners,
kids
got
a
console
and
we're
just
running
a
very
few
processes.
We
can
just
connect
to
nginx
and
get
there
hello
world
page
from
nginx.
So
that's
how
simple
it
is
to
just
build
a
very
simple,
simple
service.
Kubernetes
is
obviously
slightly
more
complicated,
but
not
much.
This
is
a
console
on
actually
on
docker
from
Mac,
and
you
can
see
it's
running.
C
So
you
can
see
it's
running.
Docker
container
decompose,
keep
DNS,
we've
networking
keep
proxy
everything
the
poor's
container.
So
it's
just
a
you
know,
just
a
very
simple
giving
it
is
install
that
we've
built
with
learners
kits,
which
is
basically
exactly
the
same.
It's
basically
the
same
characters.
If
you
go
to
kit
the
lens
kit,
kubernetes
repay,
all
I
did
made
us
all
very
large
from
each
other
when
the
screen
was
a
bit
small.
C
So
this
is
the
nose
kick
kubernetes
repo,
which
has
a
very
simple
build
process
that
you
can
basically
build
your
own
cube
initially
to
customize
it
and
basically
configure
it
in
different
ways,
and
you
can
kind
of
get
started
with
that.
So
it's
it's.
It's
a
really
simple
way
to
build
communities,
images
for
local
use
for
production
use
and
we've
got
a
lot
of
people
working
with
us
on
this
who
want
to
use
it
in
production.
C
We've
been
talking
to
had
a
chat
about
integrating
it
into
cops
yesterday,
for
example,
which
would
be
I
think
would
be
really
cool
to
do
so
that
you
can
deploy
it
on
AWS
easily
with
cops
and
we've
got
lots
of
people
who've
got.
You
know
real
interested
in
putting
this
into
production
in
large
companies,
and
things
say
we're
really
quite
excited
about,
particularly
the
knesset
integration,
because
a
load
of
a
load
of
people
have
come
to
us
and
said
that's
what
they
want
to
use
landscape
for.
C
A
A
A
A
A
A
It's
all
based
on
containers.
We,
we
launched
it
at
Linux
Con
in
Berlin,
in
October
2016,
one
of
the
difference
between
infrakit
and
other
infrastructure
management
systems
that
it's
it's
doing,
an
active
monitoring
of
the
infrastructure
and
if
the
description
that
you're
telling
him
that
you
want
for
your
infrastructure
differs
with
reality
in
frack,
it
takes
active
action
to
change
that.
A
So
we
proposed
it
to
C
and
C
F
last
June,
and
it's
a
little
bit
too
soon
to
accept
infrastructure
management
projects
in
there.
But
these
are
actually
some
of
the
slides
that
we
use
in
order
to
present
it
to
CN
CF.
So
it's
focusing
on
the
provisioning
aspect
of
provisioning,
so
you
could
use
it
to
provision
your
kubernetes
cluster
or
your
docker
cluster,
so
in
the
CN
CF
landscape.
It
tackles
that
that
part
at
the
bottom
there
and
the
kind
of
use
cases
that
he
can
be
used
for
is
to
set
up
your
day.
A
Zero
install
and
also
your
day,
one
configure
for
container
orchestrators,
but
where
intricate
really
shines
is,
in
day
n
automation
of
infrastructure
like
how
to
provision
you
nodes,
how
to
update
your
nodes
with
new
versions
of
the
orchestrator
itself,
one
of
the
yeah.
Actually
time
is
done,
but
just
one
thing
I
wanted
to
mention
is
the
one
of
the
really
interesting
development
in
infrakit.
A
Recently
David
Chang
who's
working
on
that
has
been
working
on
a
cluster
autoscaler
for
kubernetes,
so
your
kubernetes
cluster,
connected
to
infrakit
could
based
on
some
metrics
that
you
define
Auto
scale
the
cluster
itself
based
on
the
load,
so
lots
of
interesting
developments
tied
to
kubernetes
there,
so
that
these
are
the
details,
but
the
autoscaler
and
you
can
get
involved
on
github
docker,
slashing
racket.
You
can
learn
more
about
all
the
projects.
On
the
movie
blog,
we
had
a
movie
summit
at
Doc
Ock
on
this
year
that
had
tons
of
talks.
A
All
these
talks
have
been
recorded
and
all
the
slides
have
been
published
on
our
blog,
so
it's
blog
that
movie
project
or
org
or
you
go
on
github
and
you
can
find
the
code
and
play
with
it.
Thanks
very
much.
Many
of
us
well
we'll
be
at
the
conference,
so
you
can
find
us
either
at
the
docker
booth
or
in
the
corridors
and
there's
one
more
session.
That
should
be
pretty
interesting.
It's
the
open,
fast
session
by
Alex,
Ellis,
so
open
fascism.