►
From YouTube: Docker Networking Options
Description
In this lightboard talk, Nathan Ness walks through the networking options in Docker.
For more information, please visit the VMware’s Cloud-Native Apps website:
https://cloud.vmware.com/cloud-native-apps
A
A
A
After
that,
we're
going
to
draw
the
default
docker
bridge,
this
is
usually
called
docker
0
within
the
dr.
0.
We
can
hang
containers
off
that
provision,
containers
container,
1,
container
2
so
anytime.
These
containers
are
going
to
talk,
outbound
or
external
to
the
hosts
they're
going
to
be
NAT
'add
at
the
iptables
level
and
have
a
source
address
of
whatever
IP
addresses
at
the
container
host,
and
so
inbound
connectivity
is
going
to
require
a
D
net
rule.
A
When
you
start
the
docker
container,
it's
going
to
require
that
you
expose
port,
80
or
map
a
port
on
the
host
side
to
the
port
on
the
container
side,
and
this
can
be
any
arbitrary
port
to
a
specific
port
on
the
container
1
and
so
maybe
I
might
have
8080
mapped
to
80
on
the
backend.
So
this
would
be
the
host
port
and
then
it's
going
to
go
back
to
port
80
on
container
1,
but
just
know
that
the
default
behavior
of
docker
is
going
to
be
net
outbound
and
inbound
communication.
A
So
this
is
going
to
actually
perform
both
D
net
and
s
net
for
outbound
and
inbound
communication
container
to
container
communication.
So
container
one
talking
to
container
two-
this
would
happen
over
the
dr0
bridge
and
that
communication
will
be
inherently
allowed.
Okay,
the
next
option
that
we
have
is
user,
specific
bridges
or
what
are
call
user-defined
bridges.
A
A
A
And
then
we
can
have
containers
hanging
off
of
each
of
these
different
bridges,
and
you
would
do
this
with
the
net
command
when
you
start
the
dr
container.
So
what
this
allows
you
to
do
is
have
some
isolation
between
containers,
so
by
default,
these
two
containers
cannot
talk
to
each
other
and
then
the
same
inbound
and
outbound
behavior
remains
the
same.
A
A
Doctor
0
and
will
draw
one
container
off
of
their
container
2
this
time
now
we're
going
to
add
in
what's
called
an
overlay
Network
and
an
overlay
network
is
used
for
encapsulation
across
your
physical
network,
and
this
allows
typically
VMs
or
containers
or
whatever
you're
hooking
into
this
to
be
on
the
same
layer
to
segment,
which
is
exactly
what
this
is
going
to
do.
So
here
we
have
our
containers
connected
to
our
overlay,
and
this
allows
container
to
container
communication
over
a
multi
host
Network
without
using
network
address
translation.