►
From YouTube: The Level Up Hour (E29): Docker Compose with Podman v3!
Description
Podman v3 is out and has a bunch of great new features. One in particular, that we know the TLUH audience will appreciate, is the ability to run docker-compose files. Come join us to discuss all the new things with Brent Baude, lead developer, and @umohnani8, KubeCon Keynoter.
Learn more at https://red.ht/leveluphour
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
healing
from
welcome
to
another
edition
of
the
lola
power
here
on
openshift
tv,
I
am
chris
short
executive
producer
of
open
shift
tv.
I
speak
so
quick.
Sometimes
I
don't
even
realize
what
words
I'm
saying,
because
I'm
so
used
to
this
langdon.
How
are
you
doing
this
morning?
Buddy,
yes,.
B
B
So
brent
bowdy
is
here
with
us
today
to
talk
about
kind
of
what's
new
in
podman
v3
and
I
I
have
applied
the
title
architect
to
him
for
the
project,
but
I
completely
made
that
up.
So
we'll
also
ask
him
what
his
actual
title
is
on
the
on
the
project
and
we'll
go
through
a
bunch
of
different
stuff
brent.
You
want
to
give
a
quick
introduction
yourself
and
then
we'll
kind
of
introduce
the
show
a
little
more.
C
B
Know
you
gotta
get
the
jokes
in,
let's
see
have
I
been
to
michigan,
I
think
I
have
been
to
michigan.
Oh
no,
I'm
sorry.
I've
definitely
been
to
detroit
and
michigan.
I
was
gonna,
say
minnesota.
I
think
I've
been
to
minnesota,
but
I'm
trying
to
hit
that
all
50
states
one
of
these
days,
but
mostly
it
doesn't
count
as
far
as
I'm
concerned.
B
B
That's
what
we're
doing
here
today
and
this
show
is
about
trying
to
figure
out
why
containers
are
interesting
and
how
they
might
be
interesting
to
you,
especially
as
like
a
rel
admin
say,
and
you
want
to
you,
you
hear
all
this
buzz
or
whatever
around
containers.
You
know
you
got
to
learn
about
them
someday.
So
that's.
B
B
B
B
Orchestration
models
is
been.
This
thing's
been
floating
around
for
a
bunch
of
years.
I
don't
even
think
it
was
developed
by
docker
called
docker
compose
and
it's
super
useful.
You
can
kind
of
say
I
want
a
little
web
server
and
I
want
a
database
server
and
blah
blah,
and
then
you
can
just
describe
all
the
pieces.
You
need
and
say,
go
and
up
comes
all
those
containers,
and
so
recently
in
podband
v3
podman
has
grown
support
for
being
able
to
read
those
same
files.
C
Yeah,
I
think
it's
important
to
also
look
at
to
look
at
how
we
kind
of
got
here.
The
decision
to
support
compose
was
not
taken
lightly.
It
was
something
we
had
debated,
probably
for
a
year
and
a
half
oh
wow
before
before
even
deciding
to
say:
okay,
let's
do
it
wow,
and
so
we,
yes
and
and
that's
because
of
the
of
the
beliefs
around
the
orchestration
model,
which
we,
which
I
think
we'll
probably
get
to
a
little
bit
later.
C
You
100
believe
that
is
the
case
or
not.
That's
that's
the
argument
and
it's
reasonable.
So
so
last
fall
when
we
had
our
well,
it
was
even
longer
ago,
but
we
decided
okay,
we
gotta
do
this.
We
gotta
get
compose
in
because
we
don't.
We
want
to
eliminate
all
the
rat
for
lack
of
a
better
word
excuses
that
that
prevent.
C
B
Right
right,
actually,
I
had
a
question
come
up
on
twitter
literally.
I
think
yesterday
that
someone
was
asking
is
like.
When
will
podman
v3
be
available
for
rel
eight,
and
I
was
like
don't
know,
but
I
I
said
I
would
ask,
and
they
brought
up
the
great
point
of
hey.
It
could
be
in
an
app
stream,
and
I
was
like
oh
yeah.
I
I
like
those
I
was
very
involved
in
making
those
happen
so
is,
is
there
is
podman
v3
released
already
for
rel?
B
C
B
B
A
B
C
C
B
C
That's
the
apples
to
apples
comparison
right
functionally
one
of
the
areas
always
is
going
between
podband
and
docker,
regardless
of
compose,
is
always
going
to
be
swarm.
We
don't
do
swarm,
we'll,
never
do
swarm.
Okay
right,
that's
not
the
way
we
went.
So
if
your
compose
file
dips
into
that
water,
which
I
don't
see
a
lot
of
yeah,
then
we
can't.
We
can't
digest
that.
Well,
we
can
digest
it.
We
can't
run
it
right
right.
Otherwise
it
should
it
should
all
work.
If
it
doesn't,
it's
likely
a
bug
and
as.
B
Actually-
and
I
mean
it
stands
to
reason
right,
I
mean
I've.
I've
seen
swarm
like
next
to
nothing.
You
know,
swarms
addition
to
docker
compose
was
was
really
far
into
the
you
know
the
docker
composed
like
lifespan.
So
I'm
not
I'm
not
all
that
surprised.
I
am
curious.
How
is
oh
go
ahead?
Sorry
I
was,
I
was
going
to
say
one.
C
Other
thing
there
has
been
some
confusion
with
early
with
folks
that
don't
have
a
straight
vision
for
this.
Let's
say
there
has
been
confusion
on
their
thinking
that
somehow
our
podman
can
interact
with
the
doctor
stores,
like
the
doctor's
container,
run
time
where
the
containers
are
running
or
their
image
stores.
That's
not
the
case.
It's
it's
a
gamo
file.
C
Let's
get
fed
into
podman,
it's
100
isolated
from
docker
right,
except
that
you
run
docker
compose
under
pseudo,
presumably
to
to
get
this
thing
going
so
that
there's
not
actually
an
interaction
between
podman
and
docker's
back
ends,
and
you
can
see
the
containers
and
whatever
it's
it.
What
we
did
is
we
wired
the
docker
compose
application,
which
is
a
python
application.
C
B
B
C
C
If
you
want
to
make
a
different
container,
that's
that
name
or
whatever
you
deleted
it
and
you
recreated
it,
but
docker
compose
uses
rename,
and
so
we
were,
you
know
we
had.
We
had
to
force
to
contemplate
that
the
other
thing
we
had
to
do
is
fix
some
of
our.
We
had
two
network
commands
because
we,
under
that
same
belief,
you
didn't
really
modify
a
container
on
the
fly.
C
The
whole
ability
to
be
able
to
connect
a
container
to
a
network
or
disconnect
it
on
the
fly
was
not
something
we
wanted
to
do
this
forced
our
hand.
We
now
have
a
we
have
a
podman
network
connect
and
disconnect
command
because
compose
uses
that
so
so
it
really
forced
us
also
to
look
at
a
lot
of
things
we
were
doing
and,
and
so
the
side
effect
that
the
net
side
effect
was
just
a
good
thing
is.
A
Neat
yeah
sorry,
go
ahead.
Lots
lots
of
stuff
happening
in
chat
right
now.
I'm
gonna
start
from
the
easy
stuff
for
the
hard
stuff,
so
plain
risky
ask
was
volumes
one
of
those
I
remember
dan,
mentioning
that
docker
would
create
volume
directories
if
they
didn't
exist,
while
podman
wouldn't
with
podman
compose.
C
C
C
A
A
C
A
C
C
B
C
We
wrote
this
such
that
we
can
do,
fills,
can
be
added
and,
and
then
users
can
decide
or
somebody
a
developer
is
going
to
decide
it's
important
enough
to
add
it,
and
then
that
will
become
available.
The
lib
k
run
guys
have
asked
us
to
make
sure
that
we
sort
of
design
it
in
that
way
and
we're
happy.
I
mean
it's
not
really
any
extra
work,
we're
happy
to
do
that,
and
so
the
version
we're
using
right
now
it
uses
qmu
and
we
have
it
working
on.
A
I
like
that
that
that
decision
so
like
I'm
at
this
inflection
point
where
it's
like.
I
need
something
device,
wise
new
to
do
stuff
and
I'm
trying
to
figure
out
where
I
land
and
be
a
pc
or
m1
mac
or
whatever
new
ipad
pro
comes
out
next
month
or
whatever
I'm
not
sure.
Yet.
So
that's
interesting,
I
will
say
they're
quite
nice.
C
A
C
So
those
are
the
two
hurdles
we're
working
on.
Even
then,
we've
got
a
way
to
work
around
the
fact:
that's
not
official
and
we
there's
a
mirror.
We
can
go
grab
them
from,
and
so
the
user
experience
will
be
as
simple
as
this,
you
you're
going
to
brew,
install
podman
which,
which
will
bring
in
the
dependencies
and
whatever
else
we
need.
Then
you're
going
to
do
podman,
machine
init
and
hit
enter
and
it's
going
to
go
grab
the
default
image,
uncompress
it
and
then
you're
going
to
do
python.
C
A
C
There's
nothing
like
that.
Yet,
okay,
there
is
a
podman.
There
are
several
blogs
on
podman
on
mac
on
how
to
use
a
darwin,
a
binary
that
we
compiled
to
darwin
to
interact
with
a
linux
session
somewhere
else,
but
we've
never
talked
about
it
actually,
physically
being
on
the
same
machine
and
us
doing
all
the
setup
work
and
you
can.
C
We
didn't
really
want
to
get
into
the
virtualization
business
the
operating
system,
business.
You
know
to
make
this
all
work
and
wire
it
all
up
that
we're
kind
of
putting
ourselves
a
little
bit
out
there,
and
the
hope
is
that
the
upstream
community
will
help
once
we
get
the
initial
stuff
laid
out
like
that.
They'll
help
us
kind
of
maintain
it,
because
this
is
probably
a
little
bit
beyond
what
we're
going
to
be
long-term,
capable
of
doing.
B
C
B
B
It
might
be,
you
know
it
might
be
my
daily
driver,
but
that's
not
the
same
thing
as
the
thing
I'm
deploying
to,
and
you
know,
if
I'm
on
a
mac
or
whatever
right,
it's
even
worse.
So
you
know
it's
kind
of
interesting
to
be
able
to
say.
Oh,
you
know
what
okay
I'm
pretty
satisfied
with
this.
You
know
I
I've
been
using
the
fedora
core
os.
It's
fast
and
you
know
it's
excuse
me.
It's
got
some.
You
know
future
feature
set
or
whatever.
C
C
C
C
If
you
think
about
how
that
applies
to
this
scenario,
you
know,
you've
got
you've,
got
now
a
host
and
a
vm
so
root
full
and
rootless
on
the
host
and
rootful
and
rootless
in
the
vm,
and
you
know,
what's
going
to
be
the
deal.
So
what
we've
done
right
now
is
we've
just
enabled
rootless
on
the
host
rootless
on
the
on
the
guests,
but
that
has
limitations
primarily
in
the
networking
area
right.
We
can't
open
rootless
users,
can't
open
networks,
port
and
use
ports
that
are,
they
can't
create
bridge
networks.
C
C
So
it's
not
clear
cut.
We've
still
got
to
venture
that
way.
Volume
mounts
will
be
a
challenge
from
host
to
guests
with
two
different
os's
and
things
like
this.
So
we've
got
things
to
figure
out.
There
are
precedents
for
all
of
them.
We're
just
sort
of
at
this
stage
we're
just
it's
like
minimum
viable
prod.
You
know
product.
Can
we
get
this
working?
C
A
I
have
to
live
in
both
worlds
kind
of
so
yeah,
just
the
nature
of
the
beast
of
live
streaming
right,
it's
easier
to
stream
from
a
mac
than
it
is
a
fedora
rig,
although
we
have
used
fedora
quite
often
to
on
the
channel,
but
it's
right
and
it
used
to
be
the
os.
That
was
the
streaming
thing
before
you
move
to
cloud
instances
so
yeah
I've.
I've
fully
understand
that
linux,
mac
windows,
like
you,
can't
keep
track
of
all
three
or
maybe
even
two
like
it's
hard
enough
with
just
linux.
B
So
so
related
to
this
right.
So
if
people
wanted
to,
you
know
at
least
contribute
back
bugs,
you
know,
or
things
like
that,
like
what
should
they
do?
Is
there
like
a
mailing
list
they
should
join?
Is
there
is
there
a
binary
they
can
go
and
download
and
try
out
now
that
you
know
you
know
or
or
is
this
or
are
you
not
there
yet
in
a
sense,
we're
not
we're
not
well,
we
would
welcome
help
and
we
we
have
already
gotten.
C
C
Yeah,
it's
it's
a
little
of
both,
and
sometimes
you
get
stuff
for
stuff
that
you
knew
you
needed
to
fix,
just
haven't
gotten
to
it
yet
which
is
even
better
because
it's
like
they're
reading
your
mind,
so
we
haven't
changed.
What
you
can
get
from
brew
brew
is
still
the
the
I'll
call
the
old,
podman
remote
approach
where
it
interfaces
with
linux.
Yet
I
can't
see-
maybe
maybe
we
will.
I
don't
quite-
have
a
feeling
for
what
we
haven't
talked
about
this
problem
with
the
qmu
patches.
C
C
Yeah,
but
if
you
want
to
contribute,
there's
the
if
you
go
to
podman
io
podman.io,
there's
a
mailing
list,
there's
we'll
take
prs,
we
really
value
prs
from
the
community.
We
try
to
give
them.
You
know
the
first
read-through
of
the
day,
rather
than
appears
we'll
go
to
something.
Dan
is
very
good
about
dan
walsh
was
very
good
about
pointing
that
out
and
then
really
the
best
absolute
best
place.
Is
we
all
hang
out
on
freenode
in
a
channel
called
pound,
podman
nice
and
during
the
us
work
time?
C
C
B
C
B
A
B
Okay,
so
one
of
the
things
I
wanted
to
talk
about
was
one
of
okay.
So
actually,
why
don't
we
start
here?
So
when
I
do
the
docker
compose
stuff
like
how
is
podman
treating
it,
so
is
it
making
a
pod
that
is
putting
all
the
containers
in?
Is
it
a
separate
set
of
containers,
because
obviously
it
has
ramifications
for
how
the
communication
between
the
components
works
and
kind
of,
by
extension?
B
C
Sure,
when
you
run
docker
compose,
we
do
whatever
dr
compose
asks
for
so
in
the
docker
world.
That's
containers
ducker
to
this
point
is
unaware
of
what
a
pod
is
right
and,
in
fact,
there's
no
as
such,
there's
no
call
for
docker
compose
through
the
compatibility
layer
for
a
pod
that
all
sits
on
that
all
sits
on
the
podman
side,
like
we
have
all
that
extra
goodness
that
we
offer.
C
So
if
you
run
it,
you
get
what
you
would
in
docker,
you
get
the
same
network,
the
same
volume,
the
same
containers,
the
same
ports.
Everything
tries
to
follow
it.
If
it
doesn't,
it's
probably
a
bug
gotcha,
but
I
think
where
you're
going
is
what
do
you
do
then,
like
okay?
So
you
ran
it.
What
do
you
do?
What
are
some
things
that
you
can
do
with
that
from
from
someone
who
writes
code
for
podman?
What
what
do
I
think
is
that.
B
B
C
What
people
want
yeah?
That's
that
in
in
essence,
is
what
people
want,
and
now
we
want
them
to
say:
okay,
you
got
it
in
the
pot.
Man
do
something
you
know,
give
me
the
extra
chocolate
and
nuts
and
cherry
on
top,
and
so
our
view
is
I
a
good
example.
Is
I've
done?
I
wrote
an
article
with
irvashi
and
then
did
a
presentation
at
the
container
plumbing
days
that
described.
Okay,
we've
got
dr
compose
now
we
already
could
interact
with
kubernetes.
C
B
B
You
know
there's
a
lot
of
other
tools
that
I
wish
I
could
do
that
with
so
that
I
can
kind
of.
I
know
how
I
want
everything
to
connect
together.
I
don't
always
know
the
yaml
whatever
to
make
that
true
and
so
having
that
export
is
super
handy
yeah,
that's
kind
of
where
I
want
to
go.
It's
like
okay.
Now
I've
got
the
soccer
compose
yeah
mo
either
either
from
somewhere
else
on
the
internet,
or
something
that
I
figured
out
how
to
do.
C
C
On
that
topic,
that's
where
I
feel
podman
still
has
plenty
of
growth.
Is
that
assistance
from
single
node
to
kubernetes
and
back
so
thinking
as
a
developer,
I'm
trying
to
develop
this
application.
That's
got
these
pods
and
containers,
and
I
finally
got
it
working
on
my
on
my
laptop
the
way
I
want
it.
C
Oh
you
know
I
tried
to
do
this,
but
you
know
you
guys
don't
when,
when
you
snapshot
the
running
pods
or
the
running
containers,
you
don't
catch
this
attribute,
you
know
bug
so
then
we
we
say:
that's
not
a
bug,
that's
a
feature,
but
we'll
put
it
on
the
list
right
and
then
we
do
that
actually
of
late
people
have
just
given
us
a
pr
saying
you
don't
do
it
here.
It
is
and
we've.
A
C
C
Depending
on
how
you
snapshot
that,
I
might
say
well,
snapchat
those
three
snapchat
in
two
pieces:
two
groups,
one's
database,
one's
web
you'll,
get
two
yaml
files
and
then
service
files.
If
you
need
that
way,
they're
sort
of
organized,
but
we
always
we
oh,
when
we
do
the
yaml
it
has
to
be.
These
containers
have
to
be
in
a
pod.
Even
if
it's
just
one
container
in
one
pod,
that's
the
way
it
has
to
be
because
kubernetes
can't
you
know
kubernetes,
obviously
can't
run
straight
containers.
It
has
to
be
in
a
pod
as
well.
B
B
B
It
introduces
the
pod
concept.
Yes,
okay,
so
I
guess
for
me
as
a
consumer
right
like
so
what
I
would
actually
recommend.
Someone
do
is
kind
of
generate
the
cube
out
of
it
and
then
one
of
the
nice
things
about
podman
right
and
I
actually
I
know
I
filed
a
bug
about
this,
and
hopefully
it's
getting
better,
but
it's
like
then
I
would
want
to
turn
around
and
run
that
generated
cube
files
in
podman
to
make
sure
that
the
pods
are
now
set
up
correctly
because
now.
C
Yes
and
one
of
the
things
one
of
the
things
people
struggle
with
in
that
these
are
things
like.
I
said
that
we,
I
think
we
can
make
better,
there's
still
plenty
of
things
to
do
here
is
most
people
don't
under
that
aren't
familiar
with
kubernetes
but
are
familiar
with
docker
or
pod
man.
They
don't
really
understand
the
pros
and
cons
of
a
pot
of
grouping
containers
in
a
pot.
Oh.
B
B
C
C
That's
one
of
the
that's
one
of
the
things
that
we
get
daca
docker
compose
does
a
really
good
job
of
of
when
it
runs.
It
sets
up
all
the
dns
for
the
container
so
that
they
can
refer
to
each
other,
and
we
do
that
too,
but
there's
no
need
for
it.
When
it's
in
a
pod,
you
could
just
go
straight
to
localhost
or
something
like
that
right,
and
so
that's
one
of
the
upsides
that
people
quite
don't
quite
see.
Is
it's
not
that
hard
to
to
actually
make
this?
You
know
a
nice
tightly
bound
thing.
C
B
B
C
I
didn't.
I
wasn't
really
like
saying
enough,
but
we
are
requirements
driven.
We
we
we
have
ideas
on
where
we
want
to
take
like
really
core
stuff
like
security
and
networking,
and
you
know
things
that
are
core
to
the
runtime,
but
how
that
always
gets
ingested
and
used.
We
need
to
hear
sometimes
right
totally
totally.
C
C
We
talk
about
it
as
a
team.
The
team
is
primarily
a
container
runtime
expert.
We
know
we
know
about
right,
runtimes,
the
back
ends,
the
apis
name,
spacing
c
groups
v2.
We
know
about
those
things
to
say
that
we're
container
experts
it
depends
on
what
on
what
point
you're
coming
from
right
like
well,
I
don't
know
how
my
sequel
works
with
you
know
the
my
sequel
image
from
red
hat
works
with
the
alpine
image
of
php
over
here.
Like
yeah.
I
don't
know.
B
Well,
this
is
like
when
I
first
joined
red
hat
right.
I
came
in
as
a
developer
advocate
right
and
one
of
the
people
or
what
I
first
thought
was
hey.
I've
got
you
know,
red
hat
has
a
lot
of
engineers.
I
can
use
those
engineers
to
kind
of
inform
you
know
what
kinds
of
things
people
want
to
do
and
that
kind
of
stuff-
and
I
quickly
discovered
that
no,
I
can't
because
the
people
who
work
on
building
an
operating
system,
the
people
who
work
on
building
a
container
platform
or
whatever
are
not
the
same.
B
People
who
build
web
applications
right-
and
you
know
I'm
sure
both
can
you
know
at
least
in
in
many
occasions,
could
cross
over,
but
certainly
not
with
the
expertise
that
they
normally
or
or
kind
of
the
knowledge
of
the
pain
of
day-to-day
operations.
In
the
you
know,
in
whatever
you
know
house,
they
live
in
in
a
sense.
C
C
C
B
Because,
like
okay,
you
built
this
cool
thing,
but
as
a
consumer
of
it,
how
do
I
use
it
right?
But
so
that's
super
interesting,
so
we're
getting
close
to
running
out
of
time.
One
thing
I
wanted
to
ask:
you
was
okay:
we've
we've
beaten
docker,
composed
like
a
dead
horse.
What
is
your
favorite
feature
of
v3?
B
B
C
That,
for
me,
is
the
number
one
thing,
because
I
I
don't
think
it's
used
enough,
and
I
think
it's
a
shame
because
you
know
docker
compose
is
the
is
the
is
the
technology
that
allows
docker
and
podman
to
interact
and
yaml.
You
know,
kube
is
the
one
that
allows
podman
and
all
these
kubernetes
kubernetes
back
ends
to
to
coexist
right
right.
So
anytime,
you
can
find
that
that's
where
the
powerful
stuff
is.
C
B
B
It's
it's
cool
once
you
know
it's
happening,
but
at
first
you're
like
what
like,
where
did
it
come
up
with
this
thing
over
here?
At
least
that
was
my
my
opinion.
The
other
related
one
that
I
thought
was
interesting
is
the
the
like
menu
of
options,
if
it's
not
sure
which
container
you
want,
which
was
interesting,
because
I
found
one
where
all
four
of
the
options
didn't
actually
exist
at
the
far
end
and
I
was
kind
of
like
well.
This
is
disappointing.
B
Like
could
we
have
like
maybe
a
little
bit,
and
I
was
thinking
about
going
to
file
a
bug
about
this,
but
it's
like
maybe
a
little
bit
of
checking
of
that.
Is
this
an
actual
option,
even
though
it
looks
like
an
option
was
kind
of
funny
and
I
I
definitely
hit
an
edge
case
there.
I'm
I'm
certain,
but
I
thought
that
was
really
neat
is
the
you
know.
C
C
That's
how
that
product
was
designed
right
in
our
world,
with
podman
and
sort
of
being
open
sourced
a
little
bit
more
open-minded
on
where
things
come
from,
you
can
have
10
registries,
and
by
default
we
usually
ship,
two
or
three
enabled
right
fedoras,
and
you
know
whether
it's
quay
or
red
hat
or
you
know
whatever,
and
so
what
was
what
and
then
dr
io?
What
was
learned
is.
It
is
possible
that
if
you
type
in
podman
run
fubar
and
it.
C
C
B
Interesting,
I
I
didn't
actually
know
about
the
remember
part
that
it's
definitely
interesting
and
useful.
You
know,
I
think
that's
another
thing.
Maybe
I
would
go
kind
of
file
a
bug
about,
though,
is
that
if
I
then
go
and
turn
around
and
do
cube
generate,
for
example,
is
it
going
to
put
in
the
fully
qualified
names?
I
would
want
it
to
because
I've
now
I've
now
indicated
maybe
a
non-default
choice
right
and
I
actually
had
this
problem
in
openshift
we
talked
about
it
on
the
show
of,
like
I
tried
to
get
a
particular
image.
B
I
didn't
have
the
secret
setup
to
get
it,
and
so
it
silently
failed
and
gave
me
a
different.
It
gave
me
an
alternative
which
was
completely
bored
because
it
was
set
up
completely
differently,
so
yeah,
so
that
that's
really
interesting.
I
really
like
that
feature.
I
thought
it
was.
It
was
really
cool.
C
B
B
Who,
I
assume,
has
not
watched
the
show
all
that
regularly?
If,
at
all,
what
we
do
is
we
have
a
fun
little
game
where,
if
you
kind
of
watch
episodes
and
fill
in
a
google
form,
you
collect
points
and
so
and
then
every
episode
we
talk
about
where
people's
standings
are
and
so
right
now,
with
4
700
points,
we
have
narendev
and
then
netherlands
hackum
mind
you
brent.
Just
by
way
of
context,
we
completely
make
up
how
to
say
these
names.
C
B
B
We
need
joe
fuzz
to
come
back
and
detective
kona
kudo,
who
also
goes
by
the
eighth
doctor,
I'm
not
sure
which
one
he
is
today,
but
we
know
him
from
fedora
land
pretty
well
and
then
bacon
fork
with
800
points
exactly
so.
Thank
you
all
so
much
for
collecting
those
points.
I
am
looking
for
the
correct
window
to
be
able.
A
B
Or
just
go
enter
manually
and
then
the
other
thing
that
I
do
on
occasion
is
today.
I
just
want
to
call
out
some
new
people,
so
we
have
daggo
bertz,
pinhead,
tejas,
rao,
rao,
probably
97,
who
are
some
new
people
to
the
show
or
loose
new
people
to
submit
for
points.
For
example,
jp
dade,
who
I
think
is
here
at
most
episodes
still
has
like
near
zero
points.
Jp
dave,
you
could
be
getting
points
and
you
know,
but
we
like
to
welcome
new
people.
B
We
hope
you
come
back.
We
hope
you
found
the
episode
interesting,
a
couple
of
quick
points.
I
would
just
make
about
past
episodes.
We
have
jeff,
I
went
and
looked
it
up
it's
in
the
chat,
but
it
we
started
covering
podman
cube,
generate
in
like
episode.
Seven,
it
sounds
like.
Maybe
we
should
do
a
new
one
using
v3,
which
would
be
kind
of
cool,
because
I
think
it's.
I
think
it's
a
super
cool
feature.
B
I
agree
with
you
brent,
it's
like
highly
unknown,
and
it
really
needs
a
lot
more
surfacing
because
I
think,
even
even
if
you
aren't
going
to
cube
the
ability
to
generate
that
gamble
and
then
replay
it
even
in
pod,
man
is,
is
so
much
like
the
feature
set
of
docker
compose
that
it's
totally
worth
it,
whether
you're
using
kubernetes
of
any
kind
at
all
so
yeah.
I
strongly
recommend
it.
Thank
you
again
for
being
on
the
show.
Thank
you
for
all.
A
B
C
A
B
A
B
B
B
Sudo
is
because
I
almost
never
use
the
root
user
and
and
so
that
I
don't
accidentally
rm-rf
slash
right.
You
know,
like
I
mean
it's
nice,
that
rm
actually
has
a
built-in
that
is
hard
to
do
that
now.
But
the
that's
kind
of
the
point
is
like
I'm
operating
this
piece
of
software
as
non-root,
because
I
know
I
screw
that
kind
of
thing
up
regularly
right
when
an
app
makes
me
think
that
I'm
non-root,
but
I'm
actually
root,
that's
very,
very
dangerous
for
me.
C
And
by
the
way,
that's
one
of
the
biggest
issues
or
complaints
against
podman,
which
is
a
bit
unfounded.
Is
we
get
users
that
have
been
running
container
x
on
docker
for
three
years
and
then
they
run
it
and
podman
is
rootless
and
it
doesn't
work
and
that
you
know
coupon
pod
man
in
because
of
it,
and
then,
when
you
start
asking
questions
well,
that
container,
like
you
know,
needs
to
map
to
a
port
less
than
1024,
or
that
container
is
doing
something.
That's
privileged
and
therefore
does
have
to
be
run
as
root.
C
B
Fire
will,
you
know,
turn
off
the
firewall
see
if
it
works
right
turn
it
back
on.
If
you
know,
try
your
pod
or
try
your
image
as
a
you
know,
root
podman,
and
then
you
know,
that's
that's
funny.
I
I
don't
do
that.
Generally
speaking,
I
find
the
error
messaging
is
sufficient
to
kind
of
say.
Oh
yeah,
you
know
like
I
am
doing
something
that
requires
root
or
whatever,
but
that
is
a
good
that
is
a
good
tip
I'll
I'll.
Definitely
keep
that
one
around.
I
like
it
all.
A
A
B
Yeah
duh,
so
we
are
doing
we're
gonna,
give
away
some
tickets
to
cubacon,
we
have
some
tickets
and
we
are
going
to
take
a
slightly
different
tack
in
a
sense
than
the
general
internet
points
tack,
which
is
what
we're
asking
people
to
do
is
post
somewhere
on
the
social
media
pick
whichever
one
you
like,
the
best
that
you
you
know
something
cool.
You
learned
on
the
level
up
hour,
then
give
us
a
link
to
it
in
the
discord
and
say
this
is
what
I
posted
about
the
level
up
hour.
B
You
know
or
whatever,
and
then
so
for
every
time
you
do
one
of
those
social
media
posts
and
then
link
to
it
in
the
discord.
So
I
don't
have
to
follow
all
of
the
socials
forever.
That's
why
we're
asking
you
to
put
a
link
to
it
in
the
discord?
You'll
get
an
entry
into
our
our
little
raffle
to
give
away.
We
a
few
q
con
tickets
that
we
were
able
to
secure,
and
so
we
can
hopefully
support
you
going
to
kubecon.
B
B
And
so
you
know
so
you
can.
You
can
win
multiple
ways
in
a
sense
but
definitely
want
to
use
the.
This
is
an
opportunity
to
share
what
you've
learned
and
you
should
see
some
tweets
from
me
over
the
next
few
days.
You
know-
and
I
think
I
even
started
using
the
hashtag.
You
know
share
what
you
learned
in
there,
because
I'm
a
nerd
but
yeah
so
hopefully
we'll
have
a
fun
little
contest
and
you
will
also
get
internet
points
for
joining
the
disc
award.
B
A
B
A
B
A
A
B
A
B
B
Break
and
we're
doing,
oh,
then
we're
supposed
to
be
doing
a
deep
dive
into
the
ubi
with
mr
mccarty
and
then
the
one
after
that
is
when
we
do
that
t
show
with
some
pretty
big
guests
which,
as
soon
as
I
as
soon
as
we
can
like,
probably
later
this
week,
we
will
be
announcing
those
guests
and
we'll
actually
be
teasing.
A
little
bit
of
another
show
that
red
hat
produces
and
then
kind
of
going
into
a
deeper
dive
on
what
that
show's
about.