►
From YouTube: The Level Up Hour (S1E8): Podman Pods & Data Containers
Description
How Red Hat Enterprise Linux (RHEL) users and admins can benefit their organizations and improve their careers by learning how to use containers, Kubernetes, and Red Hat OpenShift.
Learn more at https://red.ht/leveluphour
A
Hello
good
morning,
good
afternoon,
good
evening,
wherever
you're,
from
welcome
to
the
level
up
hour,
where
we
aim
to
get
our
fellow
rel
admins
up
to
speed
on
all
the
fun
things
we're
doing
in
the
container
land.
I
am
joined
by
the
the
real
brains
of
this
show
langdon
white
lang.
Then
please
introduce
yourself
to
the
audience
for
anybody
new,
that's
watching
today
and
they'll.
Let
us
you
know
kind
of
regale
upon
your
resume.
I
guess
exactly.
B
So
I'm
lagging
white.
I
have
spent
many
years
now
working
with
rel
as
one
of
the
platform
architects.
For
a
long
time
now,
I
am
in
technical
marketing
management,
which
means
I
try
to
help
with
outreach
in
things
like
shows
like
this,
to
try
primarily
I'm
interested
in
the
container
adoption
by
the
entire
world,
because
the
separation
of
interests
is
very
useful
for
the
long-term
running
of
of
linux
and
the
long-term
running
of
computers.
I
want
to
see.
B
Yeah
yeah,
you
know,
I
mean
if
you
ever
check
out
the
cube's
projects
q-u-b-e-s
or
plan
nine.
That's
actually
kind
of
what
I'm
interested
in
seeing
happen
one
of
these
days,
but
maybe
a
little
more
performant
yeah.
So,
let's
see
if
we
have
any
plugs
we
wanna
start
off
with.
I
know
I
want
to
pitch
devconf.us
starts
next
week
and
that
will
be
as
a
result.
We
will
be
not
having
a
show
next
week
so
but
u.s
right,
correct,
yeah
so
definitely
come
check
it
out.
B
Right
right,
it's
free
actually,
even
when
it's
in
real
life.
Oh,
I
didn't
know
that
either.
A
B
All
the
dev
comps
are
that's
why
you
know
when
you
register,
please
try
to
actually
come
because,
obviously
we
pay
for
the
number
of
people.
We
think
we're
going
to
come.
B
Oh
totally
yeah,
if
there's
registrations
open
and
you
should
come
and
it
will
be
fun,
there's
lots
of
container
talks
there's
a
lot
of.
Basically,
the
focus
is
upstream
projects,
so
there's
not
a
lot,
there's,
basically,
no
product
kind
of
allowed,
in
a
sense,
no
product
pitches,
including
no
project
pitches.
It's
got
to
be
like
real
stuff.
That's
going
on.
B
You
could
do
kubernetes
in
a
sense,
but
you've
got
to
talk
about
what
you
want
to
what
why
this
cool
new
thing
is
happening
in
kubernetes
rather
than
you
know.
Kubernetes
is
awesome
for
the
sake
of
awesome,
although
arguably
kubernetes
is
so
new
to
a
lot
of
people
that
you
could
argue,
for
you
know
cool
for
the
sake
of
cool.
You
know,
but
doing
the
same
kind
of
thing
of
you
know
why
rel
would
would
generally
not
get
you
a
slot
as
a
as
a
speaker.
B
The
other
big
thing
that
we
do
is
we.
We
have
speaker
coaching,
attendee
coaching,
so
that
you
can
basically
so
that
newbies
can
feel
comfortable
coming
to
the
conference
or
giving
talks
to
the
conference.
So
we
want.
We
want
new
speakers
as
well
as
accomplished
speakers,
and
we
want
new
attendees
as
well
as
accomplished
attendees.
We
can.
We
explain
to
people
what
the
hallway
track
is
we
give
coaches,
we
have
meetups
and
stuff
like
that
for
people
who
want
to
get
involved.
B
A
What
is
devconf.us?
Yes,
we
answered
the
question.
Alrighty
you're,
not
too
late,
swathi
go
ahead,
I'm
registering
right
now.
Actually,
so
that's
why
I
didn't
see
the
question
in
time.
B
We
even
so
it's
just
a
virtual
conference
with
lots
of
different
talks
about
lots
of
different
technology,
open
source
projects
and
there's
even
workshops
of
the
day
before
kind
of
the
main
conference
content.
So
we
so
you
can
sign
up
for
those
especially
and
that's
actually
like
hands-on
work
with
an
instructor
about
various
technologies,
cool.
A
B
Out,
well
so
suffice
to
say
we
will
not
be
around
next
week,
for
this
show
there
will
be
lots
of
other
shows
still
going
on,
of
course,
which
we
usually
cover
at
the
end,
and
then
we
will
resume
our.
You
know
same
that
channel
same
that
time,
the
following
week,
which
would
be
the
20.
B
The
30th
yes
and
so
yeah
so
join
us
then
or
join
us
at
def.
Conf.
Definitely
look
me
up.
I
will
be
running
around
like
a
crazy
person,
but
you
know
definitely
come
and
check
it
out.
A
B
Well,
let's,
let's
hit
the
slides,
so
we
can
pitch
last
week's
show.
C
B
So
this
is
the
level
up
hour
in
case
you
were
confused
about
where
you
were.
Sometimes
I
am
so
I
like
that
we
put
up
the
big
screen,
so
that's
good.
You
can
find
us
on
twitter
and
you
can
chat
with
us
on
our
discord,
which
I
have
open
right
now,
but
it's
I
always
struggle
with
whether
I
watch
the
twitch
chat
or
the
discord
chat.
Well,.
B
And
then
moving
on
today
we're
gonna
talk
about
podman
pods.
We
were
supposed
to
talk
about
them
last
time
we
didn't
really
get
to
it.
I
asked
a
question
on
twitter,
which
got
me
some
snarky
replies.
So
that's
good.
So
we'll
talk
about
that.
A
little
bit.
A
B
B
But
I'll
explain
why,
when
we
get
to
it
so
and
then
or
you
can
go,
look
at
my
twitter
feed,
the
oh
and
then
I
also
do
show
notes
for
every
show,
including
video
highlights.
So
if
you
want
to
see
my
semi
sarcastic
content
around
the
show-
and
you
know
kind
of
what
we
discovered
or
whatever
I'm
trying
to
think
of
some
of
the
funny
highlights
from
last
time,
because
what
I
always
try
to
do
is
a
little
more
research
on
whatever
craziness
comes
up.
B
For
example,
you
know
a
few
weeks
ago
we
talked
about
podman,
the
rapper
and
you
know
so.
Of
course
I
have
links
to
parappa
or
the
rapper
and
and
run
dmc,
but
so
check
out
the
show
notes,
and
then
we
will
hold
off
on
slides
from
there,
because
the
next
slide
is
sweet,
sweet
internet.
A
B
Yes,
yes,
so
periodically,
we
get
help
from
the
chat
as
well
about
remembering
the
points.
So
that's.
A
B
Oh
well,
it
is
yes,
but
it's
the
podman
man
page.
B
Do
that
for
now
because
there's
some
ad
on
the
man
page
unusual.
A
A
B
Exactly
I
was
actually
looking
for
the
because
I
believe
the
podman
man
pages
are
produced
as
markdown
and.
B
Looking
for
the
get
repo
for
it,
but
that's
the
one
I
came
across
first,
so
that's
why
I
had
it
open
all
right
so
getting
into
what
we're
supposed
to
be
talking
about
today.
B
Okay,
so
when
we've
been,
what
we've
been
talking
about
so
far
is
kind
of
single
containers
that
that
accomplish
a
goal
so
like
what
I
usually
refer
to
as
executable
containers
so
like
we
had
the
blender
render
container
and
then
chris,
actually,
over
this
past
week,
suggested
that
I
make
a
an
image
magic
container.
B
I
don't
know
what
got
that
far,
but
one
that
would
do
so
image
magic
is
a
really
really
useful,
open
source
project
similar
to
pandoc,
both
of
which
are
worth
checking
out,
but
image
magic.
Has
this
convert
function
and
making
a
convert
executable
container
so
that
you
can
convert,
say
a
png
to
a
jpeg
just
on
the
command
line
or
in
a
script
which
is
quite
useful
and
because
image
magic
is
actually
fairly
decent
sized.
B
I
actually
have
a
friend
who's
primary,
like
he's.
Actually,
a
consulting,
you
know,
he's
a
consultant,
but
has
a
little
company,
but
his
one
of
his
big
clients
is
actually
the
prosecutors
association
of
a
state
and
they
have
this
monster
wiki
to
kind
of
support.
All
the
other
prosecutors
in
the
state,
with
like
expert
testimony
and
like
content
about
various
cases,
and
things
like
that.
But
one
of
the
big
things
he
has
to
do
is
convert
massive
amounts
of
video
content
into
usable
versions.
B
Like
you
know,
it
comes
out
of
some
like,
let's
say,
police
department
and
they
have
some
weird
format
of
video
because
their
body
cams
are
you
know
some
proprietary,
weird
thing
or
whatever,
so
he
actually
has
a
big
kubernetes
cluster
that
does
all
of
the
image
conversion
on
demand
on
the
fly
and
dynamically
allocating
so
that
he
can
kind
of
run,
lots
and
lots
of
different
engines
when
he
has
lots
of
data
to
convert
and
then
ramp
it
down
when
when
it
slows
down
and
vice
versa
right,
it's
a
it's
a
really
cool
system
and
he
is
working
very
hard
to
open
source
it
and
I
think
it
might
be.
B
Finally,
so
if
I,
if
I
find
it,
I
will-
or
if
I
talk
to
him
and
get
the
link
I'll
put
it
in
the
show
notes
but
yeah
it's
it's
really
quite
cool.
So
I
think
that
is
a
not
uncommon
problem
to
need
to
do
massive
conversions
of
video
or
images,
and
then
pandock
does
docs
types.
So,
if
you
have
you
know,
let's
say
a
microsoft
word
file
and
you
want
to
convert
it
to
openofficewriter.
B
It
will
do
that
on
the
fly
it
does
markdown,
it
does
html
it
does
everything.
It's
brother,
it's
cool,
yeah,
it's
it's
really
nice.
I
use
it
all
the
time
so,
but
both
of
those
would
be
really
nice.
Executable
containers,
yeah.
B
The
next
thing
we
talked
about
was
also
kind
of
like
taking
a
slightly
different
approach
where
you
kind
of
bundle
all
your
tools.
You
know
your
useful
tools
into
one
container
and
then
take
that
container
and
put
it
and
then
kind
of
move
it
around
your
data
center
based
on
where
you
need
those
tools
so
that
you
don't
have
to
be
so.
You
don't
have
to
install
excuse
me,
so
you
don't
have
to
install
those
tools
in
every
machine
that
you
might
want
to
work
with.
B
But
today
what
we're
going
to
talk
about
is
let's
say
we
need
some
sort
of
a
combination
of
the
two,
and
I
did
a
fair
amount
of
testing
about
this,
but
not
completely
so
it
may
go
poorly
towards
the
end,
so
we'll
see
yeah.
This
will
be
great.
B
Right
right,
so
I
will
say
it's
still
a
little
contrived.
It's
not
as
contrived
as
you
know,
basically
just
doing
a
wordpress
example,
so
I
wanted
to
keep
it
kind
of
relevant
and
but
at
the
same
time
I
didn't
want
to
you
know,
so
I
wanted
to
keep
it
kind
of
relevant.
B
But
you
know
still,
you
know
it's
a
tv
show
we're
not
really
you
know
it's
not
it's
not
entirely
for
real,
but
hopefully
you'll
get
the
idea
and
be
able
to
build
your
own
thing
based
on
it.
It's
kind
of
for
real,
but
it's
kind
of
for
real.
Yes,
exactly
all
right.
B
So,
let's
see
I
have
a
number
of
files
here
and
we're
going
to
start
with
the
most
contrived
one,
which
is
this
support
tools,
container
file,
and
so
what
I
did
here
was
I
just
changed
the
you
know
the
extensions
on
each
of
these
to
keep
track
of
which
ones
which,
rather
than
like,
make
subdirectories
and
everything
else,
because
again
going
back
to
the
empty
squat.txt
example.
B
You
know
your
container
file
could
be
called
whatever.
I
just
try
to
use
the
word
like
container
file
for
consistency's
sake,
so
I
remember
what
it
is,
but
you
know
I
I'll
add
an
extension
sometimes
to
indicate
which
thing
is
which
so,
as
you
can
see,
this
is
a
super
simple
container.
Basically,
all
it
is
is
a
wrapper
around
the
rel
upstream
support
tools.
So
why
would
I
do
this?
B
B
B
So
you
know
I
you
know
suspect
I
will
want
to
add
some
features
to
that
container
at
some
point
in
the
future.
So
I
just
shove
a
container
file
there
and
I
may
add
to
it
later
so.
The
first
thing
we're
going
to
do
is
just
build
this
guy.
C
B
A
B
Right,
yeah
yeah,
so
this
container
file,
so
we're
gonna,
build
that
into
a
container
image,
and
I'm
gonna
remember
how
to
do
that,
and
that
would
be
nice
and
just
for
the
sake
of
conversation,
point
at
this
point
we're
using
sudo
for
a
reason
in
a
few
minutes,
and
and
in
a
bit
we'll
find
out.
This
is
basically
where
my
bug
derives
from
and
we
will
then
go
back
to
then
we'll
see
why
I
don't
want
to
use
sudo
in
a
bit
right
all
right.
B
So
so
we
say
we
give
it
a
name
oops
and
we're
gonna
call
our
new
container
image,
support
tools
just
to
make
it
shorter
and
then
we're
going
to
say:
okay
and
then
we
give
it
the
file
name
container
file
that
support
tools,
and
then
we
just
give
it
a
dot
to
say,
use
this
local
directory.
B
B
All
right,
so
I
previously
built
this,
so
it
went
very
very
quickly,
and
so
now
we
have
a
container
image.
That's
just
called
support
tools
and
just
for
the
sake
of
discussion,
we
will
just
see
what's
here,
because
what
I
want
to
point
out
is:
we
now
have
support
tools
here.
That's
got
a
localhost
as
a
namespace,
but
then
I've
also
got
the
regular
old
support
tools
that
came
from
red
hat
right
so,
and
so
the
name
spacing
is
how
we
tell
the
difference.
B
Even
though
we
have
two
now
called
support
tools
and
going
back
to,
I
think,
was
last
week
when
we
talked
about
the
registry
order.
If
so,
localhost
is
always
first,
but
then
it's
based
on
the
registry
order
in
the
registries.com
file,
which
of
these
will
be
chosen.
If
you
give
it
a
bear,
let's
just
move
that
guy
over
there.
If
you
give
it
a
bear
name.
So
if
I
do
pod
man,
let's
just
say,
run,
I
t-
and
I
do
like
this
and
just
say-
support
tools.
B
It'll
choose
the
local
host
one
by
default
or
first,
and
it
will
choose
the
relate
one
second
or
if
I
had.
Let's
say
there
was
a
support
tools
in
fedora.
If
you
remember
from
last
week,
I
had
fedora
as
kind
of
further
down
the
chain
it
would.
It
would
still
choose
the
rel
one
first,
so
probably
better
to
name
space
everything
so
to
actually
say
localhost
support
tools
like
that,
but
you
know
we're
often
lazy.
So
this
is
just
what
will
happen
if
you
do
it
this
way?
B
Okay,
and
so
you
know
it
runs
and
great-
I
have
stuff,
and
then,
if
you
notice,
I
use
the
dash
dash
rm
because
I'm
using
a
one
off
tool.
This
is
also
really
useful
if
you're
doing
the
like
executable
containers,
because
if
you
don't
use
the
dash
dash
rm,
it
will
stick
around
in
your
podman
container
list.
So
the
actual
containers
versus
container
images-
and
if
I
do.
B
A
B
So
all
right,
so
then
the
other
thing
we've
been
working
with
is
our
perfect
tools
container.
So
if
we
just
look
at
the
perfect
tools
guy,
this
you'll
remember
from
I
think
a
couple
weeks
ago.
You
know
it's
got
a
bunch
of
features
we
like,
but
it's
also
based
on
the
support
tools
container,
and
then
we
actually
set
up
python
to
be
there
by
default.
If
you
do
user
bin.
B
B
Let's
see
perfect
tools
all
right,
so
obviously
I
built
it
before,
so
it
doesn't
take
very
long
because
of
the
lovely
cache
just
by
way
of
discussion.
I'm
not
actually
gonna
run
it.
So
it
doesn't
take
too
much
time,
but
you
can
add
it's
just
no
cash
right,
yeah
cash
yeah
and
it
will.
I
thought.
A
B
And
do
grep
cache
so
yeah.
So
if
you
use
oh.
B
It
will
rebuild
everything
so
takes
a
while,
but
sometimes
a
good
idea.
The
thing
to
remember
actually
about
no
cache,
though,
is
that
that
does
not
mean
it
will
go
and
re-poll
right
the
from
line
so
so.
B
Exactly
so
just
to
kind
of
note
that,
because
we
hardly
ever
use-
or
I
almost
always
use
the
cache
during
the
show
so
that
things
take
less
time
right
all
right,
so
we
built
the
perfect
tools
container
and
now.
Another
kind
of
new
concept
we
have
here
is
they've
kind
of
they
seem
like
they've
fallen
a
little
bit
out
of
favor,
I'm
not
really
sure,
but
they
used
to
be
really
common,
but
this
is
what's
referred
to
as
a
data
container.
B
B
Does
is
it
exposes
a
bunch
of
volumes
and
I,
like
them
quite
a
lot,
and
I
actually
would
will
sometimes
or
depending
on
what
I'm
trying
to
accomplish.
I
will
actually
put
functionality
in
a
data
container,
because
what
you
can
do
is
things
like
you
could
have
a
running
job
in
here
that
whatever
data
lands
in
this
data
container
or
sort
of
lands
in
this
data
container,
it's
a
little
confusing.
Maybe
I
could
do
backups
against
it
right,
so
I
could
actually
have
a
running
process
in
that
container.
B
That
will
actually
automatically
do
backups
or
you
know,
maybe
automatic,
pushes
to
say
a
github
repository
or
whatever
something
like
that,
so
you
can
have
functionality
in
them.
It's
just
that's
not
kind
of
the
default
answer
and
I've
actually
been
looking
for
a
long
time
for
more
kind
of
backup
providers
or
like
or
storage
providers
or
whatever,
to
get
more
into
data
containers
and
offer
those
kinds
of
features
as
pre-built
containers.
B
A
Like
I
feel
like
those
those
backup
programs
from
the
past,
like
bakula
and
all
those
folks
are
starting
to
like
get
to
get
the
message
that,
like
backing
up
containers
and
backing
up
cloud
native
infrastructure,
is
the
future
for
them.
So,
like
I've
seen
some
increased
messaging
right
like
I
keep
a
really
close
eye
on
the
news
from
my
newsletter.
A
B
Right
right
and-
and
although
I
will
say
I
think,
a
lot
of
that
is
about-
and
this
isn't
a
bad
thing
necessarily,
but
a
lot
of
those
backup
tools
are
looking
at
the
container
images
as
they
land
on
disk,
which
is
slightly
different
from
what
I'm
talking
about
here,
which
is
more
like.
B
I
want
an
actual
container,
that's
smart
enough
to
be
a
backup
engine
in
a
sense
which
I
think
is
kind
of
next
level
sophistication
which
you
know
hopefully
we'll
get
to
soon,
but
I
I
haven't
seen
a
whole
lot
of
that
yet,
but
we'll
see
okay,
so
point
being
right.
B
I
have
this
container
now
or
I
mean
I
have
right
now.
I
just
have
a
text
file,
but
we
will
now
build
our
container
file.
I
didn't
say
the
word
you're
welcome,
let's
see,
podman
build
t
and
let's
call
this.
I
think
I
called
it
data
container.
C
B
Well,
it
it'll,
actually,
it
won't
actually
rebuild
it
because
of
the
because
of
the
tagging
right.
So
you
know
it'll
actually
figure
it
out
and
just
tag
a
new
version,
but
just
for
the
sake
of
consistency,
so
I
don't
get
confused.
B
If
you
noticed,
I
called
it
data
container,
which
is
where
I
was
going
to
begin
with,
and
we
will
call
it
data
container
and
then
we
will
tell
it
we're
going
to
use
this
container
file
and
then
build
build,
build,
build,
build
all
right
and
as
expected
right,
even
if
I
was
using
a
no
cache
right,
that's
going
to
go
really
fast
because
it
doesn't
really
do
anything.
B
B
So
let's
say
we
have
our
two
different
containers.
We
have
our
support
tools
container
and
we
have
our
perfect
tools
container
and
they
want
to
share
some
data
between
them.
So
let's
say
I
this.
This
is
a
classic
problem
right
in
that
I
love
a
particular
version
of
a
particular
piece
of
software
that
I,
like.
I
really
like
mtr
version
one
and
mtr
version.
B
2
is
what's
shipping
everywhere,
so
I
build
a
container
that
actually
has
mtr1,
so
it's
in
one
container,
but
then
everything
else
is
in
another
container
because
they're
conflicting
for
whatever
reason
so,
but
I
need
them
to
share
data.
So
what
I
do
is
I
actually
create
a
data
container
called
with
a
subdirectory
called
data
and
then
another
example-
and
we
talked
about
this
a
little
bit
last
time
is
let's
say
inside
the
container.
I
need
things
like
ssh
keys,
but
I
don't
want
to
do
two
things
one.
B
B
And
do
everything
and
that's
bad?
I
could
just
put
them
on
disk
somewhere
and
then
mount
them
in
the
right
place
in
every
container.
But
what
happens
when
the
keys
move,
for
whatever
reason?
Well,
one
thing
you
can
do
is
basically
the
data
container
can
offer
a
layer
of
indirection
between
where
the
containers
think
the
keys
are
and
where
the
keys.
B
To
you
that
way
and
you're
very,
very
afraid
of
changing
very
much
about
it,
because
everything
could
fall
over
and
stop
working.
You
know
those
that
set
a
key
files,
for
example,
might
be
on
each
of
those
servers,
but
maybe
it's
in
different
places
right,
because
you
know
it's,
it's
some
legacy
thing
they're
different
versions
of
they
could
be
different
versions
of
linux.
There
could
be
all
sorts
of
different
reasons
right.
B
So
what
this
does
is
masks
that
layer.
You
know,
basically,
as
I
said
before,
it
requires
a
or
provides
a
layer
of
indirection
between
the
container,
that's
using
the
keys
and
the
actual
file
system
where
the
keys
live.
So
now
what
we
want
to
do
is
the
first
thing
we
want
to
start.
Is
the
data
container
so
the
way
we
do,
that
is
pseudo
podman
and
run
and
we're
not
getting
quite
to
pods?
Yet
because
I
wanted
to
explain
data
containers
first,
but
then
we'll
get
to
pods
later,
I'm
gonna
run
this
guy.
B
A
Might
have
said
something
in
twitch
that
was
completely
like
future
news,
so
jp
dave
that
is
subject
to
change
so
just
to
let
you
know,
but
that's
what
we're
thinking
of
summit
this
year,
my
bad.
B
A
Worries
I
so
we
have
the
problem
on
the
show
for
our
channel
frequently
of
we.
We
live
in
the
future
sometimes,
and
we
have
information
before
it's
public
or
we
we
have
access
to
tools
before
they're,
actually
like
production,
ready
kind
of
thing,
so
yeah
the
summit
page
itself.
Thank
you.
Whoever
that
redhead
is
you've.
You
kind
of
built
me
out
there.
I
saw
an
email
about
red
hat
summit.
Recently,
jpd
brought
it
up
in
chat
that
you
like.
Are
we
going
to
have
it?
Yes
or
no?
It's
like.
B
Right
right
and
yeah-
and
it's
I
mean
you
know,
there's
still
so
much
messed
up
in
the
pandemic
world
that
you
know,
I
think
we're
still
a
little
touch
and
go
on
on.
What's
going
on
like.
C
A
C
B
Likewise,
so,
okay,
so
going
back
to
the
data
container,
so
I'm
going
to
run
this
container
and,
oh
just
so,
I
set
up
a
couple
of
stupid
directories
to
show
my
data
directory
and
my
keys
directory,
and
so,
if
I
run
this
container,
we
are
going
to
see
we're
gonna
do
dt
and
then
we're
going
to
do
minus
v
and
then
we're
going
to
do
dollar
pwd.
B
So
one
thing
about
volumes,
you
always
need
to
give
a
full
path
to
wherever
you
are.
This
is
something
I
really
wish
they
would
short
circuit
somehow
by
just
letting
you
use
dot
or
something,
and
so
I'm
gonna
say
data
and
then
data,
and
then
I'm
gonna
mount
that
into
the
volume
at
mount
data
and
then
normally.
I
would
use
colon
z
right
here
to
make
sure
it
was
editable
by
the
user
inside
the
container.
However,
because
this
is
nfs
mounted,
if
I
do
the
golden
z,
it
won't
work.
B
So
I'm
going
to
leave
that
off.
Nice
then,
which
we
discovered
on
this
show
a
few
weeks
ago
and
now
we're
going
to
do
basically
the
same
thing
with
keys
and
then
we
need
a
data
container,
and
that
should
be
it
right.
I
think
yeah,
let's.
B
Took
too
long
all
right
so
now
I
should
have
a
container
running
called
data
container
and
it's
just
kind
of
sitting
there
in
the
background
serving
up
a
couple
of
volumes.
B
B
All
right
so
we're
gonna
copy
this
throw
pseudo
in
front
of
it
and
now
in
the
middle
here
somewhere
we
are
going
to
add
a
kind
of
an
unusual
flag
unless
you
use
data
containers
volumes
from
and
then
we
just
give
it
the
name
of
the
running
container,
so
oh
shoot
and
actually
running
it
is
running,
but
I
forgot
to
give
it
a
name.
So
it's.
B
B
All
right
so
now,
if
we
pseudo
pod
pod
man
ps,
we'll
see
that
it
actually
has
a
name
of
data
over
here
and
so
then,
let's
start
that
other
guy
yeah
I
screwed
up
my
copy
face
buffer.
So
we
will
just
copy
paste
it
again,
sudo
and
then
volume.
B
From
data
all
right,
so
now,
when
we
launch
this,
oh,
we
don't
want
to
run
it
with
an
I.
We
want
to
run
it
with
a
d,
so
I
is,
I
want
to
drop
into
the
container
d
is
run
it
in
the
background
right.
So
for
the
sake
of
this
conversation
about
pods,
which
we're
going
to
get
to
in
a
minute
we're
going
to
run
it
with
d.
B
B
And
let's
see
perfect
tools,
I
always
want
that
to
work
and
then
now.
B
B
I
can
touch
stuff
inside
the
inside
that
directory
right
and
I
can
actually
make
sure
it's
there.
You
know
if
you
have
any
experience
with
containers,
at
least
for
me.
This
is
like
one
of
the
constant
problems
I
have
is
like.
Did
I
actually
attach
the
the
directory
inside
the
container
correctly
to
be
able
to
actually
edit
it.
B
Terms
are
a
thing
exactly
all
right,
so
this
is
running
now.
My
temptation
here
is
to
type
exit.
However,
if
I
do
that
it
will
actually
kill
the
container,
so
we
don't
want
to
do
that.
So
we
can
do
and
you're
not
going
to
see
this,
but
there
is
a
command
combination
which
will
dump
you
out
of
the
container
without
actually
stopping
it,
which
is
control,
p
and
then
control
q.
B
B
B
B
B
B
Yeah
well,
I
had
my
first
test
on
the
states
when
I
was
a
senior
in
high
school
yeah,
which
I
thought
was
pretty
funny,
and
I
had
to
like
learn
them
for
that.
But
I
know
I
never
learned
the
capitals
either.
So
I
never
learned
to
type,
however-
and
I
still
don't
really
know
how
to
type,
I
know
how
to
type
a
lot
of
words
very
fast,
and
so
I
have
basically
a
vocabulary
of
words
that
I
can
type
well
and
otherwise
I
have
to
look
so
with
that.
B
That's
not
going
to
be
very
effective
that
we
can
share
the
content,
but
again
we
want
to
check
out
the
run
label
and
kind
of
do
it
by
hand
and
so
pink.
Oh,
my
gosh.
A
Narendra
was
like
oh
oh
now
I
get
why
people
make
geography
comedy
and
sitcoms
like
amer.
American
culture
is
very,
very
isolated
right.
Like
yes
insulated.
I
guess
right
like
we,
we
kind
of
put
ourselves
on
an
island
for
lack
of
a
better
term
culturally,
and
it's
not
necessarily
a
good
thing
in
my
opinion,
but.
B
Well,
also,
that
even
a
lot
of
americans
don't
realize
that
we're
way
more
similar
to
the
eu
than
we
are
to
like
anything
else,.
B
You
know
there
is
a
lot
of
independence
between
the
states
for
good
or
ill.
You
know,
and
so
things
like
education,
for
example,
are
state
managed.
On
the
flip
side,
we
have
things
like
where
texas
is
such
a
huge
part
of
the
population
that
the
texas
education
tends
to
dictate
the
textbooks
for
everywhere
else,
because
it's
cheaper
to
buy
the
textbooks
that
texas
created.
A
A
B
A
So
dota
2
attitude
gave
us
a
quiz,
where's
canada.
I
said
right
behind
me
because
technically
that's
true,
I'm
in
detroit
and
east
is
actually
right
behind
me.
So
and
then
someone
else
said
it's
right
next
to
alaska,
so
good
job,
everybody.
B
B
Now
I
can't
remember
the
name
of
it
though,
but
it's
it
might
be
a
john
candy
movie,
oh
even
so,
probably
nsfw,
but
you
know
it
is.
It
is
funny
okay,
so
I
got
rid
of
sport
tools.
Let
me
do
it
again,
except
with
a
d
all
right.
So
now
it's
running
in
the
background,
and
we
can
see
it
here
and
we
can
attach
to
it
just
like
we
did
before
or
for
the
other
guy,
the
other
one
that
I.
B
And
so
something
about
how
my
my
flags
are
set
is
making
it
so
that
I'm
getting
just
that
kind
of
blank
thing.
A
B
Right,
but
what
I
don't
understand
is
here
I'll
show
you,
if
I
attach
do
you
see
how
I'm
just
at
this
blinking
blank
blanket
yeah.
So
this
I
am
actually
in
a
place,
see
if
I
do
ls
like
like,
I
just
don't,
have
a
prompt
yet
which
I
think
is
really
confusing
for
people.
I
think
it's
because
when
I
start
it
detached
because
it's
cmd
and
not
entry
point,
it
doesn't
default
to
bash
and
then,
when
you
kind
of
run
a
command,
it
says.
A
Tillmore
says
canadian
bacon
starring
john
candy
was
the
movie,
that's
it
yes,
and
and
maybe
that
that
could
get
him
five
bonus
points.
I.
B
Exactly
and
I
do
like
canadian
bacon
I'm
kind
of
hungry,
it
is
breakfast
time
I
do
not
like
canadian
bacon.
No,
I
it
has
to
be
well
done
for
me
to
like
it,
but.
B
That
is,
bacon
is
an
interesting
cultural
difference.
I
don't.
A
And
the
fact
that
most
people
don't
eat
it
actually
well.
B
Yeah
yeah,
well,
all
kinds
of
you
know
religious
reasons
and
that
are
fundamentally
based
on
you
know
the
dangerousness
of
eating
pigs
back
in
the
day,
all
right,
so
we
are
going
to
drop
out
of
here
but
suffice
to
say
the
point
I
wanted
to
make
with
the
blinking
light
thing
there
was
that
usually,
if
you
just
hit
enter
a
couple
of
times,
it'll
drop
you
into
bash
and
work
fine.
B
So
if
you
see
that
try
that,
because
it
might
be
working
and
not
just
hanging
which
is
what
it
looks
like
it's
doing,
at
least
in
my
opinion,
all
right
so
long
story
short.
We
now
have
our
three
containers.
Oh
and
I
forgot
to
actually
point
out
what
I
wanted
to
show
here.
A
Cool,
oh
yeah,
dota
2
attitude
does
podman,
have
a
file
that
keeps
getting
bigger
and
bigger
until
you
eventually
prune
your
containers
or
delete.
I
said
yes,
your
image
door
will
grow,
there's
a
broom
command.
He
says:
okay,
it's
filled
with
a
machine
before
causes.
A
B
I
haven't
played
it
with
it
that
much,
but
it's
it's
pretty
comprehensive.
I
thought
it
was
clean,
oh
no,
maybe
a
system
and
then
clean,
but
you
can
actually
whack
like
yeah
so
reset
the
podman
storage
will
actually
like
whack
everything
that
it
knows
about.
A
Rmi
I'll
do
it
rmix
playing
risky,
says
in
chat,
which
is
an
amazing
screen
name
to
be
saying
that
yes,.
B
All
right
so,
but
maybe
that's
for
another
day,
but
the
point
is:
is
that
yeah
they're,
actually,
I
think,
even
more
sophisticated
than
docker's
ones.
But
again
I
don't
touch
docker
that
much
anymore,
so
it
could
be
that
it's
also
advanced,
and
I
just
don't
know
about
it.
So
now
we
have
our
various
containers.
B
We
can
see
the
subdirectories,
we
can
touch
the
subdirectories
or
touch
things
in
the
directories
and
then
apparently
I
forgot
to
take
a
zyrtec
this
morning
and
it's
I'm
noticing
that
you
are
like
coffee.
B
Yes,
yes,
apologies
for
that.
So
now
we
have
this
lovely
scenario
where
we
have
you
know
kind
of.
We
have
two
different
containers
that
are
able
to
talk
to
a
data
container
and
share
data
amongst
them.
We
have
that
layer
of
indirection.
If
we
want
to
move
it
around
problem
is
or
potentially
a
problem
is
that's
a
lot
of
commands
to
get
a
couple
of
things
to
work
right.
B
So
this
is
where
we
start
to
introduce
pods,
and
I
believe
I
don't
know
of
a
better
way
to
do
this,
but
I
think
I
need
to
kill
all
the
containers
I
am
running
so
far.
B
A
B
The
way
we
do
that
is
we
go
all
the
way
back
to
our.
Let's
see
if
I
can.
B
I'm
just
looking
for
a
scroll
back
to
make
it
a
little
easier
okay,
so
we
go
all
the
way
back
to
our
original
container
and
what
we
can
do
is
we
can
introduce
a
new
thing
here
called
pod,
and
we
can
do
this
one
of
two
ways:
we
can
either
tell
podman
to
create
a
new
pod,
the
let's
just
say,
sudo
pod
man
pod,
create
new
pod
like
this.
B
Name
yeah:
it's
certain
yep,
yeah,
stupid
consistency,
so,
okay!
So
now,
if
we
do
now
another
new
command
or
a
new
flag,
really
we
want
to
show
here
is
the
podman
ps
dash
p?
Oh
there's
no
containers
in
it,
though
so
it's
not
gonna
show,
so
we
can
say
podman
pod.
I
think
it's
list
yes.
B
So
now
we
created
this
new
pod,
which
has
no
containers
in
it,
except
there
is
actually
a
container
in
it,
and
this
this
I
don't.
I
may
go
file
a
bug
about
this.
I
don't
understand
why
this
command
doesn't
show
the
pause
container,
but
this
command
does
because
I
believe
this
container
is
actually
running,
so
it
should
appear
in
podman
ps
in
my
opinion,
so
I
may
go
file
a
bug
and
figure
out
why?
Why
that
doesn't
work.
B
Status
created
right,
so
I
mean
it
should
be
running,
but
long
story
short
whenever
you
make
a
pod-
and
this
is
true
of
kubernetes
and
openshift
and
podman
pods
right-
what
it
does
is.
It
creates
kind
of
like
a
little
enclosed
bubble
for
you
to
put
containers
in,
but
in
order
to
keep
that
enclosed
bubble
running
all
the
time
there
is
a
container
that's
inserted
into
it.
That's
called
a
pause
container,
which
essentially
is
a
very
very
small
container.
That
does
a
couple
things.
B
One
keeps
it
alive
and
then
also
kind
of
does
the
management
of
that
container,
so
it
does
like,
for
example,
network
routing
to
make
sure
that
stuff
coming
into
the
pod
goes
to
the
correct
container
inside
the
pod.
For
example,
chris.
B
A
So
I
have
the
illustrated
guide
children's
guide
to
kubernetes
here,
a
copy
of
it.
You
can
also
download
it
from
my
website
chrisshort.net
it's
on
there.
So
a
pod
represents
a
runnable
unit
of
work.
Usually
a
single
container
runs
inside
a
pod,
but
for
cases
where
a
few
containers
are
tightly
coupled,
you
may
opt
to
run
more
than
one
container.
B
A
So
the
actual
definition
of
a
pod
tells
you
that
it
could
be
one
or
more
containers
like
the
original
thought
was.
It
would
be
per
container.
But
the
idea
of
like
side
cars
and
having
multiple
containers
inside
of
a
pod
was
not
an
original
like
thought
of
the
kubernetes
creators
and
right
so
like
they
didn't
think
that
would
happen,
but
they
made
it
possible
which
it
was
an
interesting
design,
choice.
C
B
C
B
If
you
have
one
janky
little
machine
and
you're,
you
know
maria
db
and
your
hcpd
and
all
that
other
stuff
is
all
in
one
one
pod.
It's
all
going
to
be
on
that
one
janky
instance.
A
B
That's
exactly
yeah,
so
in
the
use
case
we're
talking
about
here,
though,
we
kind
of
want
a
monolith
with
the,
so
it's
a
little
bit
better
than
a
monolith
in
the
sense
that
it's
it's
separation
of
concerns.
Is
there,
but
not
separation
of
distribution
right.
So
so,
but
we
don't
actually
want
it
distributed
across
an
entire
environment.
We
want
it
all
in
one
place.
So
this
is
a
kind
of
a
special
case
which
a
lot
of
the
things
we've
been
talking
about
are
kind
of
a
special
case.
B
However,
it's
illustrative,
I
guess,
of
you,
know,
kind
of
what's
going
on
and
why
this
is
not
how
you'd
want
to
run
your
web
server,
but
it
might
be
how
you
want
to
run
your
kind
of
class
of
tool.
Containers
so
is
that
is
that
children's
guide
is
that
one
done
by
red
hat.
A
No,
this
one
was
originally
done
by
dyess
before
they
were
bought
by
microsoft,
and
it
is
a
open
source
project
designed
by
karen
chu,
matt
butcher
and
bailey
boger.
Well,.
A
B
And
I
believe
the
coloring
books
are
there.
I
think
so
too.
I
think
you're
right,
the
latest
one
being
one
about
k
native,
which
is
particularly
funny
story
of
dwarves
and
snow
white
right
or
snow
weight
in
the
seven
dwarfs,
roughly
all
right
so
back
to
our
regularly
scheduled
programming.
B
I'm
sorry!
So
exactly
so,
we
have
now
a
pod
that
has
a
pause
container
running
in
it
and
that's
great.
Who
cares
no.
B
What
I
call
it
a
new
pod
and
we
do
it
exactly
the
same
way
as
we
do
a
container
image,
there's
nothing
running
in
it
besides
the
pod
container,
so
I
don't
have
to
do
a
force
like
I
would
if
it
was
a
regular
one,
I'm
going
to
show
you
another
way
of
doing
the
creating
a
new
pod,
which
is,
you
can
say.
B
B
A
A
B
A
Exactly
if
you
want
to
scale
your
db
layer
horizontally,
all
you
have
to
do
is
add
another
pod.
All
right,
you
know,
and
essentially
that
pod
will
then
take
on
the
responsibility
of
communicating
with
all
the
databases
in
the
network
to
get
its.
You
know,
updated,
replicate,
replicated
replicant
data
and
it
will
all
then
join
and
you
will
have
horizontally
scaled,
so
the
ideal
state
is,
you
know,
your
database
lives
on
a
persistent
volume
group
somewhere
or
you
know,
and
you
have
a
connection
to
it
from
multiple
pods.
B
And
there's
a
thing
we
haven't
really
mentioned
yet,
which
is
that
there's
another
indirection
layer
that
you
can
have
between
pods
called
a
service
which
allows
you
to
have
those
things
talk
to
each
other
as
if
they
were
a
remote
service.
So
you
can
also,
then
also
not
tightly
couple
on
things
like
ports
and
stuff
like
that,
so
that
you
and
we'll
we'll
get
to
those,
probably
in
a
future
show.
But
basically
yes,
you.
B
B
I
would
say
a
classic
example
is
occasionally
or
depends
on
the
scenario,
but
sometimes
you
want
to
have
your
caching
server
scaling
with
your
web
server
so,
like
you
might
put
varnish
and
apache
in
the
same
pod,
for
example,
I
would
probably
really
question
your
your
motivation
and
your
decision
making
and
making
sure
that
that's
really
what
you
want
to
do,
but
there
are
arguments
sometimes
to
do
that,
so
another
thing
might
be
if
you
have
like,
oh
and
actually
to
moving
into
the
sidecar
conversation
which
was
mentioned
earlier
side
cars.
B
A
Right,
security
of
any
type
whatsoever:
right,
like
you,
have
those
like
what
is
it
gosh
we
partnered
with
a
few
of
them,
I'm
dropping
all
their
names.
A
All
those
security
folks
accurate
those
those
folks
like
if
you
need
to
run
like
something
in
your
pipeline
or
something
alongside
your
container,
to
ensure
it's
getting.
You
know
validated
code
that
it's
running
right
or
whatever
right
like
you
need
some
secondary
process
to
say
like
this
pod
is
valid.
You
could
run
that
right
beside
the
container,
that's
running
in
that
pod
right
there,
so
all
kinds
of
stuff
you
can
do
with
pods
that
you
can't
do
with
individual
containers.
B
Well,
and
so
well
especially,
I
mean
you
could
in
theory,
do
them
with
containers,
but
you'd
have
to
have
independent
processes
running
around
touching
those
containers.
What
the
pod
lets
you
do
is
put
all
of
those
things
into
their
own
containers
and
interact
with
the
thing
inside
the
pod
right
and
that.
A
Pod
could
then
be
isolated
or
you
could
have
multiple
pods
in
a
namespace
or
you
could
have
multiple
namespaces
interacting
with
each
other.
If
you
want
to
go
that
far,
I
mean
the
the
sky
is
the
limit
when
it
comes
to
cloud
infrastructure.
Folks,
I
mean
so
we're
we're
getting
into
the
ground
layer
here
with
containers
and
pods
right,
but
there's
a
big
world.
B
And
if
you
so,
if
you
have
a
computer
science
background,
the
terminology
for
this
in
computer
science
is
actually
cross-cutting
concerns
or
in
a
slightly
more
tactical
model,
something
called
aspect
programming.
So
if
you
have
any
familiarity
with
java,
does
this
and
they
call
it
aspects,
I
believe
in
the
latest:
rev
ruby.
Does
this?
B
Actually,
a
core
component
of
ruby
is
basically
cross-cutting
concerns
or
aspect
programming
which
in
ruby,
they
call
mix-ins,
but
the
idea
is
that
you
have
functionality
that
you
need
to
apply
to
all
the
different
parts
of
your
stack.
That
stack
may
be
every
method
in
a
in
a
software
system
or
that
stack
may
be
every
you
know,
process
that's
running
as
part
of
your
cloud
date
of
application.
B
So
a
cross-cutting
concern
is
our
common
examples.
Are
security,
error
handling?
Caching,
things
like
that
and
basically
what
you
want
to
do
is
you
want
to
decorate?
Actually
java
might
call
them
decorators.
Now
they
used
to
have
a
thing
called
aspect,
j
which
is
actually
incorporated
in
the
language,
but
I
think
it's
called
decorators
now
c-sharp
has
decorators.
B
What
you
do
is
that
decorator
says,
apply
this
functionality
to
this
method
or
class
every
time
a
sidecar
is
actually
the
same
concept,
but
at
a
slightly
larger
scale.
So
if
you
have
a
computer,
like
I
said,
if
you
have
a
computer
science
background,
if
you
go
back
to
cross-cutting
concerns,
that's
the
idea
of
sidecars
and
generally
speaking,
the
only
time
you
want
to
put
multiple
things
in
a
pod
is
because
you
want
to
have
decorators
on
the
thing
that
is
actually
in
the
pot.
B
A
B
B
As
I
often
advise
people
moving
into
kind
of
a
cloud
native
environment
from
an
existing
system
shoving,
all
of
the
stuff
into
one
pod,
for
example,
or
even
one
container
to
get
started,
still
gives
you
a
bunch
of
benefits,
and
then
you
can
pull
out
the
individual
services
as
you
go,
and
so
apache
and
squid,
you
know
doing
the
first
cut
of
like
kind
of
a
rough
cut
of
you
know.
Separating
services
generally
is
pretty
easy
and
a
good
idea,
because
we
have
well-known
protocols
for
communication
around
a
bunch
of
stuff.
B
B
So,
starting
with
that,
as
two
containers
or
two
pods
is
probably
a
good
idea,
but
eventually,
if
you're,
if
your
application
is
really
trying
to
scale
or
or
even
if
you
want
to
have
a
kind
of
a
minimum
amount
of
effort,
you
have
to
put
into
like
upgrades
and
things
like
that,
the
more
separation
of
services,
the
better
at
the
end
of
the
day,
you
know
the
reason
we
call
them
microservices
is
because
the
smaller
they
are
the
easier
they
are
to
operate
with.
A
B
B
Yes,
and
as
promised
narendev
has
had
a
nice
jump,
I
will
say
I
think,
there's
a
few
missing
points
in
here.
Still
that
I
need
to
go
back
and
add
in.
I
think
I
think
these
might
be
a
little
low
for
what
they
should
be,
but
you
know
you
will
see
that
update
next
time
I
just
might
have
missed
the
window,
but
first
place.
B
We
have
narendev
with
700
points
very
nice,
and
then
we
have
joe
fuzz
and
jay
walter
still
holding
and
I'm
a
little
disappointed
to
see
linux
expo
stacy.
His
seems
to
have
dropped
off.
A
B
B
Oh
okay,
all
right
as
well,
so
hopefully
she
will
be
back
so
you
know,
but
we
are
continuing.
I
will
say
there
are
still
some
dark
horses
out
there
and
you.
A
B
So
do
keep
that
in
mind.
You
know
you
may
not
be
in
the
lead
if
you're,
if
you're
not
sure
yet-
and
you
know
please
keep
collecting
those
internet
points
and.
B
Yeah-
and
I
will
drop
those
for
this
week
in
the
chat
and
there
they
are,
and
then
the
other
two
I
forgot
to
drop
in
earlier
are
the
discord
link
and
the
I
can
do
that.
I
got
them.
I
just
put
them
in.
I
forgot.
They
were
in
my
nice
little
text
pad
or
g
edit,
whatever,
whatever
this
tool
is
yeah.
B
Yeah
I
actually
used
my
job
days.
I
used
joplin
and
I
have
gotten
very,
very
good
at
note-taking,
but
when
it's
basically,
I
now
stu
stick
everything
in
there
and
it
always
saves
it.
It
does
a
really
nice
job.
It's
open
source,
it's
kind
of
like
an
open
source
evernote,
oh
okay,
it
lets
you
do
markdown
instead
of
evernote,
which
does
not,
or
at
least
didn't
used
to.
I
haven't
even
touched
it
a
year
or
two.
B
But
yeah
so
I've
gotten
much
much
better,
but
yes,
nano
nano
is
planned
to
be.
I
can't
remember
if
we,
I
think
it
got
finalized
is
going
to
be
the
default
editor
in
fedora
33.
Really,
yes,
so
you
don't
have
to
get
trapped
in
vi
anymore.
If
you
don't
have,
if
you
don't
know
what
you're
doing.
A
A
That
a
ton
in
the
90s
and
then
I
embraced
them
wholeheartedly
in
the
late
90s
and
haven't
looked
back
since
yeah.
Well
so
I
mean
I
use
vs
code
now
with
a
vim
extension
but
yeah.
So.
B
Yeah
yeah,
so
I
use
vs
code
for
for
the
big
stuff.
I
use
vi
for
quick
and
dirty
edits
and
I
use
emacs
for
for
longer
quick
and
dirty
edits
yeah,
so
I
kind
of
jump
across
them
all.
B
Well,
the
nice
thing
about
emacs
is
that
it?
Actually
it
actually
tells
you
when
there's
a
command
so
like
you,
can
always
go
and
find
the
command
really
easily
and
then,
as
soon
as
you
execute
it,
it
will
tell
you
the
keystroke.
So
if
you
do
it
enough
times,
you
start
to
memorize
the
keystrokes,
whereas
the
eye
you
have
to
like
print
a
manual
and
have
it
taped
up
around
the
room,
which
was
always
my
struggle,
yeah
all
right,
so
that
was.
B
All
right
so
going
back
to
our
tools:
pod,
okay,
so
now
we're
going
to
create
a
new
pod
with
our
data
container
inside
it
and
I'm
afraid
we're
going
to
run
out
of
time
on
this
episode.
But
that's
fine!
If
we
sudo
podman
psp
now
we
will
say:
hey.
We
just
have
the
data
container,
just
like
we
did
before,
except
it
is
now
in
a
pod
called
tools
pod
and
if
the
line
breaking
wasn't
so
weird,
it
would
look
a
little
better
but
whatever
so
there's
our
data
container.
B
B
All
right
so
we're
gonna
dump
a
support
tools
container
in
the
pod,
and
then
we
are
also
gonna.
Do
the
same
thing.
Let's
see,
there's
support
tools.
B
This
seems
like
a
lossy
effort,
but
I
promise
it's
still
shorter
than
me
typing
at
all
way.
Shorter.
B
So
pod
equals
tools
pod
and
now,
if
we
do
our,
let's
see
minus
there,
so
we
do
sudo,
podman
psp,
and
now
we
see
that
all
of
them
are
now
running
in
a
pod,
great
okay.
So
how
does
that
help
us?
Well,
it
doesn't
really
like
this,
so
what
we
can
do,
though,
is
the
next
step,
which
is
we
can
say,
pseudo
pod
man
generate
cube,
and
then
I
think
we
say
tools
pod
now
here
is
where
we
get
to
my
complaint
on
the
internet.
B
So
the
problem
is
there
is,
I
don't
want
to
say
a
bug,
but
there
is
a
feature
not
implemented
in
the
generate
for
cube
for
any
container.
That
is
privileged
and
I
did
some
experimentation.
It's
not
just
because
our
perfect
tools
container
does
a
lot
of
other
things.
It's
just
the
fact
that
it
has
this
privileged
flag
right
here.
B
B
That-
and
that
was
my
question
on
twitter,
which
was:
is
it
really
not
yet
implemented,
or
is
it
you
are
insane?
Don't
do
this
because
I'll
file
a
bug
if
it's
really
not
yet
implemented,
but
if
it's
you're
insane,
which
I
suspect
is
the
correct
answer-
I
understand
I'm
insane.
I
shouldn't
try
to
do
this,
so
that's
fine,
because
what
we
can
do
is
just
change
things
around
a
little
bit
and
not
use
the
privilege,
and
then
we
can
kind
of
continue
on
our
merry
way.
B
But
this
is
what
I
wanted
to
show.
You
is
that
if
you
use
the
privilege
flag
on
any
of
the
containers
that
you
put
in
the
pod,
it
won't
generate
the
qbml
and
why
we
want
the
qbmo
we'll
see
in
a
few
minutes.
What
would
be
nice
about
this
not
yet
implemented
would
be.
Is
it'd
be
nice
if
there
was
another.
B
B
I
was
going
to
focus
on
the
cube
one
for
today,
but
it
might
be
nice
if
we
had
a
way
to
generate
cube,
yaml
or
maybe
podman
yaml
for
lack
of
a
better
term,
so
something
I
could
run
later
with
podman,
but
wouldn't
necessarily
run
in
kubernetes
right.
If
that
makes
sense,.
B
So
and
kind
of
my
point
here
is
that
you
don't
actually
need
all
this
privilege
for
this
container
right
to
do
the
bulk
of
what
we
want
to
do.
So
the
fact
that
we
are
calling
it
with
the
privilege
flag
is
what's
causing
this
error,
but
we
can
sort
of
run
it
without
the
privilege
flag
right
and
it
will
still
do
most
of
what
we
want
right.
A
B
Right
right:
well,
the
question
is,
like
I
don't
know,
is
there
even
a
keyword
in
kubernetes
ymo
that
will
indicate
privileged
no
right,
so
that's
kind
of
I
was
like
I
can.
I
can
definitely
see
there
being
a
debate
about
how
to
approach
this,
and
you
will
get
this
not
yet
implemented
about
other
things
as
well.
Apparently,
volumes
used
to
be
a
problem
here,
but
that
was
fixed
in.
B
So
I
don't
know
what
else
but
long
story
short.
That's
what's
going
on
here.
B
Yeah
right
right
and
you
know
if,
if
people
have
thoughts
or
want
to
weigh
in
on
it,
I'm
sure
there
is
a
you
know.
You
can
always
go
file,
an
issue
on
podman
and
if
you
have
comments.
A
B
So
what
I
did
when
I
was
fooling
around
with
this
was
I
just
destroyed
the
whole
thing,
but
let's
see
if
we
can
just
kill
parts
and
see
if
it'll
still
work
rmf,
let's
do
support
tools
and
perfect
tools,
all
right
and
then
now
we
should
see
that
and
if
we
run
it
right
now,
it
should
just
work.
It
does,
but
not
very
interesting.
B
So
let
me
add
so
what
I
did
was
I
created
another
container
called
simpler
tools,
and
so
essentially
all
the
differences
here
is
that
it's
now,
inheriting
from
ubi8,
so
something
like
saucer
port
is
not
here
by
default
at
least,
and
it
would
take
a
bunch
of
investigation
to
figure
out
if
you
can
run
soft
support
without
I.
So
I
don't
think
you'd
be
able
to
run
like
a
sauce
report
without
a
privilege
because
it
never
requires.
B
Exactly
so,
but
that
doesn't
mean
you
can't
get
a
lot
of
the
tools
you
want.
You
know
ps
ip
utils
mtr.
You
know
I
just
kind
of
pick
some
at
random.
You
know
and
we
can
also
have
our
python,
so
we
can
actually
run
you
know.
Maybe
python
scripts
on
local
machines.
B
A
B
I
do
not
use
it
nano
I
find
it
is
slightly
too
unsophisticated
for
for
what
I
usually
need.
A
text
editor
for.
A
Like
the
explanation
of
lightsabers
to
luke
skywalker
in
a
new
hope,
an
elegant
weapon
for
a
better
time.
C
B
A
B
But
it
didn't
use
the
cash
for
the
first
one
either.
Oh
did
you
not?
Oh?
I
know
why
because-
and
I
can't
stop
it
because
I
did
a
pseudo
okay.
So
what
I
was
gonna
show.
That's
why
I
killed
the
whole
thing.
What
I
wanted
to
show
is
that,
if
we're
not
using
privileged,
we
don't
need
pseudo.
So
we
can
pseudo
podman
rm.
C
B
B
Okay,
so
what
I
wanted
to
show
is
that,
because
we're
not
using
privilege,
we
don't
have
to
use
pseudo
right,
and
the
reminder
to
me
was
that
the
simpler
tools
wouldn't
be
in
the
images
cache,
but
I
didn't
go
and
look
at
it.
So
I
forgot
so
what
we're
going
to
do
is
just
make
sure
that
our.
B
B
And
then
let's
call
this
simpler
flag
and
look
at
that.
It
used
the
cache
this
time.
A
B
And
this
was
actually
one
of
my
complaints
that
I
filed
an
issue,
for
it
was
actually
just
recently
closed
because
it
kind
of
went
off
on
its
merry
way.
B
But
one
of
the
things
I
dislike
about
how
podman
is
currently
implemented
is
that
if
I
have
exactly
the
same
container
image
right,
which
are
immutable,
mind
you
right
in
the
root
cache
and
in
my
user
cache
they
are
two
copies
right,
so
kind
of
wasting
space.
So
if
you
notice,
if
I
do
pseudo
podman
images,
I
have
this
list.
B
B
B
B
B
I'm
just
making
sure
I
didn't
miss
anything
else.
Okay,
so
now
we
have
a
data
container
and
if
we
say
pod
pod
man
psp,
we
see
we
have
a
tools
pod
that
has
a
data
container
in
it
and
again,
if
we
do
all
we'll
actually
see
that
it
has
a
pause
container
in
it
as
well.
Nice,
then,
if
we
add
our
simpler
tools,
but
without
all
the
flags
right.
C
B
So
we're
going
to
say
podman
run
tools,
pod
we're
going
to
run
in
the
background.
The
name
of
it
is
going
to
be
simpler
tools
and
then
here
we're
going
to
say
volumes
from
data
and
then
we're
going
to
get
rid
of
all
of
the
volume
mounts.
B
So
we
still
have
our
indirection
layer
and
then
that
should
give
us
a
new
another
container
and
then
so
now
we
have
our
three
containers
in
there.
If
we
attach
oops
yeah,
my
fingers
want
to
type
pseudo
now.
B
Data
yay
and
now
it's
owned
by
nobody,
everybody
loves
nobody
he's.
B
A
nice
guy,
hey,
I'm
just
assuming
this.
Nobody
is
a
he.
It
could
be
a
day.
I
suppose
it
could
be
nobody's.
Actually,
why
isn't
that?
It
is
for
nobody?
Why
is
the
group
for
nobody,
not
nobodies,
because
it
really,
you
know
that
would
be
funnier
consistency.
A
B
So
now
we
can
still
edit
inside
that
edit
inside
the
mounted
directory
and
so
awesome.
So
now
we
have
our
kind
of
simpler
tools
container.
It
has
a
lot
of
the
feature
set,
not
a
100
of
what
we
are
looking
for
in
our
perfect
tools
container,
but
it
allows
for
multiple
containers
to
work
together.
So
you
might
end
up
with
kind
of
two
different
scenarios
right.
You
might
end
up
with
your
podman
with
your
pod
kind
of
a
set
of
tools
or
whatever.
B
That
is
a
cluster
of
tools,
or
you
know
kind
of
the
single
perfect
tools,
container
kind
of,
depending
on
on
what
scenario
you
might
have.
But
what
we
want
to
do
now
is
we
want
to
take
a
look
at
what
happens
if
we
do.
C
B
All
right
so
cool,
so
now
we
actually
can
generate
the
pod
definition
from
this
pod
and
again
yay
like
so,
but
a
couple
things
I
want
to
point
out
before
we
move
on,
which
is
that
our
data
container,
which
I
want
to
see
where
I'm
trying
to
figure
out
where
it
starts,
I
hate
reading.
B
No,
that's
the
that's
the
other
one.
Isn't
it
well
just
look
for
the
word
volume
yeah,
so,
okay,
so
this.
So
this
is
our
data
container,
which
exposes
a
like.
Yes,
this
hard-coded
place,
which
is
editable
right.
It's
just
a
text
file,
but
it
exposes
as
this
to
the
other
container
in
the
pod
here
where
it
says
mount
mount
data
like
so
this
is
inside
the
container,
but
use
this
labeled
data
point
in
a
sense
so
that
we
have
that
layer
of
indirection.
So
it's
all
set
up
correctly
in
the
ammo.
B
Rmf
tools
pod,
so
now
we
can
do.
Let's
say
we
move
to
another
machine
right
and
we
just
took
this
yaml
file
along
and
we
had
those
images
available
from
our
centralized
registry.
Then
I
can
do
podman.
I
think
it's
just
play
right.
A
B
A
B
B
Quiet
weird,
apparently,
I
should
have
tried
this
out.
I
expected
this
to
just
work.
C
B
A
day
and
try
it
next
time.
B
B
So
we'll
definitely
investigate
that
and
come
back
to
next
time.
This
is
a.
B
For
next
time,
though,
for
sure
exactly
so
not
next
week
but
the
week
after
so
we
will
miss,
you
all
feel
free
to
watch
prior
episodes
during
that
time
slot
they
are
all
on
the
twitch
channel
chris.
Do
you
want
to
talk
about
any
shows
coming
up
this
week?.
A
So
there
is
the
series
premiere
of
what
did
we
call
it?
I
know.
A
Open
shift
administrator's
office
hours.
So,
if
you
like
our
developer
experience
office
hours,
that's
on
every
week,
every
tuesday
at
11am
eastern
time,
and
it's
with
serena
from
the
future,
we
will
have
the
openshift
admins
office
hours,
which
will
be
based
around
our
fellow
openshift
admins
that
are
running
and
maintaining
openshift,
not
just
putting
workloads
on
top
of
it
right.
So
there
is
a
kind
of
like
divide
between
using
openshift
and
maintaining
openshift
and
kubernetes.
A
So
that
is
where
we
bring
in
the
illustrious
andrew
sullivan
and
the
illustrious
it's
just
the
abbreviation
language.
Oh
the
illustrious
myself
and
some
folks
from
our
support
organization
that
will
help
us
help
you
kind
of
level
up
your
you
know:
openshift
skills
for
lack
of
a
better
term.
So
yeah.
We
look
forward
to
seeing
you
there
at
the
top
of
the
hour
wherever
you
are
but
11
a.m.
Eastern
1,
500
utc,
the
open
shift,
administrator's
office
hours
premiere
will
occur.
So
I'm
going
to
go.
A
Coffee
yeah
me
too,
all
right
thanks,
buddy.
I
appreciate
your
time.
Thank
you.
Everyone
in
chat
today,
thank
you
to
all
of
our
new
followers.
We
would
love
to
have
you
on
our
discord.
We
would
love
to
have
you
in
all
the
places
that
we
are
and
whenever
in
doubt,
tune
in
to
openshift
tv
for
all
the
latest
information
about
the
channel.
Thank
you
very
much.
We'll
see
you
soon.