►
From YouTube: The Level Up Hour (E57): Adding software to RHEL8 UBIs
Description
Do you use a RHEL 8 UBI and need to install additional software but don't know where to start? Are you new to Application Streams in Red Hat Enterprise Linux? In this episode, we'll take a look at the different methods for installing software into a container image and why you would choose one way over another. We'll walk through the steps and commands to install an individual package with different images, and we'll explore RHEL's built-in Application Streams (AppStreams) feature, in which multiple versions of packages are provided. If you’re a RHEL 8 user and want to install additional software into one of the various Universal Base Images (UBI) flavors, be sure to tune in and learn about the different methods and approaches for installing software into your container image.
Learn more: https://www.redhat.com/en/blog/introduction-appstreams-and-modules-red-hat-enterprise-linux
Want to try OpenShift?
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it
Follow us:
Scott McBrien https://twitter.com/stabby_mc
Randy Russell https://www.linkedin.com/in/randy-russell-0312243
Jaafar Chraibi https://twitter.com/ChraibiJc
What is the Level Up Hour?
Every Wednesday at 9am ET we stream live demos on how Red Hat Enterprise Linux (RHEL) users and admins can benefit their organizations and improve their careers by learning how to use containers, Kubernetes, and Red Hat OpenShift.
Learn more at:
https://red.ht/leveluphour
http://red.ht/3ayHlHI
How to participate in the The Level Up Hour:
Watch on YouTube every Wednesday at 9amET
Chat with us on Discord https://discord.gg/5VMVGJt
Check out our GitHub repo https://github.com/level-up-hour/
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
https://www.openshift.com/
https://github.com/openshift/
#RedHat #RHEL #tluh
A
B
B
We
ask
you
to
like
subscribe
and
share
so
that
everybody
knows
that
we're
on
the
air
and
we
have
a
great
episode
planned
today.
I'm
randy
russell
director
of
certification
at
red
hat
and
I'm
joined
by
my
colleague,
scott
mcbrian,
the
legendary
stabby
mick
and
scott.
I
think
we're
going
to
today
shift
a
bit
away
from
the
world
of
openshift
and
kubernetes
to
the
world
of
red
hat
enterprise
linux
in
containers.
So
what
have
you
got
in
store
for
us.
A
A
Could
you
write
an
article
that
that
tells
us
how
to
do
that,
and
so
we're
going
to
start
with
just
like
really
simple
across
the
different
ubis,
because
there's
some
different
tooling
between
them
and
then
I
think
we
should
talk
a
little
bit
more
detail
about
like
that
next
level
of
complexity,
which
is
choosing
application
streams
that
you
want
to
put
into
your
software,
and
I
think
we
can
get
into
what
is
an
application
stream.
How
do
we
manage
it
all
that
kind
of
stuff?
What
live
demo
style?
B
A
So
application
streams
is
a
concept.
It
replaces
an
older
concept
called
software
collections
that
we
shipped
with
red
hat
enterprise
lx7.
So
application
streams
was
newer
to
red
hat
enterprise
on
x8
and
we're
carrying
that
forward
into
red
enterprise.
Linux
9
as
well,
which
you
should
expect
middle
of
this
year,
and
the
idea
is
that
historically,
red
hat
enterprise
linux
has
been
seen
by
developers
as
old
and
crafty
and
doesn't
have
the
right
versions
of
stuff.
A
For
the
latest
things
and
with
red
hat
enterprise,
linux
7,
we
tried
to
resolve
that
with
software
collections
and
8
and
9
were
doing
that
with
application
streams,
and
so
the
concept
is
we
want
to
provide
newer
versions
of
stuff
during
the
lifespan
of
a
red
hat
enterprise.
Linux
release
so
like
way
way
back
back
when,
like
randy,
and
I
work
together
as
field
people,
you
know
we
would
package
up,
say
node.js,
10.
A
and
on
day
one
of
red
hat
enterprise,
linux
dropping
it
had
no
gs10
in
it.
That
was
what
you
got
for
the
entire
duration
of
of
that
rail
release
period,
full
stop,
and
so,
like
eight
years
down
the
road
when
you're
still
working
on
node.js
10.
It
was
really
uncomfortable
right
because
there
were
a
lot
of
stuff
that
that
you
wanted
that
you
couldn't
have
as
a
developer.
A
A
A
A
A
A
Exactly
and
so,
while
we
offer
node.js
10,
12,
14
and
16
on
any
system,
you
can
have
one
of
those
installed
and
if
you
want
a
different
one,
you
have
to
uninstall
the
one
you
have
and
then
install
the
new
one
that
you
want
and
that
that
allows
us
to
do.
Things
like
make
sure
that
the
executables
and
libraries
are
always
stored
in
the
same
places
so
that
you
don't
have
to
use
like
weird
extensions
on
your
executable
calls
or
library
directories
to
make
sure
that
you're
using
the
right
ones
for
the
version.
B
Well-
and
you
know
in
fairness,
if
I
think
historically
about
red
hat
enterprise
linux,
one
of
the
things
that
has
been
very
valuable
about
it
is
that
it,
it
has
historically
done
a
lot
of
support
for
being
able
to
manage
this
huge
number
of
different
projects
and
all
the
different
libraries
and
requirements
that
go
with
that.
But
perhaps
the
idea
of
having
multiple
versions
of
an
application
on
there
was
just
a
bit
more
ambitious
than
than
is
practical
right.
A
A
A
Thank
you,
neil
gamba,
so
yes,
there
are
actually
four
universal
base
images.
Well,
how
universal
can
it
be
if
there's
four
of
them
well,
they're
all
built
off
the
same
package
set,
and
so
that's
where
the
universality
comes
from
right,
but
if
you
want
we
could
switch
to
the
you
know
demo
system
that
I've
got
set
up
and
we
can.
We
can
talk
about
that
a
little
bit
further.
B
A
Okay,
so
I
just
want
to
make
sure
that
everyone
can
see
my
screen.
Randy
looks
good
to
you.
Yeah
awesome
all
right,
so
I
wanted
to
just
go
ahead
and
download
one
extra
ubi,
I've
already
pre-positioned,
some
of
them
already
on
the
system,
and
so
what
I'm
doing
is
I'm
using
the
build
a
command
to
build
from
a
container
we're
going
to
download
from
registry
and
I'm
pulling
down
ubi
micro
in
this
example,
because
I
didn't
specify
a
version,
it
goes
ahead
and
pulls
the
latest
version.
A
A
A
A
If,
instead,
you
were
wanting
something
with
executables
and
didn't
need,
systemd
then
maybe
ubi
would
be
the
one
that
you
choose,
because
it
doesn't
include
that
extra
package
set,
but
those
are
the
four
that
we've
got
and
they
also
vary
in
size.
So
ubi
knit
because
it
has
the
most
stuff
is
the
largest
right.
You
can
see
that
it's
a
253
megs
compressed.
A
I
take
that
back,
that's
uncompressed
ubi
is
235.
Megs
minimal
is
107
megs
and
micro,
uncompresses
38,
megs
30
39
megs,
when
these
are
compressed
they're,
even
smaller,
so
you're
doing
things
like
copying
their
images
to
hosts
or
to
different
nodes
in
your
open
cluster
they're
transferred
compressed.
So
I
think
ubi
micro,
for
example,
is
like
12
or
13
megs
compressed.
So
it's
not
a
lot
of
transfer
time
that
you're
looking
at
there.
A
A
A
A
B
A
B
And
so
it's
you
know,
it
would
behoove
our
audience
to
be
aware
because
note
that
it
doesn't
say:
oh,
but
please
go
and
use
micro
dnf.
It
just
says:
hey
the
executable,
isn't
there,
which
is
in
fact
true,
but
really
what
it's.
What
the
underlying
message
is
is
that
you
need
to
use
this
other
version
of
dnf,
which
is
scalable
dnf.
A
Yeah,
all
right,
so
micro
dnf
works
a
little
bit
differently.
You
can
see
the
output's
slightly
different
than
regular
dnf,
but
it's
it's
essentially
doing
the
same
thing.
It's
going
again,
the
repository
information.
That's
with
this
downloading
metadata
is
and
then
it'll
calculate
the
dependencies
and
then
install
the
software
that
we
said
we
want
to.
B
A
B
A
B
A
A
A
A
A
A
A
A
A
A
A
A
B
Okay,
yeah,
we
actually
did
have
a
little
bit
of
discussion
in
the
chat
sweaty
was
asking
about.
You
know
pointing
out
that
there's
a
small
difference
in
the
size
with
the
micro,
ubi
versus
other
ubis,
and
he
was
saying,
what's
the
what's
the
main
reason
people
use
it
and
neil
had
jumped
in
with,
I
think,
a
pretty
good
answer,
subject
to
your
approval,
mr
mcgrime.
A
The
other
thing
that
you're
doing
is
you're
minimizing
your
your
management
and
risk
footprint
because
you're
not
including
all
these
software
packages,
you
didn't
need.
That
means
that
you
are
not
going
to
have
to
worry
about,
like
maybe
the
pull
kit
cve
that
just
got
released
because
you
know
the
x
windows
is
not
in
there.
You
don't
have
pull
kit
installed,
so
you
don't
have
to
worry
about
managing
that
and
mitigating
that
cbd.
A
So
if
you
look
at
the
red
hat
container
catalog,
there
is
a
python
container
image.
There's
a
node.js
container
image
of
various
flavors
of
node.js.
There
is
a
jdk
container
image.
There
is
a
php
container
image
and
some
of
these
are
built
by
actually
most
of
them
are
built
by
our
runtimes
engineers
right
so.
A
So
when
you
look
at
the
container
catalog
and
you're,
like
oh
yeah,
php,
that's
the
one
for
me!
Awesome
use
it.
But
if
you
look
at
it
and
you
go
that's
more
php
than
I
need
well,
then
you're
back
to
what
we're
just
doing,
which
is
taking
one
of
the
base.
Images
of
your
choice,
choosing
and
then
installing
the
php
bits
that
you
desire,
inside
of
them,
to
build
out
your
development
environment.
A
A
A
I
will
warn
you
that
in
red
hat
enterprise,
linux
9,
if
you
download
and
install
the
beta,
you
will
see
that
there
are
many
less
modules,
because
we're
moving
a
little
bit
away
from
modularity
to
reduce
complexity,
kind
of
like
what
we
did
with
application
streams
in
the
first
place,
all
right.
So
here
we
go.
A
A
So
you
can
see
that
node
doesn't
have
that
version
extension
its
name,
so
I
installed
node.js
earlier
on
my
ubi,
my
regular
ubi.
I
got
version
10.
notice
that
there's
a
little
d
next
to
it.
That's
the
default
version
that
if
you
say,
install
node.js,
that's
the
version
you
get.
If
you
don't
specify
a
version
right
and
then
down
here
in
these
versions
of
pearl
python
is
a
little
bit
special
because
we
can
specify
the
version
in
the
package
name.
We
want
to
install
and
it'll
know
which
one
to
get
all
right.
A
B
A
Yes,
they
can
be
installed
at
the
same
time,
but
the
reason
that
that
works
is
because
we
included
this
version,
information
in
all
the
library
paths
and
all
the
executable
names
right.
So
if
you're
sitting
on
a
box
that
has
python27
and
python39
installed
in
your
shebang
at
the
top
of
your
python
script,
you
actually
make
a
call
to
was
it
user
bin,
python,
39
or
user
bin
python
27
to
make
sure
that
it
gets
the
right
one
and
there
is
a
way
to
make
it
using
the
alternative
subsystem.
A
So
user
bin
python
points
to
one
or
the
other.
But
that's
that's
outside
the
scope
of
our
discussion
today,
all
right
so
notice
that
when
I
say
install
python
39
there,
it
is
installing
python,
three,
nine
and
now
conan
kudos
should
be
happy
that
we
talked
about
python
because
he
loves
him.
Some
python.
B
A
B
A
Ends
up
being
two
or
three
hundred
meg,
because
that's
the
stuff
that
you
needed
in
your
container
payload:
okay,
yeah!
Well,
you
made
the
choice,
yeah
and
the
stuff
that
we
gave
you
as
the
bare
minimum
was
what
30
meg
and
so
of
that
200
or
whatever
30
meg
is
container
overhead.
The
rest
is
actually
your
stuff.
B
A
A
A
A
So
the
the
problem
is
micro
dnf.
If
we
look
at
the
commands,
does
understand
the
concept
of
module,
but
it
only
understands
the
concept
of
module
in
these
three
ways
enable
disable
and
reset,
but
I
said,
module
install
because
I
wanted
to
install
a
modular
software
and
it
doesn't
support
module
install.
A
B
A
B
A
A
And
sure
enough,
in
my
package,
calculations
and
stuff,
it's
talking
about
installing
ruby
version,
three
okay,
so
you
have
a
little
bit
of
a
little
bit
of
extra
steps
to
work
with
when
you're,
using
ebi
minimal
and
the
micro
dnf
implementation.
That
comes
with
it
right
all
right,
so
we're
ready
for
for
my
potential
dumpster
fire
of
micro.
A
A
B
A
A
B
A
B
B
A
But
in
this
episode
we're
talking
about
installing
extra
software
beyond
that,
and
so
when
you're
tracking
your
gpl
source
code,
you
can
get
the
source
container
from
us.
That'll
give
you
your
base
image,
but
then,
when
you
install
ruby
or
you
install
node
or
you
install
apache,
that's
additional
stuff
that
you
need
to
grab
from
red
hat
too.
A
To
then
make
your
full
and
complete
image
source
for
the
image
that
you're
building
out.
So
that's
just
something
to
keep
in
mind
as
you're
deciding
what
to
stick
in
there
and
that's
another
example
of
why
one
might
use
minimal
or
micro
instead
of
the
others,
because
micro
has
just
those
packages
that
you
picked.
Although,
since
we
give
the
source
code
for
all
the
images
pretty
easily
with
a
scopio
yeah,
you
can
really
use
any
of
them
and
then
you
just
have
to
track
your
changes.
B
Right
and
again,
you
know
a
reminder:
it's
posted
in
the
chat
episode
52
delves
much
deeper
into
this,
and
why
you
might
you
might
care
about
this
because
again
you
start
bringing
things
in
into
these
containers.
You
still
want
to
make
sure
that
you
are,
you
know,
gpl
compliant
with
any
gpl
compliant
applications
you're
bringing
in
and
the
ability
to
bring
the
source
in
is
is
actually
very
invaluable
for
that,
so
scott,
can
we
now.
A
A
B
B
Of
see
where
a
trial
and
error
might
be
something
that
is
sometimes
going
to
be
the
case,
but
obviously
you
know
it's
better
if
you
know
initially,
so
what
are
some
things?
What
are
some
things
that
somebody
can
think
through
or
consider
that
would
allow
them
to
make
a
good
choice
early
on
in
the
process.
A
B
A
Right
and
between
micro
and
minimal,
like
you
know,
there's
a
100
or
so
megabytes
of
extra
stuff
in
minimal,
but
you
get
micro
dnf,
which
makes
like
the
building
and
maintenance
and
some
of
the
other
things
a
lot
easier.
So
are
you
willing
to
sacrifice
some
size
and
overhead
to
get
that
easier,
build
and
maintenance
path.
B
A
A
Right,
if,
if
size
and
threat
vector,
are
not
the
overwhelmingly
important
criteria
that
you
use
for,
choosing
something,
then
that
opens
the
floor
to
regular
ubi
and
ubi
net.
I'm
sorry
yeah
ubi
net.
So
with
those
you
get
the
full
implementation
of
dnf.
So
again
it
like
makes
building
and
maintenance
easier.
A
B
That's
actually
very
enlightening,
so
you
know,
I
think
we
we
are
coming
to
the
end
of
the
show.
We
don't
have
any
outstanding
questions,
and
so
I
would
just
ask
everybody
to
again
like
subscribe
and
share
so
that
everybody
knows
that
we're
here
we
have
moved
to
a
bi-weekly
schedule,
and
so
we
will
see
you
again
two
weeks
from
today
again,
thank
you
for
joining
level
up
hour,
and
we
will
see
you
in
two
weeks
thanks
folks
and
thanks
scott.