►
From YouTube: Container Registry
Description
in this lightboard talk, Massimo Re Ferre provides an introduction to container registry.
A
Hi,
my
name
is
Masum
oleifera,
I'm
a
technical
product
manager
with
the
current
native
application
business
unit
and
vmware.
In
this
brief,
talk,
I'm
going
to
talk
about
container
registries
in
the
previous
shooting
I
have
introduced
the
concept
of
containers
and
the
concept
of
basic
concept
of
docker
in
this
particular
session,
and
in
this
particular
brief
talk.
A
Basically,
the
processes
that
you
describe
in
a
docker
file
how
your
application
and
the
packages
that
your
application
requires.
Look
like
you
basically
script,
that
into
what's
called
the
docker
file
you're
only
built
against
the
docker
file
and
the
docker
file
produce
an
image
or
the
big
process
produce
an
image
that
is
hosted
on
the
docker
host,
where
you're
running
the
build
process.
Again,
when
you
have
an
image,
then,
on
the
same
host,
you
can
run
that
image
and
that
run
basically
instantiate
that
docker
image
as
a
container
on
that
host.
A
What
we're
going
to
briefly
talk
about
here
is
the
notion
of
being
able
to
push
and
pull
that
docker
image.
One
of
the
advantages
of
darker
one
of
the
many
advantages
of
docker
is
that,
when
you're
building
your
application,
the
active
fact
of
your
application
as
a
docker
image,
it
is
very
easy
to
to
share
that
image
with
someone
else.
A
The
way
that
this
work
is
because
register
because
docker
when
they
introduce
the
very
core
technology,
they
have
introduced
the
notion
of
a
hub
where
you
can
actually
push
and
pull
these
docker
images.
The
docker
hub
lives
in
the
cloud
right.
So,
basically,
in
order
to
be
able
to
share
these
docker
image
with
someone
else,
what
you
have
to
do
is
basically
you
have
to
push
this
image
into
the
docker
hub
service
that,
as
I
said,
live
in
the
cloud
or
in
the
Internet
right.
A
At
this
point,
what
happens
is
that,
if
something,
if
someone
else
would
like
to
use
your
image,
they
can
just
pull
that
image
off
of
docker
hub
and
they
are
ready
to
go
without
having
to
go
obviously
through
the
build
process,
which
is
probably
something
that
you
have
to
do
at
the
owner
of
the
application.
This
works
beautifully,
but
a
lot
of
customers
are
asking
for
other
options
to
store
those
images
in
unprimed
registries
right.
A
So
basically,
what
docker
provides
in
what
the
ecosystem
has
been
building
upon
is
the
notion
of
the
docker
registry
as
a
piece
of
software
that
you
can
instantiate
wherever
you
want.
You
can
obviously
instantiate
this
docker
registry
in
the
cloud
as
well,
but
most
likely
a
lot
of
users
are
interested
in
the
use
case
of
instantiating
that
darker
edges
on-prem.
A
One
of
the
darker
registry,
that
I'm
going
to
talk
about
is
harbor.
Harbor
is
an
open
source
project
sponsored
by
VMware
and
basically,
what
we
have
done
is
we
took
the
open
source
version
of
the
docker
registry.
That
docker
has
been
writing.
We
took
that
code
and
we
extended
it
to
add
enterprise
features
to
it.
We
keep
harbor
as
an
open
source
project.
A
We
also
add
a
UI
or
a
graphical
user
interface.
We
also
add
a
replication
mechanism
so
that
you
can
have
multiple
harbor
instance
inside
your
data
center
or
across
multiple
data
centers,
and
let
harbor
replicate
those
images
without
having
you
to
push
those
images
into
different
harbor
services
and
obviously
Active
Directory
and
LDAP
integration.
A
So
these
are
some
of
the
features
we
have
more
inside
harbor,
but
these
are
some
of
the
features
that
we
are
basically
adding
to
the
basic
docker
registry.
As
I
said,
we
keep
our
open
source,
so
you
can
go
on
github
and
download
harbor.
So
why
are
people
interested
in
doing
these
versus
going
into
docker
hub?
We
came
across
a
number
of
different
use
cases,
three
of
which
the
three
most
common
use
cases
are
latency
right
and
speed.
A
So
if
you
have
to
push
a
large
image
or
multiple
large
images
to
docker
hub
on
the
Internet,
you
have
internet
as
a
roadblock
and
obviously
so.
People
may
be
requiring
to
have
a
non-prime
setup
of
a
docker
registry
where
they
can
push
and
pull
images
faster
regulatory
requirements
where
there
are
some
customers
that
like
to
keep
those
images
on
Prime
and
they
would
not
like
to
push
them
into
a
service
running
on
the
open
Internet.
A
And
the
third
use
case
that
we
came
across
very
often
is
that
some
of
the
enterprise
customers
that
we
have
been
working
with
do
not
have
open
access
to
the
Internet.
So
some
of
them
are
able
to
set
up
darker
on
a
number
of
docker
host,
but
they
do
have
problems
in
reaching
out
docker
hub
because
of
the
policies
that
they
have
from
a
networking
and
firewalling
perspective.
So
having
a
local
hub
inside
their
organization,
make
their
sharing
inside
the
company
of
those
docker
images.
Much
easier.