►
Description
Building the Perfect Tools Container (rhel-tools)
Have you used the `rhel-tools` container? Come learn about what it is and what you can use it for.
Learn more at https://red.ht/leveluphour
A
Good
morning,
good
afternoon,
good
evening,
welcome
to
the
level
up
hour
on
openshift.tv,
I
am
chris
short
principal
technical
marketing
manager
on
the
openshift
team.
I
am
also
a
cncf
ambassador.
I
was
also
a
sys
admin
back
in
the
day,
I
was
also
a
network
admin
and
all
kinds
of
other
fun
things
and
I'm
joined
today
by
langdon
white
langdon.
Please
introduce
yourself
hello.
B
Everybody,
I
am
langdon
white
and
this
is
the
level
of
power.
I'm
not
sure
how
much
introduction
we
should
do
every
time
you
know,
but
I
am.
B
It's
hard
to
say
you
know,
but
I'm
a
former
developer
advocate
engineer,
consultant
now:
technical
marketing
manager,
with
red
hat
and
I'm
here
to
convince
you
that
containers
are
awesome
and
you
really
want
to
be
using
them,
and
so
that's
what
we
talk
about
during
this
show.
I
do
have
to
apologize
because
you
know
my
support
staff
at
my
house
was
in
the
middle
of
making
coffee
and
that's
why
the
coffee
was
delayed.
Our
start,
you
know
your
staff
board
staff.
A
B
B
Hear
you
it's
because
I'm
so
young
at
heart
or.
B
Exactly
so
today,
ostensibly
we're
going
to
get
to
a
container
type
called
rel
tools,
but
there's
a
bunch
of
stuff.
I
want
to
talk
about
before
we
get
there,
so
I
hopefully
we'll
get
there
we'll
see
and
I'm
also
concerned
sorry.
My
I
think
I
forgot
to
take
a
zyrtec
this
morning.
C
B
So
I
may
have
to
break
that
off.
B
Clean
for
a
little
bit,
so
we
were
going
to
talk
a
little
bit
about
kind
of
the
the
way
you
can
kind
of
get
to
the
rel
tools
thing
and
maybe
we'll
learn
some
new
stuff.
I'm
always
impressed
myself.
If
I
teach
you
something
that
you
haven't
seen
before,
so,
let's
see
should
we
go
ahead
and
get
started.
Is
there
any
other
introductions?
We
should.
A
A
In
by
no
doing
of
their
own,
potentially,
you
know
who
knows
yeah.
B
Well,
it's
also
the
convenience
factor.
I
think
of
containers
is
very
high,
which
I
don't
think
you
know
people
necessarily
realize,
and
so
yeah
there's
this
all
this
scary
cloud
native
stuff
in
a
sense,
but
in
fact
many
of
the
things
you
might
want
to
do
are
actually
easier
in
kind
of
a
cloud-native
sort
of
way.
B
Surprising
so
yeah,
so
I
wanted
to
get
started
with
okay.
So
let's
start
here
where,
let's
see,
if
I
have
the
right
tab
open,
of
course,
I
don't.
C
B
We're
gonna
start
with
the
container
catalog
red
hat
cad
catalog,
and
is
it
this
guy?
B
Google
was
in
my
way
that's
what
I'm
looking
for.
So
the
thing
we're
going
to
be
talking
about
today
is
this
thing
called
rel
tools
and
what
I
want
to
point
out
with
rel
tools.
It
was
it's
actually
only
available
as
a
rel,
seven
version.
That
doesn't
mean
it's
not
interesting,
especially
if
you're
managing
real
seven
servers,
which
we
know
something
like
some
ridiculous
percentage
of
people
are,
so
it's
it.
B
You
know
it
probably
largely
works
on
a
rel
eight
host,
but
because
it's
the
concept
of
this
is
that
it's
so
integrated
with
the
os
itself
that
it
may
not.
So
you
know,
generally
speaking
right,
you
can
run
kind
of
any
container
on
any
of
the
rails
generally,
some
of
that
scenarios
are
supported
and
some
aren't,
but
you
know
in
general
it
should
just
work
right
with
this
thing.
B
It's
a
little
shakier
just
because
when
you
you
know,
because
the
whole
idea
of
this
container
image
is
that
it's
tightly
integrated
and
let
me
actually
let
me
back
up
a
little
bit
for
a
second.
So
what
we've
done
in
the
past
couple
episodes
right
is.
We
talked
about
here's.
How
to
get
a
container
that
is,
you
know,
kind
of
single
purpose.
B
I
need
this
tool,
it's
not
installed
by
default,
so
I
want
to
go.
Get
it
right
and
I
want
to
just
be
able
to
use
it
one
time
or
whatever
so
like
netstat
was
an
example,
and
then
we
had
a
few
others.
If
you
want
to
know
the
rest
of
them,
go
back
and
watch
the
show
right.
If
and
then
we
talked
a
little
bit
about
okay.
Now
I
have
a
custom
piece
of
software.
A
B
Random
places
right,
so
I
wanted
to
show
that
in
a
container.
So
what
we're
looking
at
today
is
okay.
Well,
wouldn't
it
be
nice,
even
if
it's
a
little
heavy
weight.
If
I
had
a
tool
set
all
in
one
container
that
I
could
use
any
of
the
tools
in
right
and
red
hat
actually
publishes
a
few
of
these
and
over
the
next
couple,
episodes
we're
going
to
kind
of
look
at
all
of
them
and
they
all
kind
of
take
slightly
different
approaches.
B
So
the
first
one
we're
talking
about
is
this
one,
which
is
rel
tools
which
was
originally
developed
way
back
when,
when
we
used
to
talk
about
atomic
host,
an
atomic
host
and
core
os
or
what
we're
calling
what
red
hat
core
os
now
is
are
very,
very
similar.
They
both
use
the
same
technology
underneath
the
rpmos
tree
and
the
idea
is
you
have
an
operating
system,
that's
immutable,
except
for
configuration.
B
B
So
the
problem
with
an
os
tree
based
host
is
that
the
scenario
of
you
know
a
lot
of
times
in
a
data
center.
You
don't
want
to
install
anything
because
it's
dangerous
and
makes
you
frightened,
but
in
the
case
of
our
cause,
right
or
rh
cause
or
red
hat
core
core
os,
you
can't
actually
install
anything
else
or
at
least
not
without
a
huge
amount
of
difficulty.
B
So
this
thing
this
tool,
this
toolbox
essentially
was
developed
to
try
to
get
you
some
of
the
tools
that
you
need
for
troubleshooting
and
debugging,
that
kind
of
stuff
to
be
making
it
available
on
an
immutable
operating
system.
B
So
all
that
said,
if
you
see
references,
for
example
in
the
documentation,
so
taking
a
look
at
real
atomic
host,
for
example
great
and
yes,
that
was
its
original
use
case,
but
that
doesn't
mean
it's
not
also
useful
in
a
regular
rail7
or
you
know,
or
maybe
a
rail
eight
like
I
said
your
mileage
may
vary
because
you
still
don't
want
to
install
anything
on
those
if
you
can
avoid
it.
So
the
container
is
really
useful
as
just
a
set
of
tools
that
you
might
find
handy.
B
So
that's
a
bunch
of
background
around
and
did
we
have
any
questions
in
the
chat.
B
A
Like
he
is
usually
every
week
and
we're
talking,
coffee
making,
apparently
charles
mahoney's
five-year-old,
can
make
coffee.
Now
that's
super.
A
B
It's
just
we
don't
go
to
a
lot
of
effort
per
capita.
A
B
Excuse
me
so
talking
about
rail
tools.
Okay,
so,
let's
see
I
want
to
talk
okay,
so
one
of
the
things
we've
talked
about
this
a
little
bit
in
the
past.
Is
that
there's
a
difficulty
in
running
a
container
of
somebody
else's
and
that
difficulty
is,
how
do
you
run
it
right?
B
And
so
there
have
been
a
number
of
attempts
and
I
think
we
talked
about
some
of
these
attempts.
You
know-
maybe
maybe
it
was
last
week.
You
know
talking
about
things
like
juju
and
charm
and
helm
and
charts,
and
even
this
old
thing
called
atomic
app
that
that
I
actually
worked
on.
But
one
of
the
other
things
was
this
atomic
cli,
which
was
originally
developed
as
kind
of
like
this
extra
tool
that
came
with
every
atomic
host
and
has
kind
of
since
been
discontinued.
B
But
one
of
its
side
effects
was
this
idea
of
using
the
labels
on
container
images
as
a
way
to
give
information
to
future
users
right
right,
and
so
I
couldn't
figure
out
a
great
way
to
make
this
show
nicely.
But
okay,
so,
let's
just
kind
of
start
off
with
so.
B
So
it
might
have
just
been
me,
my
you
know.
B
If
we
do
a
pod,
man
inspect-
and
I
don't
know
about
you,
but
I
always
have
a
mental
block.
It's
inspect
and
then
info
gives
you
information
about
how
podman
is
installed
and
set
up.
B
Blame
you
for
that
at
all,
so
there's
lots
of
useful
information
in
here
about
the
container,
but
the
thing
we
want
to
look
at
in
this
particular
case
and
I'll
try
to
expand
this.
So
it's
a
little
bit
more
legible.
That's
what
I
mean
is
it's
it's
hard
to
make
it
legible,
but
is
this
block
called
labels?
Oh
stupid
t-mucks.
C
B
I
always
fall
for
it,
okay,
so
this
block
called
labels
here,
which
basically
has
this
whole
set
of
different
labels
and.
C
B
Notice
description
exactly
so,
there's
what's
the
license
on
it
and
I'm
going
to
stop
selecting
so
that
it
stops
jumping
or
I
can.
I
can
select
this
way
if
I
remember
so,
there's
the
license
on
it.
Here's
the
architecture,
one
of
the
things
that
we've
been
trying
to
introduce,
is
multi
architecture,
containers.
B
Starting
to
be
a
real
thing,
and
so
that's
also
super
useful
mostly,
you
should
never
have
to
worry
about
this
too
much
right.
It
should
select
the
architecture,
that's
appropriate
for
the
platform
you're
on,
but
but
then
you
have
kind
of
useful
for
end
user
information
right.
So
you
have
things
like
the
description
and
then
what
I
really
want
to
get
to,
though,
is
this
thing
called
run,
and
so
what
run
does
is?
B
B
That,
but
there
is
just
a
label,
excuse
me,
and
so
you
can
find
out
what
that
you
know
what
the
what
the
recommended
way
of
running
this
label
is,
and
so,
if
we
do,
I.
B
Right,
so
what
we
can
do
is
we
can
kind
of
look
at
the
individual
piece
by
delving
in
like
like
extracting
the
this
individual
label
from
oops.
B
B
Well,
the
point
being
you
know
so
normally
this
works.
I
don't
know
why
it's
not
working
today
for
me.
Maybe
I
have
a
typo
somewhere
that
I'm
just
not
seeing,
but
that's
what.
B
To
look
at
it
differently
anyway,
so
admin,
I
think,
to
kind
of
avoid
the
docker
naming
namespace
has
a
lot
of
like,
in
my
opinion,
kind
of
slightly
pretty
complex
commands.
B
Oh,
my
god,
I
am
having
c
oh
and
then
you
need
run
okay.
So
what
this
says
is
kind
of
in
the
container
stuff.
Take
a
look
at
the
run
label
then
display
it
and
then
you
this
is
which
run
label
we
want,
because
in
theory
you
can
have
more
than
one,
but
I
haven't
seen
that
too
often,
you
know-
and
I'm
not
entirely
sure
of
the
use
case
for
that.
B
But
if
you
do
this,
it'll
actually
not
only
show
you
kind
of
like
we
saw
before
in
the
label
up
here
all
right.
So
there
should
be
in
here.
B
A
A
C
A
B
C
B
You
can
also
obviously
cut
and
paste
it
sure
and,
of
course,
is
this
not
gonna
work
for
us.
What's.
A
B
So
the
idea
yeah,
which
is
good
in
a
sense
this
guy,
the
idea
of,
is
it's
a
container
that
you
kind
of
keep
around
and
keep
adding
to
right.
So
if
you've
heard
the
not
ps,
sorry
if
you've
ever
heard
the
which
we
don't
really
like
right-
the
pets
versus
cattle
metaphor,
there
was
a
guy
there's,
a
guy
called
the
stevo.
B
Who
has
a
elephants
and
ants
metaphor,
which
I
like
better,
because
it's
because
if
you
actually
ever
had
cattle,
you
do
actually
have
a
fairly
strong
relationship
with
most
of
your
cattle.
So
the
idea
being
is
that
this
container
is
one
that
you
treat
like
a
pet
like
you
keep
adding
to
it,
you
you
know,
use
it
or
whatever.
Obviously
it's
still
pretty
ephemeral,
you
can.
You
know
I
just
destroyed
it
relatively
easily,
so
you
don't
necessarily
want
to
put
anything
in
there.
B
That's
going
to
be
super
dangerous
to
to
wander
off
with,
but
you
what
was
I
going
to
say
so,
but
you
can
look
at
you
know,
so
you
can
kind
of
keep
adding
to
it.
But
that's
why
it's
a
named
container
and
actually
before
we
start
talking
about
rel
tools
entirely.
Why
don't
we
just
look
real
quick
at
how
you
do
the
run
label.
B
And
it's
really
obvious,
so
you
just
put
in
a
there's
just-
and
this
is
supported
by
you-
know
most
of
the
container
runtimes,
and
so
you
just
put
in
a
label
called
run,
and
then
you
have
certain
variables,
which
I'm
sure
are
docs
somewhere,
that
you
can
use
to
indicate
what
you
want
it
to
be.
B
C
B
B
Yeah
there's
there's:
this
is
a
very
quote-unquote
dangerous
container
to
run.
However,
if
you
notice,
I
am
still
running
it
as
non-root
right,
so
it
doesn't
have
complete
privilege.
A
B
In
theory,
so,
okay,
so
what
we
do
is
we
do
the
run
on
the
run
label
and
that
should
work
better.
This
time.
B
What
I
love
about
both
docker
and
podman,
is
that
you
don't
have
to
type
the
complete
id
just
enough
to
make
it
unique
or
you
can
even
give
it
the
name
which
is
probably
in
this
case
a
better
choice.
B
Now
it
should
just
drop
yeah.
That's
what
I
thought.
Okay,
so
you
got
to
do
bin
bash
and
then
you
usually
want.
I
t.
B
A
B
B
B
883,
I
thought
it
was.
I
still
think
it's
podman's
start.
C
B
B
B
B
Right
clearly,
I
think
there's
a
difference
between
privileged
running
that
container
as
a
root
user
and
privilege
running
a
container
as
a
non-root
user
absolutely.
But
this
is
a
little
bit
where
you
know
you
kind
of
have
to
dig
into
the
details
a
little
bit
and
I
haven't
lately,
because
this
is
something
podman
can
do
and
docker
can't
and
not
something
that
comes
up
for
me
a
whole
lot.
You
know,
basically
it's
one
of
those
things
where
I
know
what
I'm
trying
to
accomplish.
So
I
usually
pull
off
the
security.
C
A
B
So
what
I
discovered
is
that
so
I
don't
know
how
many
people
are
aware
of
the
ls-lz
command,
but
this
will,
if
I
have
any
if.
B
I
just
made
it
last
night
because
it's
roll
seven.
So
if
you
notice
here
most
of
these
files
are
labeled
user
home
t
in
order
to
access
files
with
user
home
t
or
a
bunch
of
other
labels,
you
need
to
pass
the
colon
z
to
get
those
to
turn
into
a
a
label
with.
B
Container
file
t
so
what
happens
when
you
pass
that
colon
z?
Is
it
re-labels
it
as
container
file
t
so
and
that's
how
you
access
it
from
within
the
container?
However,
if
you
notice
here
so
this
is
actually
a
sim
link
to
a
nfs
mounted
directory.
Okay.
Basically,
what
I
do
is
I
loop
back
onto
my
host
machine,
where
the
actual
files
are.
A
B
To
make
you
know,
so
I
don't
have
to
install
everything
in
every
vm.
I
make
right.
A
B
B
So
I
thought
that
was
super
interesting
and
you
get
a
very
unusual
error.
Basically
that
says
you
pass
the
colon
z
and
it
tells
you,
oh,
you
can't
do
this,
because
it's
mounted-
and
so
I
can't
relabel,
but
it
turns
out
that
it
will
actually
just
work
if
you
just
drop
the
colon
z
which
never
would
have
occurred
to
me.
A
A
Yeah
so
narendra
has
some
chat.
You
know
like
how
to
run
a
container
as
root
right
like
is
it
actually
as
simple
as
oh,
it's
pseudo
pod
man
yeah.
That's
it
right
like
don't
don't
overthink
it.
Narendev
is
basically
like,
don't
read
too
much
into
it
and
don't
try
like
I
get
it.
It's
it's
layered
and
it
could
be
a
little
complicated,
but
pseudo
podman's
sudo
docker.
That
would
run
the
container.
B
As
free
exactly
and
the
most
common
reason,
I
want
to
do
that,
and
this
is
one
of
those
kind
of
never
ending.
I
think
data
center
problems,
whether
that
data
center
is
your
house
or
a
real
data
center
is
I
want
to
run
whatever
thing
web
server,
the
one
I
I
come
up
with.
B
All
the
time
is
actually
a
znc
server
on
its
standard
port
and
running
it
on
its
standard
port
is
a
privileged
operation
and
the
reason
I
want
to
run
on
a
standard
port
is
because
I'm
firewalled
and
nodded
and
routed,
and
all
that
stuff,
such
that
from
the
external
you
can't
get
to
that
port
directly.
Right,
like
you,
can
only
get
to
you
know
some
manufacture
port.
That
then,
is
rerouting
blah
blah
right,
but
to
minimize
the
headaches
in
the
actual
tool,
I'm
using
you
know
whether
that's
apache
or
whatever.
B
I
just
want
to
run
that
as
port
80
right
and
in
order
to
do
that,
you
need
to
build.
You
need
to
run
it
as
a
privileged
operation
to
be
able
to
get
to
port
80..
So
that's
a
bad
practice
on
my
part.
A
lot
of
the
time
I
should
probably
be
running
those
as
unprivileged
ports,
so
I
should
be
running
an
apache
8080,
but
if
you're
doing
something
quick
and
dirty
and
I'm
routing
that
way,
that's
why
I
often
do
it
that
way.
B
Openshift
is
interesting
like
this,
because
it
it
basically
it
kind
of
does
what
I'm
describing
right,
where
openshift
is
actually
running
it
or
even,
if
you
look
at
a
standard,
if
you
do
like
pod,
man
run
minus
p
or
minus
p.
B
C
B
A
B
B
I
have
no
idea,
oh
I'm,
on
the
rel8
machine.
Oh
that's
weird!
Oh
okay!
Oh
I
thought
I
opened
a
new
tab,
but
I
am
an
existing
one.
That's
why
okay!
So
let
me
just
look
here:
yeah,
okay,
so
this
as.
C
B
B
I
shouldn't
need
to
do
that,
but
whatever
okay.
So
now,
if
we
look
at
httpd
right,
it
actually
manufactures
a
port
right
and
it
points
it
at
point
80.
As
far
as
the
container
is
concerned,
so
inside
the
container,
my
apache
everything's.
B
Does
the
same
thing
right
and
this
is
in
some
ways-
this
is
the
right
answer.
One
thing
I
will
point
out
about
podman
that
I
am
not
in
love
with
and
have
filed
a
bug
about
is
that
this
number
is
essentially
randomly
generated
and
if
you're
used
to
docker
it's
a
counter.
B
So
when,
when
I
was
doing
a
lot
of
debugging,
for
example-
and
I
wanted
to
restart
a
container
over
and
over
and
over
again,
I
could
guess
what
the
new
port
would
be,
but
you
can't
do
that
with
podman.
It
will
be
a
random
number
again
from
a
security
perspective
that
might
be
better,
but
from
a
debugging
perspective,
it's
not
as
much
fun
so
yeah
nice,
so
we
kill
out
of
that.
Okay.
So,
let's
see
what
else
I
want
to
talk
about
related
to
this.
B
Oh
in
the
show
notes.
I
have
a
couple
references
in
particular
this
article
about
the
run
label.
Basically,
this
guy,
who
is
a
big
contributor
to
podman
and
all
things
container
inside
red
hat
anything
he
ever
writes,
go
read
it
it'll
be
like
smarter
than
certainly.
I
am
right.
A
B
A
You
drop
that
link
into
something
that
I
can
drop
into
chat
or
you.
B
B
So,
thank
you
yeah.
I
actually
have
it
open
this
time,
I'm
doing
pretty
well
all
right,
so
so
there's
that
guy
and
then
there
is
also
again
off,
like
I
said
I'll
put
these
in
the
show
notes.
But
like
here's,
you
know
a
blog
post
about
the
rel
tools,
guy
itself,
you
know
and
how
you
might
want
to
use
it.
Oh
and
then
actually
speaking,
of
running
containers
as
rootless.
Here
you
go
because
I
was
looking
at
this
earlier.
A
Okay,
that
is
his
twitter,
handle
narendev.
B
C
A
Chris
shorts
and
we're
all
in
tech
or
we're
all
tech
savvy
when
I
went
to
go
by
chrisshort.net
in
2003,
somebody
had
scooped
chriswort.com
in
2002.,
yeah,
they're,
a
photographer
and
digital
artist.
So
I
was
like
well
that's
fine.
I
do
work
on
infrastructure
and
networks
and
you
know
all
kinds
of
fun
stuff,
so
that
works
well.
A
B
Used
to
do
because
I
was
in
consulting,
I
would
basically
go
after
the
brand
name
of
my
full
name,
so
langdon
white.
C
A
B
Stupid
twitter
handle
right,
it's
just
way
too
long,
yeah
and
but
because
I
wasn't
a
big
user
of
twitter.
I
didn't
really
get
that
at
first.
So.
C
B
Time
I
kind
of
started
being
a
big
twitter
user.
I
I
kind
of
went
back
and
was
like
oh
I'm,
an
idiot
so
we'll
yeah,
so
there
there's
the
the
background
for
that
story.
All
right,
let's
see
so
rail
tools.
So
let's
now
that
we
theoretically
know
how
to
actually
get
into
rel
tools
again,
we
can
go
into
rail
tools
and
then
oh
and
then,
of
course,
let
me
show
you
what
is
not
here
right,
so
no
net,
stat
and
then
inside
rail
tools.
B
So
the
way
so
this
one,
this
container
takes
a
slightly
different
approach
than
we've
been
taking
right,
which
is
that
what
we've
been
doing
is
what
I
commonly
refer
to
as
an
executable
container.
So
one
where
we
can
just
say
podman,
run
and
then
essentially
feed
it
flags
right
or
or
arguments
or
whatever,
and
it
will
run
whatever.
The
thing
is
this
one
takes
the
approach
more
so
of
you
go
into
the
container
and
it
has
enough
privilege
to
do
the
operations
on
the
local
machine.
B
How
many
people
I
know
in
the
rel
admin
world
right
pseudo
is
kind
of
a
new
thing.
That
really
was
much
more
in
the
debian
side
of
the
house,
but
for
me
I've
always
been
a
pseudo-user
and
so
there's
a
sometimes
I
use
sudo,
because
I
want
to
do
a
couple
of
things
right
and
sometimes
I
actually
su
into
the
root
account,
because
I
want
to
do
a
whole
series
of
things.
B
So
it's
kind
of
like
that
difference,
so
it
kind
of
depends
on
the
use
case
and
what
you're
trying
to
accomplish,
which
one
you
want
to
use
so.
But
we
can
also
take
a
look
at
the
docker
file
itself,
which
of
course
I
lost
that
window.
Why
is
there
no
bottom
scroll
bar?
That's
weird,
so
yeah.
So
if
you
notice
this
is
command
user
bin
bash.
So,
as
a
result,
we're
always
going
to
drop
into
that
another
way
you
can
develop
this
same
tool.
A
B
Exactly
you
can
override
this
make
an
entry
point
here
that
would
somehow
get
you
the
set
of
commands.
You
wanted
right
that
might
get
a
little
tricky,
trying
to
figure
out
how
to
make
the
difference
like
basically
make
them
all
available,
but
maybe
we'll
play
with
that
when
we
get
to
so
we're
gonna
go
through
a
few
of
these
containers
that
exist
and
then
go
and
try
to
develop
our
own
and
figure
out.
B
Maybe
how
do
we
choose
the
best
of
both
worlds
or
all
worlds
right
that
we
want
but
kind
of
going
back
to
the
soccer
file?
One
of
the
nice
things
about
the
docker
file
and
being
able
to
see
the
docker
file
right.
This
is
beauty
of
open
source
right.
Is
this
kind
of
tells
us
all
the
stuff
that's
inside
here?
B
So
these
are
all
the
different
tools
we
have
available
and
again,
if
there
is
a
tool
that
we
don't
have
that
we
would
like
to
have,
we
can
also
either
you
know,
because
this
is
a
persistent
container
or
semi-persistent
container.
You
know
we
can.
I
don't
know
if
wireshark
is
actually
out
there
is
that
do
we.
B
C
B
B
Yeah
so
so
I
don't
know
if
it's
there,
but
if
we
wanted
something
else,
you
know
we
could
track
it
down
and
install
it
whatever
it.
A
B
Let's
see
so,
are
there
particular
things
we
might
want
to
talk
about
here?
You
know
we
could
go
into
screen
and
really
confuse
ourselves,
but
I
you
know
like
one
of
the
nice
things
I
think
is
that
it
does
have
get
installed
and
you
know,
like
I
said,
before:
netstat
and
tcb
dump
and
kind
of
all
the
things
you
might
want
to
use
for
your.
A
A
I
need
to
go
check
on
a
system
right
and
I
don't
want
like
my
key
is
already
set
up
right
like
I
can
ssh
wherever
I
need
to
go
on
the
network
and
everything
right
and
but
I
don't
necessarily
want
to
leave
the
friendly
confines
of
my
ide
right
like
because
I'm
used
to
working
in
that
environment.
Potentially,
you
know,
there's
a
way
to
do
remote
connections
and
then
there's
a
way
to
do.
A
A
B
Yeah,
no,
I
think
that
was
good
yeah
one
of
the
old-school
ways
of
doing
that,
which
I
don't
know.
I
don't.
I
doubt
this
one
is
set
up
this
way,
but
is
people
would
actually
install
ssh
in
the
container
right.
B
Well,
yeah,
I
mean
it's
one
of
those
things
I
mean.
If
somebody
connects
to
your
host,
you
know
so
yeah,
so
that
would
be
that
that
was
one
way
people
used
to
do
it.
We
are
past,
like
we
have
so
much
privilege
in
this
container
that
if.
A
B
So
I'm
not
actually
running
ssh
inside
this
container,
but
I
wonder
if
you
could
ssh
directly
into
it
right
what
happens?
I
don't
know
what,
if
I
haven't,
because
I'm
sharing
the
host
so
but
I
don't
think
any
ports
are
exposed
so.
A
B
A
C
B
Right
like
one
of
the
things
that
yeah
no,
I
like
vs
code,
a
lot
too,
but
so
one
of
the
things
the
eclipse
team,
not
the.
C
B
Really,
but
the
gcc
team
developed
years
ago
was
a
way
in
eclipse
that
you
could
generate
containers
to
do
compilation
on
multi-arch.
B
B
Expensive,
but
you
know
it
was,
it
was
really
interesting,
and
so
because
there
there
are
a
fair
number
of
c
and
c
plus
developers
who.
C
B
Eclipse
or
you
use
ides
at
all,
which
you
know
is
a
little
bit
of
a
shock,
I
think
to
most
people
having
this
kind
of
built-in
tool
that
you
could
just
send
off
your
compilation
into
a
container
was
a
really
neat
little
feature.
I
don't
know
if
it's
still
around,
but
I
do
remember
that
I'm
developing
it
and
talking
about
it
at
a
couple
of
different
conferences,
so
yeah
super
neat,
so
I
really
thought
talking
about
run
labels
and
stuff
like
that,
was
going
to
take
a
lot
longer.
B
I'm
trying
to
think
what
else
we
want
to
show
about.
What's
in
this
container.
A
A
Oh
you
can
do
nmap
and
ncat.
So,
oh
so
like
set
up
like
a
quick
ncat
to
like
output,
a
file
or
something
right.
Maybe
I
don't
know
or
just
nmap
something
from
the
container.
A
Nc
a
lot
to
do
point-to-point
like
bandwidth,
testing
inside
internal
networks,
so
you
can
actually
build
with
dd.
You
can
build
large
files
and
then
use
them
to
like
frequently
test
bandwidth
across
the
network
using
cron
jobs
and
report
that
you
know,
and
you
can
then
graph
that
data
as
a
csv
or
whatever,
and
you
know
present
it.
You
know
in
any.
C
A
B
No,
it
is,
I
think
it
is
yeah.
It.
B
A
True
yeah
yeah,
like
I,
I
would
use
this
so
when
you
know
the
ethernet
over
power
line
stuff
like
I
set
this
up
in
my
house
one
time
my
first
house-
and
I
was
like
I
wonder
if
this
is
a
viable
thing
and
like
if
it
wasn't,
I
was
just
gonna
return
it
to
amazon
right
so,
like
I
set
up
dd
with
like
these
massive
files
like
here's,
a
here's,
a
10,
meg
file,
100
meg
file,
a
gigabit
file,
and
you
know
like
push
these
across
the
network
multiple
times
record
how
long
it
takes
to
do
it
each
time
with
netcat,
and
it
was
just
bouncing
between
two
raspberry
pi's
across
the
powerline
ethernet
thing
and
instead
of
using
you
know,
you
could
do
this
on
your
own
internal
network.
A
Containers,
this
is
pretty
cool
right
right
to
me,
yeah
and,
and
it
turned
out,
it
was
not
very
efficient
for
that
house
because
of
a
circuit
breaker
like
issue,
but
whatever.
A
So
yeah
I
threw
that
out
and
just
went
with
wi-fi
mesh
well.
B
A
B
But
like
I
won't
put
privilege
on
this,
you
know
which
is
fine,
but
I
mean,
I
think,
a
bunch
of
the
stupid
stuff
like
the
fact
that
this
I
don't
think
works.
Oh
they
did
put
ping
in
there.
B
A
A
B
B
All
right
now,
I
bet
that
ps
is
not
going
to
work.
No
ps
does
how
about
ping
there
we
go.
Okay,
so
ping
doesn't
work.
I
think
ip
is
missing.
Yeah
ip
is
missing,
you
know,
so
a
bunch
of
the
basics
are
missing
which
are
in
our
tools
container
right,
so
you
get
ip,
you
get
ping,
you
know
the
number
of
times
I've
tried
to
connect
a
container
and
wow.
That's
interesting.
A
A
B
Oops
well,
whatever
the
point
is
ping
that
one's
a
little
weird,
I
think
it's
because
we
are
so
privileged
that
maybe
we're
blocking
it.
You
know,
and
so
that's
why
it's
actually
having
trouble.
But
the
point
being
is
just
that
even
the
the
basic
stuff
is
not
in
a
you
know,
a
typical
container,
and
this
is
uv
i7
right,
like
they're,
I
mean
you're,
probably
in
most
of
your
scenarios,
gonna
be
running,
something
like
ubi,
minimal
right.
B
You
know-
or
you
know
basically
the
smallest
thing
you
can
get
to
kind
of
minimize-
that
attack
service
like
this
one
doesn't
even
have
yum
installed.
For
example,.
B
You're
unfamiliar
with
this
there's
this
thing
called
micro,
dnf
and
if
you're
in
any
of
the
minimal
containers,
that's
how
you
install
file
or
install
rpms,
and
it's
a
little.
I
think
it's
a
c
program.
But
you
know.
C
A
B
Not
here,
for
example,
so
yeah,
so
that's
that's
kind
of
the
idea
you
know
and,
like
I
said
what
I
wanted
to
introduce
today
was
more
the
idea
that
it's
handy
to
have
you
know,
tool
containers,
basically
when
you're
in
these
environments,
not
only
because
you
know
if
you're
trying
to
troubleshoot
the.
C
B
Of
a
container,
but
also
when
you're,
you
know,
even
if
you
have
a
more
traditional
data
center,
set
up,
whether
it's
bare
metal
or
virtual
machines,
you
know
having
this
handy
container,
which
has
all
these
tools
already
in
it
that
you
can
just
download
as
a
binary
blob
from
somewhere
else
on
your
network
is
super
useful
right.
Yes,
so
you
want
to
talk
about
points,
real,
quick,
look
at
that.
A
Yeah
yeah
yeah.
Let's,
let's
talk
about
some
points,
I
am
actually
setting
up
a
bot
command,
real,
quick,
I'm
just
going
to
set
that
as
a
global
cooldown
and
be
done
all
right
narendev.
You
know
I
have
a
discord
command
that
you
could
run.
I
think.
B
To
the
discord
yeah
yeah,
I
I
was
in
a
a
loopback
problem
there,
so
we
need
more
people
to
submit
for
internet
points
in
rendezvous.
I
was
a
little
surprised
that
you
did
not
submit
for
more
internet
points.
You
know.
So
if.
B
Yeah
but
it's
internet
points
I
mean
like.
B
So
so,
if
you
want
the
points
from
today's
show,
you
can
go,
you
can
just
go
to
the
forum
itself
and
enter
this
code
or
you
can
use
this
handy
link
which
will
essentially
pre-populate
the
code.
There.
A
B
That's
one
answer:
the
other
answer
is
that
if
you
use
the
same
public
name,
I'll
just
go
fix
your
email,
it's
not
like.
We
have
thousands
of
submissions
at
this
point.
B
Third
week,
yeah
yeah,
that's
why
I
keep
using
the
s1e3
whatever
to
remember
so
but
yeah.
So
we
have
d.
I
don't
know
how
to
say
these,
though
d
l
housed,
maybe
and
then
sausage,
crumbs
and
parrots
for
red
hat,
and
I
I
like
paris,
it's
a
very
big
city,
but
it
only
has
one
r.
So
I
assume
it's
not
the
same
paris
but
yeah.
So
here
here
are
cool
internet
points.
B
If
you
want
last
week's
points
or
the
prior
week's
points,
all
you
got
to
do
is
scan
through
the
video.
You
know.
A
Video
video
and
you
can
get
all
of
those
like
for
now
they're
on
twitch.
They
roll
off
in
60
days.
So
basically
for
the
next
two
months.
You'll
have
you
know
well
two
months
minus
three
weeks
or
whatever
you'll
have
those
videos
on
twitch,
but
they'll
always
be
on
youtube
and
langdon.
We
probably
should
get
you
your
own,
like
youtube
like
playlist
thingy,.
A
Yeah,
or
at
least
at
least
at
least,
have
a
good
feeling
about
your
day
for
getting
the
internet
points
right.
A
B
That's
that's
why
I
did
not
list
your
name.
I
apologize.
Well,
I
don't
really,
but
that's
why
you're
you're
not
listed.
A
A
Touch
base
and
discord
with
us
and
yeah
yeah
or
with
langdon.
I
don't
have
access
to
it.
I
don't
think
well,
yeah,
I
do
don't.
I.
B
I
probably
gave
you
privs
whether
you
know
where
it
is
or
not.
I
would.
B
So
yeah,
so
that's
I
don't
know
why?
Don't
we
I
kind
of
feel
like
we
should
wrap
it
here
unless,
anyway,.
A
C
A
Level
up
channel
feel
free,
there's
no
such
thing
as
like
a
a
noob
or,
like
you,
know,
wrong
kind
of
question
to
ask
right
like
come
in
there
ask
your
questions,
no
judgment
like
we.
We
very
much
think.
Oh,
this
is
a
great
opportunity
to
teach
you
something.
Not
oh.
How
do
you
not
know
this
right
like
we
want
you
to
learn
this
stuff?
We
want
to
help.
You
learn
this
stuff,
so
please
feel
free
to
jump
in
and
ask
your
questions.
Well,.
B
Part
of
this,
like
I
mean
I've,
been
using
containers
for
I
don't
know
what,
like
seven
years
now,
six
seven
years,
something
like
that
I've
been
I've
had
servers
in
ec2
since
2006.
B
That
I
know
that
I
think
is
obvious,
because
you
know
I
learned
it
somewhere
and
I'm
happy
to
talk
about
it
and
say:
oh
well,
that's
because
blah
you
know.
A
C
B
And
we're
gonna
start.
You
know
like
so
we're
gonna
play
around
with
some
more
of
this
tool
container
stuff
for
another
couple
episodes
then
we're
gonna
start
looking
at
okay.
How
do
we
start
deploying
those
things
in
ways?
That's
consumable
for
across
the
environment,
you
know
or
across
your
data
center
and
things
like
that
and
then,
if
I
can
work
it
right,
I
can
try
and
get
brent.
Maybe
we
can
get
brent
soon
on
the
show.
B
Exactly
exactly
yeah,
I'm
sure
he
will
he
would
jump
at
the
chance.
We
just
need
to
make
sure
the
timing
works,
but
yeah
so
watch
the
calendar
because,
as
I
get
people
as
I
can
twist,
people's
arm
into
being
interviewed
we'll
get
them
on
the
show,
but
we'll
just
kind
of
slot
them
in
and
bump
whatever
is
there
out?
You
know.
C
B
A
B
A
All
right
all
right,
thank
you,
join
us
next
week
for
the
level
up
hour
same
about
time
same
bat,
channel
later
today,
at
noon,
though
we
have
openshift
commons
briefing
today
is
I
just
typed
it
in
edge
computing
and
industrial
manufacturing
was
wolfram
richter,
which
is
kind.
A
From
yesterday's
openshift
commons
briefing,
so
yeah
it'll
be
super
interesting
to
continue
that
aiml
story
and
edge
computing,
etc.
In.