►
Description
Building the Perfect Tools Container (toolbox)
Have you used the `toolbox` container (formerly fedora-toolbox)? Come learn about it and what you can use it for.
Learn more at https://red.ht/leveluphour
A
B
B
But
there's
as
always
a
lot
going
on,
so
we
have
a
lot
of
interesting
stuff
going
on
in
the
technology
world
as
well.
Yes,
and
today,
we're
gonna
talk
a
little
bit
about
kind
of
a
completely
different
style
or
kind
of
completely
different
approach
to
the
you
know,
the
tools
container
that
we've
been
talking
about
so
in
past
couple
weeks,
right.
A
A
Yeah,
okay,
sorry
folks,
it's
hard
to
manage
a
live
stream
first
thing
in
the
morning:
the
joys
of
it,
though
it's
fun
stuff,
all
right.
So
yeah
we've
been
talking
about
using
containers
in
lieu
of
like
installing
a
bunch
of
packages
on
your
system
to
do
some
troubleshooting
and
then
uninstalling
them
later
kind
of
thing.
B
Well,
and
not
only
can
you
kind
of
think
about
your
own
thing
like
what
do
you
like
to
use?
You
know
we
were
kind
of
talking
about
mtr
last
week,
but
if
you're
using
other
people's
tools,
containers
like
the
ones
from
red
hat
so
like
support
all
tools,
they
there
may
be
tools
that
you've
never
heard
of
before
in
there,
which
then
says
to
yourself.
Why
is
this
person,
including
this,
because
they
clearly
know
what
they're
doing
and
that's
why
they
decided
to
put
it
in
this
container
right.
B
B
Yeah
exactly
exactly
so,
I
highly
encourage
anybody
who's
here
or
whatever
to
check
out.
You
know,
obviously
the
prior
shows,
but
you
know,
check
out
rel
tools
for
yourself
check
out
support
tools
for
yourself
and
if
you
aren't
familiar
with
any
of
the
things
that
are
kind
of
installed
as
as
part
of
that
tool,
obviously
not
the
stuff.
That's
generally
not
the
stuff
that's
installed
by
default,
but
the
stuff
that
they're,
adding
onto
the
container
because
remember
the
container
base,
of
course
includes
some
binaries.
C
C
B
B
B
B
B
Actually
I
will
pitch
this
because
I
think
it's
interesting
red
hat
relatively
recently
came
up
with
two
new
fonts
one,
that's
kind
of
your
your
big
text,
font
and
one
that's
the
content
font
for
things
like
slides,
but
also
like
documents
and
stuff
like
that,
but
they're
both
open
source
and
they're
in
public,
and
they
are
called,
I
think,
intuitively
enough,
like
red
hat
display
and
red
hat
text.
If
anyone
is
interested
in
acquiring
those
fonts,
because
they're
open
source
and
they're
for
free.
B
B
Want
to
use
containers
as
part
of
their
normal
work
life
and
then
maybe
talk
a
little
bit
from
there
about
how
once
you
start
using
containers,
why
orchestration
starts
to
become
important,
and
why,
then
you
know
as
an
orchestration
platform.
Openshift
can
be
a
good
one
for
that
and
in
a
couple
of
episodes,
I
think
we're
going
to
start
to
talk
more
about
that
right.
Now,
we're
still
kind
of
going
through
kind
of
the
various
ways.
B
B
A
B
B
B
B
B
A
B
B
A
B
And
so
there
have
been,
as
with
all
things
right,
a
number
of
attempts
to
to
try
to
resolve
this
problem.
So
a
few
years
ago,
six
or
so
the
like
this
was
core
os
when
it
was
the
company
core
os
right.
But
I
know
red
hatters
contributed
to
this
toolbox
and
there
were
a
bunch
of
red
headers
who
were
at
core
os.
B
So
I'm
not
sure
where
exactly
the
overlap
was,
but
both
groups
started
to
use
this
kind
of
really
complicated
shell
script,
which
I
think
is
this
guy
to
launch
a
container
that
was,
as
we've
talked
about
in
the
past
a
you
know,
a
container
that
you
reuse,
that
you
know
you
kind
of
just
install
on
your
machine
and
then
you
kind
of
keep
coming
back
to
it.
Right
so
often
referred
to
as
a
pet
container,
but
this
container
is
specifically
for
bringing
all
your
tools
with
you.
B
B
B
B
Emacs
versus
vi,
so
we
will
talk
about
that,
but
it's
a
sub
tool
of
the
systemd
suite
that
will
actually
launch
a
container,
and
so,
but
it
was
a
little
bit
more
as
a
competitor
for
like
a
better
term
to
true,
not
actually
a
competitor
to
like
docker
or
rocket
or
or
podman
so
systemdnspawn
is
still
around.
You
can
still
use
it
and
some
things
do
still
use
it.
B
This
is
where
you
find,
if
you
want
to
do
containers
that
launch
on
boot,
for
example,
because
one
of
the
problems-
this
is
less
true
with
podman,
but
I'm
not
sure
if
it's
completely
solved
but
with
docker.
The
problem
is
that
it's
a
it's
running
a
background
process
right
in
order
to
launch
a
container
at
boot.
You
need
to
wait
for
the
background
process
to
launch
then
launch
your
container
right,
which
makes
sense.
A
C
B
So
I
think
podman
in
some
ways
is
inspired
by
a
combination
of
systemdnspawn
and
and
docker
in
a
sense
so
yeah.
So
that
was
a
lot
of
story,
but
so
to
give
you
an
idea
so
toolbox,
you
know.
Is
this
thing.
However,
what
I
wanted
to
point
out
is
that
let's
do
sudo
yum
info
toolbox,
and
this
is
where
it
starts
to
get
a
little
confusing.
A
A
B
B
B
A
C
A
B
C
A
B
B
A
B
Video
game,
oh
gosh,
so
yeah
so
and
then
the
run
part.
This
is
where
I
would
need
to
go.
Look
it
up,
but
the
run
part
I
think,
is
exclusive
to
podman
and
is
not
the
same
code
as
like
in
cryo,
for
example,
but
I
think
there
was
some
effort
to
make
it
the
same
or
whatever.
So
at
that
part,
I'm
a
little
personally,
I'm
a
little
confused
about
and
keep
it's
one
of
those
things
I
keep
meaning
to
go.
Look
up,
however,
our
digression
into
podman.
B
Yeah,
no
worries.
Sorry,
so,
basically,
that's
that's.
What
build
this
for!
That's
the
scopio
is
for
is
just
they're
the
independent
pieces
in
case
you
need
those
independent
pieces
for
some
reason,
but
if
you
get
podman,
you
have
the
same
functionality,
but
I
don't.
I
can't
remember
how
the
dependencies
work,
whether
you
actually
get
the
now.
We
have.
B
But
there's
a
dependence
one
too,
which
I'm
blanking
on
how
to
do.
But
whatever
the
point
being
is
that
when
you
install
podman,
you
may
not
get
build
up
because
go
code
right,
which
is
it's
all
compiled
together,
and
so
you
know,
arguably
whether
bundling
is
a
good
idea
or
not
that's
another
nice
fun
religious
war
that
you
can
go
and
check
out
on
your
own
time,
but
the
terminology
for
it
is
you
know.
Basically,
they
also
call
it
vendoring,
a
really
good
example
of
this.
B
Actually,
if
you've
ever
used,
vagrant,
which
I
highly
recommend,
if
you've
never
tried
it
check
it
out,
it's
really
handy,
but
vagrant
had
a
lot
of
problems
with
getting
lots
of
bug
reports
from
different
platforms
right
so
different
linuxes
for
mac.
You
know
for
windows,
and
so
they
started
doing
what
is
a
no
no
in
the
linux
community,
which
is
called
vendoring
or
bundling
where
they
include
the
ruby
they're
using
in
the
vagrant
package
itself,
it's
separated,
but
they
manage
what
ruby
you're
getting
the
problem
with.
B
So
with
the
advent
of
go
and
containers,
some
of
that
bundling
argument
has
gone
the
other
direction
because
you
know,
is
it
better
to
just
have
one
binary
that
has
all
the
things
you
need
in
it
or
you
know.
Do
you
need
all
these
other
libraries?
So
basically
that's
the
that's
the
struggle,
so
yeah
long
story
short.
I
don't
remember
if
bulda
is
actually
distributed
separately
from
podman
when
you
install
podman
and
is
it
using
to
build
a
binary
underneath
or
is
it
bundled
into
the
code
of
the
pod.
C
A
And
how
to
do
it
and
certain
ways
of
doing
it
and
I'm
friends
with
sam
boyer
here
in
the
detroit
area.
He
knows
all
about
dependency
management
and
he
has
very
deep
opinions
about
it
and
there's
very
deep
opinions
from
other
people
in
the
go
community.
It
is
wow,
it's
just
a
very
deep,
deep,
deep
subject.
B
B
B
You
know
it's
a
it's
a
it's
a
viewable
blob
like
you
can
explore
the
blob,
but
you
get
the
whole
set
of
the
run
time
for
the
operating
system
as
one
image,
and
it
also
atomically
updates
as
one
image.
So
in
other
words,
you
can
never
yum
your
way
into
a
unbootable
system,
for
example,
at
least
in
theory.
B
People
are
talented,
so
you
know
they
can.
They
can
always
find
a
way
to
break
their
computers.
Problem
with
silver
blue
is
is
kind
of
like
the
problem
we've
been
talking
about,
which
is
that
okay,
you
don't?
You
literally
cannot
use
yum
or
dnf
on
the
command
line
it
just
it's
just
not
installed,
and
the
reason
is
because
you
have
to
layer
on
packages
onto
this
image
blob
you
got
so
it
has
to
kind
of
work
quite
differently.
B
So
in
order
to
get
around
that
problem
and
to
give
a
familiar
experience
to
anybody
who's
using
silver
blue,
but
as
like
a
programmer
or
as
an
admin,
this
guy
devarshi
ray,
who,
I
think,
we're
going
to
try
and
have
on
the
show,
soon
developed
this
toolbox,
and
it
was
also
a
big
janky.
Shell
script,
a
really
big
janky
shell
script.
Originally
like
thousands
of
lines.
Oh.
B
A
B
God,
and
actually
that's
an
interesting
thing
to
take
a
look
at
is
if
we
can
quickly
find
the
docker
file,
but
maybe
we'll
get
to
it,
so
so
this
is
kind
of
the
next
level
toolbox.
So
same
idea,
however,
this
one
kind
of
comes
with
a
stronger
feature
set,
and
so,
while
I
don't
have
it
installed
in
rel,
I
was
going
to
show
it
to
you
a
little
bit
of
fedora
just
for
ease
of
discussion,
but
you
so
you
can.
You
can
theoretically
get
it
for
rel.
I
was
thinking
we.
B
B
In
the
same,
get
tree
also
be
maintained
for
enterprise,
linux,
and
so
enterprise
linux,
you
know,
is
basically
referring
to
rel,
centos,
scientific
linux
and
basically
any
other
derivative
of
rel
right.
So
as
as,
hopefully,
everyone
here
knows
like
centos
is
a
downstream
of
route,
and
so
we
talk
about
upstream
and
downstream.
What
we
mean
is
like
you
know:
the
packages
are
created
in
the
upstream
right.
The
code
is,
you
know.
B
We
talked
about
blender
a
couple
weeks
ago,
someone
there's
a
blender
community,
they
build
code
and
then
a
linux
distro
comes
along
and
says:
okay,
we're
going
to
package
that
for
this
linux
distro,
so
the
upstream
for
the
linux
distro
is
blender
itself,
then
fedora,
for
example,
picks
it
up
packages
at
rpms
and
they
create
a
binary
so
that
you
can
install
it
on
your
linux
system.
But
then
they
have
downstreams.
So
rel
is
considered
a
downstream
of
fedora.
So
a
lot
of
things
that
are
maintained
in
fedora
are
then
recreated
for
rel.
B
With
all
the
same
code,
or
at
least
all
the
code
is
public.
Sometimes
there
will
be
special
patches
for
rel
because
they
want
something
to
be
more
enterprise
ready
or
they
don't
want
to
support
something.
So
they'll
take
out
a
feature
or
something
like
that,
but
all
of
that
is
public
and
accessible
because
gpl,
but
rail
is
a
downstream
of
fedora.
B
B
I
thought
the
new
toolbox
was
there,
but
I
guess
not
so
it
hasn't
been
packaged,
at
least
in
either
of
these
two
sets
of
repositories
for
rail.
At
this
time
it
may
be
packaged
somewhere,
and
I
just
don't
know
where
it
is
so
we
can.
You
know
we
can
either
try
to
go,
find
it.
We
can
also
try
to
build
it
and
see
if
we
can
get
it
to
work
and
see
what
happens
all
right,
any
questions
so
far,
should
we
continue
on
our
merry
way.
A
B
B
B
B
Yeah,
I
just
wonder
what
what
led
them
to
rust
and
to
begin
with
right,
okay,
so
toolbox,
all
right.
So,
unlike
some
of
the
other
tools,
containers
we've
been
talking
about
toolbox,
and
I
have
this
weird
bug
right
now.
That's
something
to
do
with
how
I
have
set
up.
That's
why
you're
seeing
this
warning,
so
I
just
haven't,
figured
out
what
it
is
yet.
B
B
Yeah
it's
something
because
I
use
t-much
all
the
time,
and
so
it
has
to
do
with.
Basically
my
keys
getting
passed
around
correctly
right,
which
I've
haven't
been
able
to
quite
figure
out
what
the
deal
is,
because
gnome
has
their
own
key
ring,
which
sits
kind
of
on
top
of
ssh
agent,
which
kind
of
or
something
I
don't.
B
A
B
Yeah,
but
I
bet
I
already
have
netstat
so,
but
the
point
is,
is
that
you
can
install
things
directly
in
this
container
that
you
don't
have
on
the
base
os,
and
so
then
you
can
carry
those
around
in
your
toolbox
and
have
you
know
kind
of
that
functionality.
But
again,
let
me
just
try
to
think
how
to
show
this
the
best.
So
that's
gonna,
that's
gonna
cook
for
a
second
and
then
what's
one
thing
is
kind
of
interesting.
C
B
Oh,
I
think
it's
the
latter
okay,
but
I
don't
actually
know
how
it
works.
It's
one
of
those
things
I
it's
like
on
the
list
of
things.
I
need
to
figure
out
how
it
actually
works
and
find
interesting,
like
I'm,
not
sure
which
way
I
like
better,
because
sometimes
you
want
to
be
back
on
the
bass
os
and
you
know
so
I
I
can't
decide
whether
I
like
it
or
not,
but
if
we
take
a
look
at
images
wow,
I
have
a
lot
of
container
images.
B
B
B
B
B
A
B
A
B
Right,
oh
yeah,
so
this
is
actually
earlier
than
you
guys
just
saw
now
so
it'll.
Actually,
so
I
can
do
one
of
two
things
I
can
do
enter,
which
will
basically
go
and
do
the
create
step
and
then
enter
or
if
it
already
exists.
It'll
just
drop
me
into
the
toolbox,
but
what
I
wanted
to
show
a
little
bit
was
how
that
works.
So
it
goes
and
actually
grabs
the
image
itself
and
that's
why
I
have
this
fedora
toolbox
here
by
default.
B
B
Exactly
exactly
so
vice
versa,
yeah
right.
So
that's
super
handy
if
you
want
some
feature
of
some
binary
that
maybe
doesn't
exist
on
the
version
you're
on
so
that's
kind
of
interesting,
but
what
I
wanted
to
also
show
you
is,
as
we've
been
discussing
in
the
past,
is
we
can
info
right?
No
inspect.
You
know.
Oh,
I
figured
out
why
I
have
such
a
mental
block
about
it
is
because
the
in
podman
inspect
of
the
yum
world
is
info.
B
A
B
B
B
So
well,
that's
a
bummer.
I
totally
thought
it
still
used
it,
but
yeah
I
don't
know.
I
thought
I
think
it's
cool.
So
for
some
reason
it's
not
loving
this
idea
and
it
does
not
seem
I
mean
from
doing
inspect.
It
doesn't
seem
to
have
a
run
label.
So
my
guess
is
that
the
go
code
now
directly
interfaces
with
podman
api
to
launch
the
container,
which
is
fine.
I
just
think
it's
less
cool
because
I
really
like
the
run
label
concept.
I
think
that
was
a.
I
think.
That's
really
interesting.
Very.
A
B
Net
tools
so
yeah,
but
point
being,
is
that
so
toolbox?
You
kind
of
the
idea,
is
you
add
a
bunch
of
your
stuff
in
here
and
then
you
have.
You
know
kind
of
that
tool
set
that
you
carry
around,
except
that
now
you
have
a
persistent
binary,
a
persistent
container
image
and
you
know
cool
things
can
can
happen
from
there.
B
The
thing
that's
a
little
bit
different
about
toolbox
versus
rail
tools
or
support
tools.
Is
you
know,
so,
first
of
all,
it's
not
meant
to
be
used
on
its
own
right.
You're
meant
to
go
into
it
and
install
the
things
you
might
need,
which
is
a
little
bit
different
than
support
tools,
which
is
kind
of
meant
to
be
coming
to
you
out
of
the
box
set
up
right.
B
The
other
thing
that's
a
little
different
is
that
you
can
be
more
declarative
about
your
toolbox,
and
so,
while
I
haven't,
I
don't
have
a
great
job
of
this.
What
you
can
do
is
you
can
actually
declare
your
toolboxes,
I'm
not
sure
if
that's
the
right
way
of
saying
it.
But
if
you
take
a
look
here,
you
can
actually
say
I
want
to
use
this
container
and
I
want
to
I'm
sorry.
I
want
to
use
this
image
and
I
want
to
make
it
this
container
and
the
reason
you
might
want
to
do.
B
C
A
A
B
So
so
I
never
want
the
directory
I'm
working
in
to
be
the
one
that
is
the
get
repo
right.
I
always
want
it
underneath
it
because
I
might
have
other
ancillary
stuff.
Maybe
I
collect
some
some.
You
know
notes
or
something
like
that,
that
I
don't
want
in
the
git
repo,
so
I
end
up
calling
it
whatever
it
is.
I
always
end
up
calling
it
dash
stuff,
because
you
know
I
need
a
name,
and
you
know
I
can't
just
call
it
ansible
scripts
right,
because
that
would
be
the
git
repo.
B
B
A
B
C
B
Know
it's
like.
I
have
to
go
back
and
like
change
things
to
be
packaged,
you
know
versus
using
dns
or
whatever
yeah
so,
however,
sideways
pitch
here
highly
recommend.
How
do
I
and
task
warrior
if
you've
never
checked
those
out?
How
do
I
is
a
command
line,
interface
for
searching
stack
overflow,
which
is.
B
B
Part
of
the
reason
I
don't
like
how
this
is
set
up,
for
example,
is
that
I
actually
made
a
task
warrior
container
itself,
so
I
run
task
lawyer
as
a
container,
and
so
that's
what
I
mean
is
like
some
of
sometimes
my
you
know
my
ansible
scripts
have
to
catch
up
to
my
my
containerization
of
all
the
things
so
yeah.
So,
but
if
we
take
a
look
in
brenda.
B
B
A
B
B
B
So,
let's
see-
and
oh
I
also
like
trash
cli,
which
keeps
me
from
accidentally
deleting
entire
directories,
so
so
yeah.
So
here
is
the
the
ansible
script
that
I
run
on
startup
of
a
toolbox.
So
basically
I
go
and
I
go
and
install
ansible
in
the
toolbox
and
then
I
go
and
run
this
toolbox
playbook
and
then
I
podman
commit
the
image
that
is
or
the
container
that
is
resultant
and
has
a
new
image
called
my
toolbox.
B
B
A
A
B
A
Coming
in
from
discord
your
new
codes,
your
street
sweet
internet
points,
narendev
linux,
expo
stacy
and
dnl
housed.
Thank
you
all
for
participating.
Thank
you.
Everyone
for
participating,
your
engagement,
really
matters
to
us,
and
we
really
appreciate
everything
that
you
bring
to
the
channel,
because
your
questions
help
us
help.
You.
B
B
A
A
B
A
B
To
that,
I'm
throwing
it
in
there
right
now
is,
if
you
make,
if
you
add
an
issue
or
if
you
submit
a
pr,
for
example,
if
you
want
to
add
your,
you
know,
add
commentary
to
the
show
notes,
for
example,
or
you
want
to
add
some.
You
know
new
way
of
doing
something
that
I
did
you
know
make
a
pr,
but
so
you
get
internet
points
for
those.
What
I
realized
kind
of
early
this
morning
is
that
the
list
of
ways
you
can
get
internet
points
is
not
posted
anywhere.
B
B
A
B
B
B
You
know
submitting
prs
also
inter
internet
points.
Repeated
attendance
at
the
show
is
also
internet
points,
in
fact,
there's
a
riser,
so
there's
a
riser
on
the
points
that
you
get
for
attending
the
show.
If
you
attend
more
than
one
so
first
off,
that's
how
narendra
in
fact
can
get
to
500
points
with
this
being
only
the
fifth
episode
right,
because
each
episode
is
worth
100
points.
A
C
B
B
Well,
yes,
and
no
I
mean
you
know
what
I'm
not
a
fan
of
is
github
has
kind
of
locked
it
up
as
a
as
the
police
right.
But
you
know
I
am
much
more
confident,
so
I
I
actually
teach
a
class
at
boston
university
right
as
well
as
do
a
lot
of
work
with
the
students
there
and
you
know-
and
I
have
some
projects
going
on
there
and
I
have
to
hire
pretty
regularly.
To
put
you
know,
students
onto
those
projects.
C
B
Right,
like
I
spent
I
spent
15
years
as
a
software
consultant.
I
think
I
had
one
project
in
that
entire
time
right
where
any
of
the
ip
could
be
public
at
all,
because
it
just
it
wasn't
in
my
business
right
to
like
sell
open
source
into
this
organization.
I
was
trying
to
sell
hours,
you
know,
and
so
as
a
result,
even
though
it
was
a
lot
of
those
projects
very
misguided
to
keep
it
super
secret,
that's
what
they
did
and
someone
asked
what
the
internet
points
are
used
for.
C
B
Meaning,
but
so
that's
why
it's
kind
of
gone
to
internet
points
versus
internet
karma,
but
there
is
a
you
know
like
questionable
construct
of
not
being
very
inclusive,
to
use
a
term
like
karma
when
you're
not
really
talking
about
their
religion.
So
that's
why
we
call
it
internet
points
and
when
and
so
as.
B
B
A
B
A
B
C
A
A
A
A
A
B
B
C
A
B
Yeah
so
I
kind
of
wanted
to
you
know
I
went
through
kind
of
how
it
works
and
why
it
works,
and
you
know
maybe
we'll
spend
another
episode
making
it
work
on
rel,
or
I
will
talk
internally
to
people
about
why
it's
not
available
for
rail
right
now,
because
I
think
it
should
be
personally,
but
you
know
we
can.
We
can
try
to
go
figure
that
out.
The
other
thing
that
I
had
proposed
talking
about
today
was
also
app
streams,
but
I
think
that
probably
just.
A
B
A
B
A
B
All
right
so
as
a
brief
introduction
to
af
streams
or
upstream
referred
to
as
modularity.
This
is,
in
some
ways
a
very
similar
problem
to
the
one
we
were
talking
about
with
bundling
it's
also
a
similar
problem.
To
you
know
I
kind
of
mentioned,
like
you
could
use
a
tool
f32
toolbox
on
an
f30
machine.
B
B
So
if
you
need
oh
boy-
postgres,
for
example,
a
very
popular
database,
yes
on
rel,
traditionally
with
a
distribution
or
fedora
or
whatever,
there's
only
one
version
by
design,
because
that's
what
it
means
to
be
a
distribution.
So
in
order
to
upgrade
postgres,
for
example,
you
have
to
move
your
entire
operating
system.
B
A
B
B
I
don't
have
a
good
link
to
here's
all
this
talks,
I've
given,
but
you
know
so
in
fedora,
obviously
so
in
fedora.
What
tends
to
happen
is
actually
you
you
want
to
upgrade
the
operating
system,
but
you
don't
want
to
change
your
application
bingo.
So
you
want
to
get
f32,
but
your
application
is
still
using,
let's
say
node.js
10,
which
is
now
not
in
f32.
B
B
A
B
B
B
What's
super
cool
about
using
an
app
stream
or
a
module
inside
a
container
is
that
you
can
also
have
say
a
single
docker
file
or
container
file
and
then
depending
on
what
you,
basically,
how
you
feed
it.
So,
basically,
if
you
do
we'll
talk
about
it
more
in
detail,
but
I
can
have
a
single
container
file
and
build
it
with
multiple
versions
of
whatever
my
baseline
is
okay,
so
like,
for
example,
I
have
an
application
that
runs
on
node.js.
B
I
want
to
test
it
with
node.js
10,
11
and
12.,
but
in
order
to
to
do
that,
normally
I'd
have
to
write
a
custom,
docker
file
per
version
of
node.js
using
app
streams.
I
can
use
the
same
docker
file,
give
it
a
slightly
different
flag
and
it
will
get
different
versions
of
node.js,
thereby
taking
out
one
of
the
risk
factors
of
changing
anything
when
you're
doing
testing.
B
So
what
scares
me
right
is
making
any
modifications
to
my
configuration
when
I
want
to
claim
that
this
thing
is
going
to
work
on
node.js,
11
and
12..
So
if
I
can
remain,
if
I
can
keep
all
of
my
configuration
the
same,
I
can
be
way
more
confident
that
the
tests
I'm
running
are
true.
This
making
sense,
yes,
okay,.
A
B
B
Yeah
point
being
it's
we're
starting
to
try
to
use
the
term
container
file,
because
what
we're
building
is
an
like
an
oci
compliant
container.
We
are
not
actually
building
a
docker
container,
and
so,
while
an
oci
compliant
container
will
run
in
docker,
it
will
also
run
in
podman
or
run
in
whatever
other
runtime.
That
supports.
A
C
A
A
C
B
A
It's
actually
surprisingly,
cool
how
we
do
the
dns,
but
anyways.
I
could
do
a
whole
episode
on
that
yeah.
This
is
the
new
twitch
landing
page
put
to
us
put
together
by
us
by
the
way,
and
only
dan,
russo
yeah.
That
looks
interesting
right,
like
you
could
just
go
to
this
page
and
watch
us
live
at
any
point
in
time
and
here's
links
to
all
of
our
common
shows
the
the
youtube
archive.
Is
there?
Yes,
it's
a
long
list,
because
we've
done
hundreds
of
episodes.
A
A
B
A
And
the
way
it
has
embraced
this
channel,
so
thank
you
very
much
everybody
for
just
watching
for
participating
and
being
engaged
right
like
this.
This
whole
channel
would
be
nothing
without
you.
So
thank
you
very
much
for
joining
us
today
and
joining
us
every
week
and
earning
your
sweet,
sweet
internet
points
and
interacting
with
us
and
just
being
accepting
of
learning
new
things
right
like
that
is
a
huge
part
of
our
life.
We
have
to
learn
new
things
as
technologists.
We
can't
be
stuck
on
our
ways
anymore.
A
C
A
Yeah,
so
we
got
today
so
yesterday
on
openshift
commons,
they
did
a
thing
on
aiops
from
ibm.
So
today,
on
openshift
commons,
we're
bringing
in
zach
berry
from
red
hat
to
talk
about
devops
versus
ml,
ops
versus
aiops
and
that'll
be
an
interesting
discussion
in
which
I
might
get
involved
because
you
know
normally,
I
try
to
just
like
produce.
Diane's
show
and
kind
of
stay
in
the
background
and
just
you
know,
learn
new
things
and
absorb.
A
A
A
In
the
fast
lane,
but
let's
see
tomorrow,
we
have
devnation
with
a
tech
talk
talking
about
hacking,
istio
with
webassembly
modules,
that's
pretty
cool,
and
then
we
have
a
live
stream
on
adding
openshift
workers
post
install
with
our
friend
the
one
and
only
christian
hernandez,
and
then
friday,
we've
got
friday
morning.
We've
got
a
fun
stream
on
how
to
get
started
with
quay
container
registry,
which
might
be
very
useful
for
everybody
out
there.
This
week
after
docker's
latest
announcement
on
their
life,
cycling
of.