►
Description
There is a lot of discussion around containers versus container orchestrators. For Red Hat Enterprise Linux, that container platform is Podman. Join us in this episode to discuss Podman and all things containers with a fun twist! We are going to deploy a gaming server, on-air!
Red Hat Livestreaming: https://red.ht/livestream
Get Started with RHEL: https://redhat.com/tryrhel
Eric The IT Guy Hendricks: Twitter @itguyeric
Brian Smith: Senior Product Manager
Scott McCarty: Senior Principal Product Manager (Twitter: @fatherlinux)
Focus areas include cloud, containers, workload expansion, and automation. Working closely with customers, partners, engineering teams, sales, marketing, other product teams, and even in the community, he combines personal experience with customer and partner feedback to enhance and tailor strategic capabilities in Red Hat Enterprise Linux.
A
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
red
hat
enterprise
linux
presents
this
is
episode
26,
building
a
home
gaming
server
using
podman.
So
I,
before
we
go
any
further,
let
me
bring
on
my
esteemed
co-host.
We
didn't
chase
him
off
last
time,
so
he's
he's
back
with
us
today,
hey
brian,
how
you
doing.
A
A
You
are
out
of
the
green
room,
much
to
my
much
against
my
instincts.
My
instincts
told
me
to
to
just
leave
you
back
there,
but
you
know
it
wouldn't
be
much
of
an
interview
if
we
left
you
in
the
green
room.
So
why
don't
you
introduce
yourself
tell
folks?
What's
what
you
do
here
at
red
hats
and
and
then
we'll
introduce
our
topic.
C
C
C
A
For
those
of
you
that
are
completely
lost
and
confused
clearly
you're,
not
children
of
the
80s
or
90s.
If
you
work
in
technology,
if
you
work
or
used
to
work
in
an
office,
office,
space
is
required
reading
to
to
be
able
to
continue
in
your
job
so
that
that's
our
free
public
service
announcement
for
for
this
episode
go
watch
office
space,
it's
I
I
watched
it
about
a
year
into
my
first
first
real
it
job
and
was
like.
I
think
they
filmed
this
in
our
office
because
we
have
all
of
these
people.
A
A
Just
for
you,
oh
good,
all
right.
So
today
I
I
wanted
to
we're.
In
december
we
just
came
back
from
from
thanksgiving
break,
so
I
I
wanted
to
do
something
a
little
bit
different
red
hat
enterprise.
Linux
is
near
and
dear
to
my
heart
and
has
been
for
for
a
couple
of
probably
about
15
years
or
so
now,
and
so
I
wanted
to
do.
I
wanted
to
talk
about
something
that
we
haven't
really
addressed
on
the
show,
but
I
also
wanted
to.
A
I
wanted
to
also
have
some
fun
with
it
we're
kind
of
towards
the
end
of
the
year.
So,
let's,
let's
do
something
fun.
So
why
not?
Why
not
talk
about
containers
from
a
home
network
perspective?
Why
not
talk
about
podman,
so
we
we
kind
of
iterated
on
this
a
little
bit
and
we
came
up
with
I
kind
of
want
to
relive
my
early
days
as
as
a
systems
administrator.
A
So
when,
when
I
bought
my
first
server
okay,
it
was,
it
was
a.
It
was
a
desktop
with
a
couple
of
extra
drives,
but
my
first
home
server.
It's
like
I
need
to
do
more.
Sys
admin
type
things.
I
can't
really
test
on
work
systems,
because
that
will
just
break
things
so
I'm
I
bought
my
own
system
set
it
up
at
home.
It's
like
okay,
great
now.
What
so
I
I,
a
friend
of
mine,
had
gotten
me
hooked
on
on
minecraft
and
so
those
two
worlds
kind
of
collided,
really
quick.
A
It
was
hey,
guess
what
you
can
actually
run
your
own
minecraft
server
and
it
runs
under
linux.
So
my
my
first
home
lab
project
was
to
spin
up
a
minecraft
server
here
at
home,
and
so
that's
that's,
that's
kind
of
been
the
that's
been
kind
of
my
hello
world
approach
to
any
time.
I
do
something
is
instead
of
getting
a
web
server.
It's
can.
A
I
run
minecraft
on
it
so
when
I
started
learning
docker
when
I
started
learning
docker
compose
and
then
when
I
moved
to
rel
eight
and
moved
to
podman,
it's
like
can
podman
run
doc
or
can
podman
run
minecraft
so
that
that
that
was
kind
of
that
was
kind
of
my
trip
down
memory
lane
so
scott.
I
wanted
to
ask
you
what
what
is
podman?
How
does
that
relate
to
docker
just
kind
of
give
us
the
the
basic
the
basic
overview.
C
Yeah
before
real
quick
before
I
do
that
I
was
gonna,
do
a
shout
out
to
I
believe
I
don't
know
how
to
say
your
name.
I
believe
it
is
chanting
but
we've
been
debating
on
twitter
about
whether
containers
even
matter
it's
been
actually
fun
but
but
so
yeah.
I
can
see
you,
but
sadly
I
can't
respond
in
the
text.
So
that's
why
I
had
to
do
this
verbally.
So
so
I
guess
you
have
to
create
an
account
before
you
can
respond
to
the
text.
A
So
you
can
actually
this
the
great
great
point
piece
of
housekeeping.
We
have
a
discord,
server
I'll,
get
the
invite
link
posted
into
the
chat.
You
can
also
join
us
on
twitch
or
on
youtube.
So
if
you
just
pull
up
this
video,
you
can
post
as
your
youtube
account
or,
if
you're,
a
twitch
person
you
can
respond
to
the
chat
in
in
in
twitch
chat
with
that
being
said,
as
we
go
through,
this
feel
free
to
post
your
questions
feel
free
to
to
to
interject
as
we
go
through
this.
C
C
How
do
they
agree
with
web
stuff?
No
so
good
segue
into
pod
man,
so
pod
man?
When
did
we
start
podman?
I
don't
know.
Four-Ish
years
ago
I
was
in
the
room
with
dan
walsh
and
matt
hicks,
and
we
were,
I
don't
know
we
were
red
hat
stuff,
which
usually
involves
like
giant
meetings
where,
like
everyone
starts
fighting
and
back
in
the
day,
the
old
school
red
hat,
where
like
we
were
just
like
getting
together
before
the
before
the
pandemic,
and
we
would
like
all
all
debate
vigorously
debate.
C
We
didn't
fight
per
se
like
we're
all
nice
to
each
other.
We
just
are
very
passionate
about
our
feelings
about
things
and
like
daniel
riek
and
dan
walsh
are
all
everyone
has.
You
have
to
get
loud
and,
and
we
were
like
well,
what
should
we
do?
Blah
blah
blah?
We
came
up
with
cryo.
We
came
up
with
the
idea
of
cryo,
which
was
essentially
we.
C
If
you
look
at
what
a
container
is,
it's
essentially
a
user
space
definition
of
a
bunch
of
tools
in
the
operating
system,
and
so
it's
like
you
fire
up
a
process,
but
here's
how
you
fire
it
up.
You
add
these
security
constraints.
You
mount
this
file
system,
but
here's
how
you
do
what
you
do
with
this
special
stuff.
C
All
in
one
thing
is:
there's
concepts
about
portability
and
what
they
meant
and
how
everything
should
pull
images
from
docker
hub,
and
there
was
this
it
was
at
the
end
of
the
day.
It
was
kind
of
there's
just
a
fundamental
difference.
The
way
we
looked
at
like
this
as
part
of
the
os,
and
they
looked
at
us
as
that
was
the
new
layer
that
you
should
like
program
to
and
so
long
story
short
we
looked
at.
C
How
could
we
build
something
that
we
thought
like,
for
example,
aligned
better
to
kubernetes,
and
so
we
built
cryo
and
so
cryo,
basically
versions
exactly
with
kubernetes?
It
has
the
exact
features
in
it
that
that
whatever
version
of
kubernetes
needs
so
like
with
kubernetes
117
came
out.
We
had
all
the
features
we
needed
in
cryo
to
manage
that
you
know
to
basically
work
perfectly
with
that
verse
and
we've
always
done
that
since
the
beginning,
I
think
we
started
maybe
1.10
ish,
all
the
way
to
like
1.21
or
wherever
we're
at
now.
C
The
the
dot
versions
of
kubernetes
have
become
less
exciting,
as
they've
gotten
larger,
and
so
I
don't
stay
as
up-to-date.
But
then
we
looked
at
okay,
so
we
looked
at
crowley
went.
Oh,
that's,
pretty
cool.
Even
before
that
we
had
looked
at
creating
a
utility
called
scopio
that
just
was
able
to
move
images
around.
C
It
was
a
very
simple
concept
where
you
could
just
like
move
container
images
around
from
like
one
registry
to
another,
and
the
idea
with
docker
is
you
had
to
you,
had
to
pull
to
the
local
stores
and
push
back
to
another
registry,
and
it
just
seemed
hokey
you're
like
why
can't
I
just
copy
from
that
registry
to
that
registry.
These
are
just
fancy
file
servers.
C
I
should
just
build
a
copy
from
here
to
here,
like
if
you're
in
unix,
you
can
just
you
know,
cp
or
rsync,
something
from
one
nfs
server
to
another
based
on
the
file
system.
You
know,
or
you
can
use
like
you
know,
what's
the
program
I
use
cl.
Oh
my
gosh,
I
forget
the
name
of
it,
but
there's
like
there's
this
one
that
I
use.
That's
cloud-based.
You
can
basically
copy
from
like
dropbox
to
pcloud
rclone.
Our
clone
is
freaking
awesome.
C
You
can
copy
from
anything
to
anything
and
there's
no
concept,
you
don't
have
to
pull
it
down
and
then
push
it
out.
You
just
copy
from
here
to
there
you
like,
so
we
we
looked
it
again.
We
just
viewed
it
as
like
unix
tools
and
then
eventually
we
had
built
scopio,
we
built
cryo
and
we
were
like.
We
need
something.
That's
like
instead
of
a
client
server
model
like
docker
is
where
you're
like
you
connect
to
it,
and
it's
a
server,
and
it's
very
like
web
2.0,
world-ish
thinking
like
web
services
and
all
this
magic.
C
We're
like
honestly,
the
old
school
stuff
here,
is
better
to
just
have
this
like
fork,
exec
model,
because
that's
what
the
server
the
docker
server
was
doing
anyway,
and
so
we
looked
at
it,
we
went
well,
let's
just
have,
let's
just
have
a
fork,
exec
model,
and
then
there
was
a
whole
bunch
of
work
going
on
in
this
community
called
rootless,
which
was
this
other
project.
That
was
these
technical
guys.
C
Akira,
I
think,
is
one
of
the
main
guys
and
there's
a
whole
bunch
of
other
people
are
working
on
this
concept
of
running
containers
as
a
regular
user
and
they're
working
on
weird
network
stacks
to
do
things,
and
we
were
like
oh
wow.
This
fork.
Exec
model
works
really
well
with
this
idea
of
running
it
as
a
regular
user,
and
so
then,
like
I
would
say,
that's
when
got
rid
of
the
demon,
ran
it
as
a
regular
user
and
pod
man.
A
C
So
by
default,
docker
runs
as
root
and,
like
I
mentioned
this
rootless
sort
of
experimentation,
I
call
it
like
almost
like
a
separate
project
was
some
stuff
that
was
going
on
on
the
side
that
there
were
people
looking
at
doing
rootless
stuff.
They
called
it
and
there's
even
a
rules.
Project
docker
looked
at
how
to
integrate
it
in
their
stuff
as
well,
but
the
the
problem
was
is
like,
if
you
run
a
demon
rootless
in
your
home
directory,
that's
still
like
hokey
right
like
it.
C
It
becomes
very
obvious
that
that's
hokey
when
you
run
it
in
your
home
director
you're
like
oh,
I
can
just
run.
I
have
62
users
on
this
system.
I'll
just
run
62
demons
all
running
as
these
different
people
and
that's
how
I'll
start
containers
like
that's.
That
falls
apart
really
quickly
on
like
on,
like
any
shared
user
system,
so
like
hpc,
that
falls
apart.
It
also
just
there's
this
thing
in
technology.
C
This
is
hard
to
explain
to
marketing
people,
but
you
just
know
when
stuff
is
right:
you're
like
it's
just
right,
it
feels
right
and
that's
what
you
want
like.
I
don't
want
a
demon
running
in
my
home
directory
so
like
historically
docker
just
had
a
single
demon
running
as
root,
and
that
was
great
again.
It
was
a
great
poc
like
it
was
a
proof
of
concept.
It
worked
great
you're
like
this
is
amazing.
We
put
the
proof
of
concept
in
production
all
over
the
place
as
root,
which
was
terrifying.
C
Just
how
technology
is
you
adopt
things
because
they're,
convenient
and
and
then
podman?
On
the
other
hand,
you
can
run
it
as
root
or
you
can
run
it
as
user.
It
doesn't
really
matter,
it's
just
a
utility.
It's
like
bash,
like
you,
can
run
bash
as
a
regular
user
or
as
root.
There's
no
reason
you
can't
do
that
and
I
call
pod
manage
just
bash
for
containers
like
it's.
Just
it's
got
a
slightly
different
interface.
You
don't
interact
with
it
like
bash,
you
don't
type
commands
on
it
or
in
it,
but
you
run.
C
B
C
Yeah
we
view
pod
man,
so
so
so
this
goes
back
to
an
article.
I
just
wrote
on
on
on
network
world
recently
where
I
talked
about
like.
Why
did
docker
change
the
world
so
like
docker
changed
the
world
because,
like
paz
was
so
I
go
back
to
like
2008
people
forget
this
history
and
I
get
always
frustrated.
Actually
I
was
I
was
joking.
This
is
again
I
was
I
was
debating
with
shen
shantanu
with
about
like
some
of
these
things.
C
I
just
seen
this
movie
time
and
time
again,
and
I
see
the
movie
over
and
over
again
like
these
debates
and
they're
just
patterns
so
like
it's
like
one
of
them
is,
is
you
know,
should
everybody's
been
saying
that
everything's
going
to
the
cloud
forever
and
and
certain
things
are
for
sure,
also
a
lot
of
server
workloads
are
going
to
the
cloud.
I
don't
disagree,
but
there's
still
a
huge
cad
ring,
like
95
percent
of
developers
like
to
run
things
locally
on
their
desktop
like
like.
C
What's
the
first
thing
you
do
if
you
go
to
learn
a
new
programming
language
like
I
fart
around,
I
like
bring
something
local,
and
I
like
I
want
to
like
do
my
inner
loop
development
locally
and
like
docker,
knows
that
the
company
docker
knows
that.
I
know
that
red
hat
knows
that
I
mean
a
lot
of
people
in
red
hat.
C
Know
that
although
there's
debates
in
red
hat
because
we're
a
big
company,
there
are
times
where,
like
vdi,
for
example,
makes
sense,
like
that's
the
same
debate
in
virtual
machines
right,
like
does
vdi
work
like
vdi,
is
really
elegant
for
certain
solutions,
but
it
still
feels
better
in
a
lot
of
scenarios
to
have
a
vm
locally
and
I'd
say.
The
argument
is
exactly
the
same.
With
like
kubernetes
versus
podman,
like
podman's
kind
of
thing,
you
run
locally,
it
works
really
well
in
a
development
environment.
C
We
have
a
pod
man
for
mac
working
pretty
well
today,
although
we've
had
some
bugs
and
things
but
but
the
the
is
elegant
like
this
is
one
of
the
hard
parts.
When
you're
like
early
in
code,
you
can
once
you
see
the
whole
thing
hanging
together
like
oh,
this
cathedral
will
be
beautiful
once
we
like
actually
get
all
the
glass
in
and
everything
but
like
the
glass
is
not
in
on
all
these
things.
C
I
have
a
big
honking
oracle
database
and,
like
a
web
app
and
you're
like
and
that
scenario,
I
don't
really
want
the
oracle
database
restarting
42
million
times,
and
I
and
I
just
want
to
be
able
to
like
fire
these
two
things
up
with
systemd
and
let
them
run
forever.
Just
like
I
did
with
processes,
but
I
want
to
use.
C
I
could
just
like
go
from
relay
to
rel
nine
and
just
like
update
the
app
and
swap
it
out,
and
you
know
the
data
is
all
the
same,
and
so
like
it
just
makes
upgrades
downgrades
rollbacks,
you
don't
have
to
do
things
at
2
am
anymore.
You
can
do
them
at.
You
know
4
p.m.
Before
you
go
home
and
you're
like
oh
that
just
worked,
if
not
I
just
roll
back,
I
don't
care
I've
actually
experienced
this.
C
C
I'm,
like
I
haven't,
touched
this
thing
in
a
long
time.
I'm
like
do.
I
really
want
to
mess
with
this
and
then
I'll
I'll
like
I'll,
like
top
type
pod
man
build.
I
even
have
some
scripts
to
like
rebuild
them.
I'll
just
run
the
script,
I'm
like
okay,
that
all
worked,
I'm
like,
let's
restart
and
see
what
happens
and
it
works.
I'm
like.
Oh
that's
awesome
like
it's
so
much
better
than
like
when
you
would
have
to
like
back
up
all
the
data
and
you're
like.
C
Oh,
let
me
back
this
up
and
do
all
this
crap
and
fart
around
and
like
and
then
like
try
to
upgrade
and
break
halfway
and
you're
fighting
around
now.
If
it
breaks
I'm
like
I'll
just
mess
with
her
later,
I
can
do
the
rebuild
later,
because
it's
just
a
container,
and
so
I
don't
have
to
run
the
new
version
of
the
image.
I'd
say
those
are
that
that
single
node
server
use
case
and
that
desktop
you
know,
mac
windows,
linux
use
case
are
probably
the
two
biggest
places.
C
I
think
podman's
awesome,
because
you
can
like
say
you're
running
openshift
in
production.
You
can
bring
that
kubernetes
gmo
back
from
prod
run.
It
dev,
you
know,
run
the
whole
app
it'll
fire
up
three
four
five
containers:
whatever
it
takes
to
build
the
app
change,
your
little
part
test
it
locally,
do
the
commit,
let
it
go
through:
ci,
cd,
roll
it
out
and
prod,
and
it
works
back
on
kubernetes
and
prod,
and
when
you
have
a
scale
problem,
absolutely
kubernetes
is
the
most
elegant
tool
to
do
that.
C
A
C
I'm
not
sure
where
we're
at
with
m1
support.
I
I
think
we're
very
close,
like
I
don't
know
right
off
the
bat
I
know
a
few
weeks
ago
we
were
saying
it
was
only
a
week
away
and,
like
we've
been
we've
been
dilly,
dowling
figuring
out.
Basically,
what
was
happening
was
dependency
problem.
There's
we're
using
like
I
forget
what
they're
using
libvard
or
I
forget
what
they're
using
behind
the
scenes.
C
But
but
there
was
some
patch
they
had
to
make
and
then
had
to
get
into
brew
and
then,
like
so
there's
like
dependency
chain
problem,
where
it's
just
blocked,
there's
an
actual
patch
and
this
works
and
we've
done
it
on
like
m1
max
and
we've
got
it
working
locally.
We
just
don't
have
the
public
version
working
all
the
way,
yet
I
don't
think
it
may
actually
be
working,
but
I
think
I
would
have
heard
somebody
squealing
about
it,
but
ashley
and
our
team
worked
on
she's
got
really
elegant,
like
it
works
really.
C
Well,
we
just
got
to
get
the
patches
out
there
in
brew.
Basically,
and
then
that
highlights
something
longer
term,
I
think
brew
might
not
be
the
answer
for
the
red
hat
way
of
doing
it.
We
just
want
it
in
brew
today
because
it's
a
very
fast
inner
loop,
iteration
process
compared
to
like
download
this
thing
from
redhat.com,
but
I
am
very
much
investigating
like
what
is
the
download
this
thing
from
redhat.com.
C
So,
like
you,
ssl
connect
to
redhat.com
download
a
thing
install
it
on
your
mac
and
the
same
process
happens
where
you
do
a
podman
machine
in
it
machine
start,
but
it's
probably
rel
bits
and
it's
you
know
sanctioned
from
red
hat
and
you
go
from
this
entity
and
you
transfer
it
to
you
and
it's
just
those
two
entities.
Instead
of
like
going
messing,
we've
had
some
customers
say
like
we
can't
download
stuff
out
of
brew,
that's
crazy
talk
and
I'm
like.
Okay,
that's
fair.
B
C
C
A
A
C
C
But
bottom
line
is
we
support
the
podman
socket
api
so
like,
if
there's
a
tool
that
talks
to
this
podman
socket
api
and
and
it
breaks
the
api
breaks
in
some
way
to
where
the
docker
compatibility
doesn't
work.
We
pretty
much
consider
that
a
bug
and
we
try
to
fix
it.
So
that's
the
first
layer
that
you
need
to
think
about.
I
was
like
okay,
so
when
you
run
pot,
basically
podman
has
a
system
sub
command
and
you
can
basically
fire
up
a
socket
there's
like
a
socket
and
you
run
it
as
a
service.
C
Now
you
can
run
this
as
root
or
as
non-route.
Just
like
I
mentioned,
you
can
run
a
demon
in
your
home
directory.
If
you
want,
systemd
can
actually
do
this
again,
it's
not
the
most
elegant.
I
don't
like
it,
but
it's
what
you
got
to
do
to
be
docker
compatible
if
there's
a
tool,
that's
looking
for
an
api,
so
you've
got
to
have
an
api
socket.
So
we
support
that.
The
next
layer
up,
though,
is
people
go,
oh
was
podman,
is
docker,
combo
support
and
I
go
well.
C
C
So
that's
the
next
stop
on
the
dewey
support,
docker
compose
train
and
then
the
next
stop
is
like
okay.
Well,
there's
this
other
thing
called
podman
compose.
What
is
that
and
we
go?
Is
it
supported
in
rel?
No,
not
really
we
don't
support
it.
You'd
have
to
go
get
this
utility
yourself.
This
works
it's
tested
upstream.
C
It's
part
of
the
containers
project.
This.
This
team
really
works
hard
to
make
it
compatible
with
pod
man.
What
it
does
is
it
actually
uses
the
podman
cli,
so
you
don't
have
to
have
a
demon
running
so
there's
some
advantage
there.
It
has
some
other
things
where
it
can
do
some
speed,
work
and
copy
things
and
do
some
things
because
there's
no
socket
so
it
doesn't
have
to
copy
data
up
through
a
pipeline.
It
just
does
fork
exec,
so
it
has
direct
access
to
data.
So
there's
some
there's
some
pluses
and
minuses.
C
It
may
have
some
compatibility
issues
with
docker
compose
a
little
bit,
but
it
works
mostly
with
compose
it's
an
interesting
project
but
again
skip
it
as
part
of
rel,
because
we
don't
really
sanction
it
as
the
thing
to
do.
We
kind
of
like
really
think
this
is
probably
the
long-term
solution,
but
we
still
want
to
unblock
this.
So
if
you
want
to
bring
your
own
podman
compose
and
it
works
with
your
composed
files,
great
the
next
level
is
like
docker
compose
1.0,
which
is
a
python
script.
We
go
yeah
that
works,
we
test
it.
C
We
actually
test
it
upstream.
It's
part
of
our
ci
cd.
We
make
sure
that
this
works.
If
you
bring
your
own
docker
compose
one,
it
should
work
if
it
doesn't
work,
we're
pretty
much
going
to
consider
it
a
bug,
because
it's
probably
a
bug
between
the
docker
compose.
If
it's
a
bug
in
the
socket
api,
because
something's
changed
in
docker
bows
and
then
it
breaks
something
we'll
fix
it.
If
it's
a
problem
in
docker
compose,
obviously
you're
on
your
own
you'd
have
to
go
figure
that
out,
but
it's
an
upstream
project.
C
C
We
won't
need,
build
kit
or
or
any
of
that
stuff
to
make
this
work
it'll
just
work
built
into
pod
man,
because
because
pod
man
vendors
in
build-
and
so
it
can
do
everything
builder
can
do
so.
We
see
a
path
to
making
this
work,
adding
it
to
our
ci
cd
and
making
it
work,
but
it
doesn't
work
now
warning
these
three
options
are
not
support
on
rel,
but
they'll
probably
work
and
we
test
them
and
if
it's
a
problem
with
the
socket
api,
then
we'll
fix
it.
C
B
C
Yeah,
so,
first
off,
let
me
show
you
what
pod
man
on
podman
is:
let's
go
out
here
to
red
hat
universal
base
image.
Here
I
can.
I
can
make
my
screen
bigger
for
eric,
since
he
thinks
he's
older
than
me,
even
though
he's
not
and
let's
go
to
components
and
you'll
see,
so
this
is
right.
Universal
base
image.
This
is
I
mean
this
is
basically
our
freely
redistributable
container
image
toolkit.
If
you
will
it's
a
whole
bunch
of
things,
it's
a
bunch
of
different
container
images.
C
C
If
you
want
and
it's
its
own
version
so
like
you
can
see
here,
this
is
like
the
dockerfile
or
container
file
that
builds
it
and
it
does
like
you
know,
does
some
magic
in
here
to
make
it
easier
to
make
them
run
better,
but
at
the
end
of
the
day,
basically,
what
it
is
is
dnf
install
and
it
basically
installs.
You
know
podman
and
c
run
and
some
other
things
makes
this
work
inside
of
a
container.
C
So
the
idea
here
is
that,
like
okay
there's
times,
I
want
to
use
podman
because
it
has
some
cool
feature.
I
want
to
run
it
on
some
ci
cd
system
somewhere,
but
the
ci
cd
system
only
supports
docker
you're
like
well
no
problem,
you
just
run
podman
in
docker,
sometimes
you're
like
oh.
I
want
to
do
some
cool
thing
with
podman.
It
does
some
weird
stuff.
I
need
cool,
you
can
run
it
in
kubernetes,
so
you
can
run
podman
in
kubernetes
as
a
container
inside
of
kubernetes.
C
Another
scenario
that
I
see
is
people
are
like.
Oh,
I
have
this
old
version
of
pod
manor
docker.
We
can't
change
because
of
blah
blah
blah
it's
corporate
standards,
whatever
reason
we're
stuck
we're
using
an
old
we're
using
rel7
and
we
need
podman,
3.4
or
podman
3.3.1
and
you're
like
well.
That's
not
going
to
happen
because
we're
not
going
to
update
roll
seven
but
rel
state
container
images
are
supported
on
rel7.
C
So
now
you
can
just
run
podman
in
a
container
on
rel7
and
get
access
to
the
latest
pod
man
and
it
works
those
kinds
of
scenarios.
Basically
I'd,
say
podman
on
podman
unlocks
all
these
like
edge
cases
that
are
just
really
irritating
and
you're
like
you're
like
I
just
want
access
to
the
latest
one.
I
want
it
to
work,
or
maybe
the
newer
version
breaks
something
and
you're
like.
I
just
need
to
use
the
older
version,
but
we
have
the
newer
version
installed
on
the
host.
C
You
can
just
like
run
the
older
version,
so
it
kind
of
like
it's
time
and
space.
It
unlocks
you
like
that's
kind
of
the
magic
of
containers
and
so
running,
podman
in
podman,
unlocks
time
and
space
between
the
different
versions
of
podman
and
or
docker
and
or
kubernetes,
and
you
can
basically
run
potman
in
that,
and
so
uvi
makes
this
completely
freely
distributable
and
usable.
However,
you
want
so,
you
can
go
use
the
ubi
version
of
podman.
You
can
run
it
in
cirrus,
ci
or
whatever
online
ci
cd
provider.
C
In
gory
details,
so
if
you
really
want
to
understand,
what's
going
on
when
you
run
a
container
in
a
container
and
when
you
need
privilege
and
how
you
need
privilege,
I
would
recommend
checking
out
this
article
and
then
one
other
thing
a
root.
I
call
it
root
inside
and
outside
the
container.
This
is
another
one.
C
I
would
recommend
if
you
need
to
understand
like
what
is
going
on
in
podman
and
podman
and
when
you
use
a
root
inside
out,
or
you
know,
inside
or
outside
the
container,
and
when
you
use
a
user
inside
and
outside
the
container.
I
think
these
are.
These
are
good
articles,
so
I'd
recommend
this
little
table
is
like
a
cheat
sheet
for
your,
like.
Oh
I'm
root
outside
in
there,
and
then
I
run
podman
I'm
inside
and
then
it
gets
inception.
C
I
could
like
create
like
a
whole
tool
of
this,
of
like
running
route
outside
the
container
running
route
inside
the
container,
then
running
pot
in
as
root
inside
the
guitar,
which
runs
another
container,
has
non-root
and,
like
you
can
get
his
inception
level
deep
as
you
want.
I
probably
need
to
create
the
next
version
of
this
table,
which
makes
your
brain
hurt.
B
A
B
C
Yeah,
that
is,
that
is
freaking
awesome.
I
forgot
to
I
forgot
to
bring
that
up
yeah.
I
remember
when
you
created
that-
and
I
saw
that
I
was
like
oh,
I
was
like
this
is.
I
am
not
as
good
at
videos
as
you
I'm
like
hardcore
blogger,
like
I'm,
a
I'm
gen
x
old
school.
Like
I
just
write
blogs,
I
need
other
people
to
do
cool
videos
like
you,
because
I
just
don't
make
as
good
of
videos.
A
A
But
I
told
him
before
we
brought
him
on
the
show.
I
told
him
there's
a
catch.
We
spend
the
first
30
minutes
talking
about
talking
about
the
topic,
but
then
you
got
to
put
your
money
where
your
mouth
is
and
I
sent
a
challenge
your
way.
So,
let's,
let's
pull
up
the
terminal
and
and
let's
let's
see
this
stuff
in
action.
C
C
So
I
just
added
some
dns
for
this
guy
and
we're
out
here
and
if
you
look,
this
is
like
a
rel,
eight
server,
it
has
podman
3.3.1
and
we
were
like
okay.
So
now
we
have
an
ip
address.
We
have
a
rel
server,
we
have
pod
man,
and
this
is
where
I
get
off
in
uncharted
territory.
I'm
like
I
don't
I
don't
even
understand
mine.
I
mean
I
understand
mine,
like
I
don't
understand
why
people
play
it
like.
I
understand.
I
understand
why
I
actually
I
don't
understand
all
no,
I
I
joke.
C
I
get
it
it's,
but
we're
gonna
try
to
run
it
now,
and
I've
never
tried
to
run
it.
Definitely
not
in
rel,
definitely
not
with
pod
man,
and
I
I
went
out
and
I
started
looking
at
this
kind
of
this
tutorial
and
I
was
like
okay,
okay,
I
like
blogs,
and
this
guy
seems
per
this
guy
or
gal
seems
pretty
dialed
in
this
looks
like
a
very.
This
looks
like
a
pretty
impressive
script
here.
That,
like
seems
like,
I,
wouldn't
want
to
run
this
on
like
mudbox.
C
C
Oh
yeah
yeah
here,
let
me
zoom
in
on
this.
Yes,
so
so
this
blog
is.
Apparently
this
guy
figured
out
how
to
run
minecraft
in
pod
man
and
they
blo
he
blogged
about
it
back
in
2019,
so
now
we're
in
2021
so
we're
what
two
years
later
this
guy
james
young,
is
awesome.
He
got
this
to
work
like
two
years
ago,
and
so
apparently
you
like
that
the
you
know
blah
some
max
min
max
ram.
C
Some
tz
stuff
looks
like
you
might
be
in
australia,
because
I
saw
down
here
in
this
in
this
looks
like
it
might
be,
setting
australia
tz
data,
that's
terrifying!
Let's
see!
If
that
breaks
on
our
system.
I
don't
know
what
will
happen,
and
I
don't
know
I
don't
know
what
all
these
things
are,
but
so
I
was
thinking.
Let's
try
to
run
this
and
then
let's
see
if
it
breaks
or
runs
and
then
let's
try
to
fix
it.
If
it
doesn't,
work
is
kind
of
what
I'm
thinking.
C
C
C
A
Well,
like,
like
all
technology
answers,
it
depends.
Do
you
want
to
be
able
to
moderate
your
your
minecraft
server?
Do
you
want
to
give
certain
friends
like
moderator
privileges
and
give
yourself
like
admin
privileges,
because
there's
nothing
worse
than
giving
a
friend
of
yours
admin,
privileges,
building
this
beautiful
castle
out
in
the
middle
of
nowhere,
and
then
your
friend
coming
in
and
and
setting
creative
mode
and
deleting
your
castle
essentially
just.
C
That's
what
I
think
they're
being
funny
yeah.
This
is
like
basically
like
somebody
could
screw
up
your
your
like
lego
castle
like
and
you're
like
I
don't
want
that
yeah,
I
don't
know.
I
was
just
analyzing
this
a
little
bit
before
I
run
it,
but
now
we'll
let's
try
and
run
it.
This
thing
looks
interesting.
I
don't
know
what
this
is.
This
looks
like
it
might
be
pulling
in
some
kind
of
data,
like
the
version
of
the.
C
So
I
thought
this
was
interesting.
Let's
see
what
happens,
let's
run
this,
let's
get
brave,
what
can
we
break
right?
I
mean
I
can
just
delete
this
thing.
So,
oh
I
I
lied
a
little
bit.
I
did
try
to
run
it
once
and
so
it
so
it.
Let's
do
this
podman
images.
It
apparently
did
pull
this
image
down
and
then
that's
like
a
gig
a
little
under
gigabyte.
C
C
C
A
C
C
A
C
C
C
C
C
C
Oh,
oh,
that's
right,
actually,
pod
man.
So
what
what
did
it
say
is
that
it
names
the
container
when
it
fires
up,
and
so
basically
we
just
gotta
kill
that
so
we'll
do
a
pod.
Man
kill
dash
a
and
we'll
do
a
pod
man
rm
dash
a
this
is
kills
and
everything
and
then
we'll
run
this
again
and
it'll
start
from
scratch.
C
C
A
C
A
C
C
A
C
B
B
C
B
A
C
A
C
C
You
out
here
I
know:
oh
well,
we
tried
now
it
doesn't
matter
because
I
didn't
like
this
anyway,
so
I
guess
I
can
talk
about
what
I
didn't
like
about
this
anyway.
I
didn't
like
that.
This
is
running
whatever
this.
I
believe,
where
is
it
at
from
podman
run?
So
this
all
the
way
down
here
this
itzg
minecraft
server
latest.
I
think
it's
built
on
some
kind
of
debian
distribution
and
I
was
like
to
make
me
happy.
I
would
need
to
build
this
on
ubi
and
or
fedora,
and
then
I
would
be
happy
there.
C
A
B
C
C
C
C
C
A
C
C
A
C
C
A
C
A
C
B
A
C
A
So
this
this
does,
although
this
blew
up
in
our
faces,
maybe
next
time
we'll
actually
try
it
before
we
go
live,
but
this
makes
me
think
that
that
I'm
sorry
go
ahead
and
if
you
could
repost
that
vm
question,
I
must
have
missed
it
there
somewhere,
but
one
of
the
things
I
was
thinking
of
was
red.
Hat
actually
has
16
licenses
for
role.
Instances
and
different
people
have
virtual
machines
running
on
their
laptops.
Some
people
have
home
labs.
Some
people
spend
a
lot
of
time
on
linux
or
or
aws
or
digitalocean.
A
Whatever
the
case
may
be,
it
might
be
good
to
do
like
a
mini
series.
I
know
I've
already
committed
to
a
satellite
one
next
year,
but
it
might
be
good
to
do
some.
What
are
some
good
things
to
do
with
those
16
subscriptions
and
I
think
a
minecraft
server
would
be
a
great
one,
maybe
we'll
actually
maybe
we'll
actually
go
in
and
make
sure
it
works
before
we
bring
it
on
air
next
time,
but
it
might
be
cool.
A
So
if,
if
you
got
to
twitter
red
hat
rel
is
our
is
our
handle
real
presents,
it
would
be
great
if
you
just
share
your
ideas.
Tell
us
some
things
that
you'd
like
to
run
in
your
home
lab
and
with
the
last
few
seconds
I
do
want
to
share
with.
I
do
want
to
share
the
question
that
we
that
we
missed,
and
that
was
where's
the
podman
machine,
create
the
create
the
vm.
A
C
I
think
they
had
to
do
some
patches
of
live
vert
to
make
the
m1
work
and
the
live.
Vert
stuff
is
what
they're
waiting
they
were
waiting
to
patch
it
up.
They
patched
it
upstream,
but
they
were
waiting
to
pull
it
into.
They
were
gonna.
Do
some
one-off
fork
patches
in
excuse
me
in
brew
to
like
get
us
through
until
they
patch
it
upstream
and
then
pull
the
latest
version,
blah
blah
blah?
I
think
that
was
the
problem.
If
I
remember
right,
it
could
have
been
another.
B
A
A
A
A
Have
you
seen
my
stapler
all
right
y'all
before
this
deteriorates
any
further,
I'm
going
to
call
it
a
day.
Join
us
in
in
two
weeks
for
rel
fireside
chat,
that'll
be
the
last
rel
presents
of
the
year
brian.
Thank
you
so
much
my
co-host
scott.
Our
guest
today
follow
him
on
twitter
at
father,
linux.
Of
course
I
am
eric
the
it
guy
hendrix.
So
join
me
on
twitter
mastodon,
all
the
things
at
itguy
eric
and
until
then,
we'll
see
in
two
weeks.