►
Description
Can you produce source code for your open source based software container? If you're doing open source containers and don't stay mindful of GPL, you're doing it wrong. In today's episode, we'll discuss why developers should care about the source of their images and present a general overview of GPL requirements to help you understand basic licensing considerations when developing container images. We'll also look at the history of open source and GPL, what it looks like when working with containers and walkthrough pulling down a source container for UBI. So join us to learn more about GPL and examine why the provenance of your container image is important.
Disclaimer: The information provided in this program does not constitute business or legal advice and does not create any attorney-client or other legal relationship between the viewer and any of the presenters or producers of the program or the sponsors of this channel.
Learn more: https://www.redhat.com/en/blog/gpl-cooperation-commitment-and-red-hat-projects
https://www.gnu.org/licenses/gpl-faq.html
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 #OpenShift #tluh
A
Good
morning,
good
afternoon
and
good
evening,
as
the
case
may
be,
wherever
you
are,
you
are
joining
us
for
the
level
up
hour,
where
we
consider
all
things,
containers,
kubernetes
and
openshift-
glad
to
have
you
here
today,
please
like
and
subscribe
and
share,
and
let
everybody
know
that
we
are
on
the
air
talking
about
containers,
kubernetes
and
open
shift.
So
I'm
randy
russell
the
director
of
certification
shout
out
to
all
the
red
hat
certified
professionals
out
there
and
I
am
joined
by
stabby
mick,
scott
mcbryan,
the
evil
winged
minion
scott.
A
A
C
B
Well,
I
think,
before
we
can
get
into
like
why
it
might
be
a
thing
and
especially
for
the
container
ecosystem
that
that
we're
starting
to
see
kind
of
crop
up
all
around.
We
probably
should
first
talk
about
like
what
is
the
gpl
and
what
does
that
mean
if
you're
using
gpl
software,
so
I'm?
I
know
that
you
are
also
familiar
with
this,
because
we've
we've
worked
at
red
hat
for
a
minute,
but
the
gpl
is
the
new
public
license
most
of
the
software
that
we
ship
with
things
like
red
hat
enterprise.
B
Linux
are
covered
under
the
gpl
version
too,
but
not
everything.
There
are
a
variety
of
other
open
source
licenses
as
well,
and
those
occasionally
are
also
shipped
with
red
hat
products.
But
the
big
thing
with
open
source
licensing
is
that
you
are
obligated
to
provide
the
source
code
for
any
binary
stuff
that
you
ship
right.
So,
for
example,
I
work
on
the
red
hat
enterprise,
linux
team
and
there's
a
lot
of
open
source
software
in
the
red
hat
enterprise,
linux
distribution.
A
Right
well-
and
it's
always
informative
to
actually
take
a
look
and
see
what's
in
there,
if
nothing
else,
because
you
start
to
see
what
the
value
is
that
red
hat
ads,
you
know
there.
I
think
there
is
sometimes
the
impression
that
that
you
know
hard
archive
out
there
of
source
code
is
what
just
automatically
goes
into.
A
You
know
one
piece
of
technology
or
another,
and
it
couldn't
be
further
from
the
truth.
If
you
think
about
something
like
the
the
linux
kernel,
for
example,
we're
probably
into
the
I
don't
know
hundreds,
maybe
thousands
of
patches
at
this
point
that
get
applied
to
get
applied
to
that
kernel,
to
make
it
work
effectively
for
our
users.
So
you
know
having
access
to
the
source
is
at
the
very
core
of
open
source.
A
It's
that
you
get
to
see
the
entire
story
start
to
finish
what
you
know,
how
it
works
and
anything
that's
been
done
to
modify
it,
and
you
have
this
commitment
as
scott
says,
to
to
share
it
to
others,
so
that
they
have
the
same
advantage.
That
you
did
that's
sort
of
the
philosophical
point
right
is
that
the
gpl,
unlike
some
other
software
licenses,
does
have
this
this
part
that
says,
if
you
share
a
binary,
you
have
to
share
the
source,
and
it
has
to
include
the
things
that
you
might
have
changed
right.
B
B
So
we
used
to
describe
it
with
something
we
call
the
cake
analogy
right,
which
is:
if
you
went
to
a
bakery
and
you
bought
a
cake
if
it
was
an
open
source
cake.
The
baker
would
also
have
to
provide
the
recipe
for
that
cake
upon
request
right,
so
you
pay
for
the
cake,
but
you
get
the
recipe
that
you
can
then
buy
the
ingredients
and
bake
at
home.
You
could
even
make
adjustments
to
it.
B
You
know
adding
nuts
or
something
like
that,
but,
as
you
mentioned,
the
the
open
source
license
also
covers
changes.
So
if
you
brought
that
cake
to
your
friend's
house
that
had
the
nuts
in
it
and
your
friend
says
hey,
this
is
really
great
cake
and
I
have
the
recipe
you're
obliged
to
give
it
with
the
addition
of
the
nuts
that
you
added
to
that
recipe,
so
that
that's
kind
of
how
how
open
source
works
right.
A
Thought
on
this
is
that
you
know
the
you
know.
The
gpl
is
the
creation
of
the
free
software
foundation,
and
you
know
it
is
something
that
is
voluntary
in
the
sense
that
if
somebody
creates
a
an
open
source
software
project,
that's
a
choice
that
they
make
to
share
it
under
the
gpl
and,
of
course,
we've
all
benefited
greatly
by
all
the
many
projects
out
there
that
have
adopted
this.
A
C
B
Oh
so
again,
this
is
a
place
where
we
are
not
lawyers.
We
can
only
look
at
kind
of
some
historical
things
of
how
it's
been
handled
in
the
past,
so
there
have
been
vendors
that
have
have
not
through
accident
or
intentionality.
I
don't
know
which
not
provided
the
source
code
and
oftentimes.
What
will
happen
is
first,
there
will
be
repeated,
repeated
requests
for
it
and
when
those
aren't
met
there's
you
know,
there's
probably
some
public,
shaming.
That
happens
right.
C
A
Right
right,
so
so
there's
a
couple
of
things:
there
there's
there's
sort
of
reputational
risk
and
of
course
all
organizations
and
companies
are
highly
sensitive
to
this
now
in
in
the
social
media
age.
You
know
that
is,
that
is
the
thing
that
you
don't
want
is
to
be
trending,
negatively
everybody's
saying
that
you,
you
know
you
fail
to
honor
the
the
gpl
or
whatever
it
is
that
they
might
be
saying
about
you
right.
A
That's
one
part
and
reputational
risk
is
actually
very
highly
valued
and
very
you
know
at
a
very
important
risk,
but
then
the
other
is
that
there
are
potential
legal
actions
that
can
also
follow.
So
this
is
all
kind
of
scary
stuff,
but
historically,
there's
been
a
pretty
straightforward
way
of
of
dealing
with
with
providing
the
source
in
in
red
hat
products.
Let's,
let's
kind
of,
simplify
and
say
we're
we're
talking
about
something
like,
like
you
know,
red
hat
enterprise
linux.
A
B
And
so
let's
say
that
we
are
a
software
company
and
we
pull
a
container
image
from
a
public
registry
and
we
put
our
software
in
it
and
then
we
send
it
on
to
our
end
customer,
while
all
the
open
source
software
within
that
container
image
that
you
based
your
product
on
that's
all
gpl
and
is
subject
to
the
requirements
of
the
gpl.
So
that
end
user
customer
could
say.
Hey.
B
Give
me
the
source
code
for
this,
for
this
container,
that
you
just
sent
me
and
you
would
be
obligated
to
provide
it,
and
I
think
that's
where
things
get
really
kind
of
interesting,
crazy
and
dangerous.
Well,
not
really
dangerous
but
challenging.
Let's
say
challenging,
because
you
have
to
go
back
to
the
container
image
that
you
base,
that
off
of
and
figure
out
how
to
get
the
source
code
for
all
the
open
source
software.
B
That's
within
it
all
right,
and
I
do
see
that
carlos
is
asking
us
about
red
hat
software,
developed
by
red
hat,
that's
gpl!
So
there's
a
lot.
There's
well.
Red
hat
typically!
Will
sponsor
communities
like
the
fedora
distribution
and
that's
where
a
lot
of
our
development
happens
but,
like
systemd,
for
example,
was
initially
started
by
red
hat
employed
engineers
through.
C
A
C
A
You
know
for
for
all
the
rail
sysadmins
out
there
you
know,
do
your,
you
know,
do
your
rpm
qi
and-
and
you
can
see
that's
one
of
the
pieces
of
information
that
shared
with
every
single
package
we
distribute
is
what
is
the
licensing
that
it's
under
again
illustrating
sort
of
the
world
that
has
been
up
to
now
sort
of
pre-containers,
where
it's
pretty
straightforward?
If
I'm
going
to
use
this
rpm,
I
can,
I
can
query
the
rpm
and
I
can
find
out.
A
B
Right
and
I
think
that
the
thing
just
to
kind
of
keep
in
mind
the
developer
is:
do
you
keep
track
of
the
components
that
you're
using
for
your
containerized
application
in
such
a
way
that
you
could
provide
someone,
those
components
and
they
could
rebuild
it
themselves
if
you're
in
that
situation,
I
think
you're
in
pretty
good
shape.
Now
there
are
some
nuances
there
like
that
you
have
to
give
them
the
exact
version
of
source
code
that
you
used
when
providing
them
the
binary
and
that's
that
can
be
sticky
right.
B
B
You
need
to
distribute
the
exact
source
code
that
you
used
for,
making
your
thing
that
you
gave
to
them.
So
if
you
took
that
nginx
base
software
and
you
made
some
changes
or
you
patched
some
bug
or
security
vulnerability
or
whatever
you
have
to
provide
that
source
code
for
that
patch
as
well,
you
can't
just
grab
the
base
archive
from
the
open
source
project
and
send
it
on
unless
your
software
is
indeed
solely
based
on
that
based
software
from
that
project.
C
A
A
On
top
of
this,
and
that
they're
not
maybe
finding
themselves
on
the
wrong
side
of
of
this
and
facing
some
of
that
reputational
risk
and
facing
even
potentially
some
some
legal
action
right
and
again,
the
purpose
here
is
not
to
scare
people
away
from
using
containers
or
open
source
software.
It's
to
build
awareness
of
what
some
of
those
risks
are
and
help
people
to
handle
it.
So
are
there
some
things
that
people
can
approach
and
do.
B
Sure
so
one
of
the
things
is
just
compile
a
list
of
all
the
software
contained
in
this.
The
container
image
that
you're
basing
your
software
off
of
you're
building
your
own
container
images
from
scratch.
This
is
probably
a
much
more
direct
path
than
if
you're
pulling
a
image
off
of
a
software
registry.
C
A
A
Okay,
so
this
is,
this
is
an
interesting
concept,
because
it's
the
distribution
of
source
via
container
help
me
understand
what
would
actually
be
in
a
source
container,
because
I
understand
what
would
be
in
a
container
that
okay,
there's
my
container
there's
whatever
libraries
you
know,
whatever
applications
are
needed.
You
know
the
minimal
set
needed
to
run
this
thing
that
you
know
says
hello
world
right,
but
what
would
be
in
a
source
container?
What
does
it
do
and
and
and
how
you
know?
A
B
Right
so
we
think
of
containers
as
like
image
that
you
download,
and
then
you
execute
binaries
out
of
right
and
you
create
additional
processes.
So
source
container
is
a
little
bit
different,
because
containers
just
kind
of
stepping
back
a
little
bit.
Containers
are
really
just
an
archive
they're,
an
archive
of
stuff
and
it's
archives
of
binaries
and
files
and
file
system
images
and
other
things.
B
So
when
you
pull
down
the
source
container,
you're
really
just
pulling
down
an
archive
file,
and
then
you
need
to
kind
of
extract
the
archive
out
of
it
and
that's
how
you
get
access
to
the
source
code
and
it's,
it's
probably
a.
I
don't
know
three
or
four
command
process
to
get
down
to
the
place
where
you
can
actually
look
at
the
source
code,
that's
in
there
and
because
it's
irritating
to
track
versions
and
a
variety
of
other
things.
I've
I've
written
a
small
script
to
do
it.
For
me.
B
That
way,
I
can
just
like
pull
a
container
whenever
the
script
by
itself
pulls
the
latest
ubi,
but
you
could
put
in
as
an
argument
a
specific
tag,
number
or
version
number,
and
it
would
go
into
the
red
hat
archives
and
pull
that
one.
But
if
you'd
like
I
can,
I
can
just
pull
one
and-
and
we
can
take
a
look
at
it.
Let's.
A
C
B
A
B
A
B
B
B
B
So
so
I
installed
scopio
or
made
sure
scopio
was
installed,
and
then
I
just
set
a
couple
of
variables
here
for
the
version
of
the
image
that
I
was
interested
in.
So
if
I
was
basing
a
piece
of
software
on
gbi,
8
minimal,
I'd
want
to
track
what
version
it
was
based
on,
so
that
I
can
pull
the
right
source
container
to
go
along
with
it,
and
this
one's
actually
a
little
older.
This
is
not
the
most
recent
ubi
image.
B
The
most
recent
ubi
image
would
be
based
on
eight
five,
which
was
released
last
week,
so
we
also
provide
the
source
code
for
all
historical
ubi
images
we've
produced
and
you
can
pull
them
out
of
the
the
container
catalog
down.
Here
I
do
a
scopio
inspect
and
all
that's
doing
is
getting
some
information
about
about
the
image
that
I'm
wanting
to
pull
and
then.
B
B
B
B
And
so
when
we
did
that
extraction
of
all
the
archives,
it
actually
pulled
out
all
source
code
rpms
into
the
blobs
directory
and
then
created
these
symbolic
links
right.
So
I
look
at
some
more
points
of
the
rpm
directory
right,
so
the
actual
content
of
the
container
is
morally
complex,
but
then
we
create
in
the
source
container
this
symbolic
link
structure
so
that
we
can
do
a
one-to-one
of
here's.
The
source
code
rpm
that
was
used
for
the
software
used
to
make
this
container
and
here's
where
it's
stored
in
the
container.
A
Okay,
so
this
invites
a
couple
of
questions
from
from
yours.
Truly,
if
I'm
thinking
about
a
container,
I'm
I'm
typically
thinking
about
sort
of
that
least
possible
set
of
things
that
I
can
put
in
to
get
the
functionality,
that's
needed
right,
and
so
you
have
a
container
that
is
essentially
built
down
to
that
that
level.
So
then,
you
have
a
container.
You
have
all
of
the
source
that
went
into
that.
A
If
I'm
thinking
about
all
of
this
long
list
of
source
rpms
that
you've
listed,
I'm
going
to
assume
that
there's
things
that
those
sarge
rpms
would
build
that
are
not
actually
put
into
the
container.
So
is
there
any
notion
about
you
know,
somewhere
between
that
source,
rpm
and
then
what's
in
the
blobs
directories,
you
know
sort
of
restricting
it
down
to
what's
actually
used.
A
Okay,
so
it's
not
okay,
so
the
this
is
actually
whatever
is
the
source
that
was
used
for
the
container,
as
opposed
and
the
reason
I
say
this
is
because
some
of
these
resemble
packages
that
you
might
see
in
red
hat
enterprise,
linux,
for
example.
It
is
not
the
same
source
rpm
that
you
would
find
there.
It
is
the
paired
down
source.
B
No,
no
so
one
of
the
nice
things
about
universal
base
image
is
that
it's
based
off
the
same
stuff
as
red
hat
enterprise
linux.
So
these
source
rpms
do
correspond
with
ones
that
you
would
find
in
red
enterprise
linux,
because
we
use
the
same
content
to
make
the
universal
base
image,
which
is
freely
redistributable
and
does
not
require
subscription.
B
So
I
think
the
the
fact
that
we're
seeing
the
same
packages
here
as
we
see
in
red
hat
enterprise.
Linux
is
very
intentional
because
we
want
them
to
be
identical,
and
so,
if
we
went
out
to
the
rel
84
source
code
repository,
we
could
find
the
exact
same
versions
of
this.
But
the
big
difference
is
rel
is
a
very
large
distribution
with
you
know
thousands
of
packages,
whereas
this
one
is.
Let's
look.
B
B
B
B
There
we
go
so
I
think
I
put
the
version
numbers
in
before
we
start
shipping
micro
or,
for
some
reason
build
a
micro
of
the
same
version
and
tag,
but
so
I
just
went
out
to
the
red
hat
container
repository
and
pulled
up
the
page
for
ubi,
8
micro
and
then
just
grab
the
version
information
from
that
page,
pull
it
down
all
right.
So
a
couple
shows
ago
we
talked
about
ubi
micro
and
what
was
the
special
magicness
of
ebi
micro
and
why
people
cared
about
it.
C
B
So
we
ship
four
images
with
ubi
we
ship
ubi
init,
which
is
the
multi-service
image.
It
includes
a
full
implementation
of
systemd,
we
ship
the
standard
image
we
ship
the
minimal
image
and
we
ship
a
micro
image
and
each
one
of
those
has
less
software
than
the
one
before
it
right
and
we're
done
with
the
actual
container,
really
small.
So
when
I
showed
you
the
source
code
of
ubi
8
minimal,
there
were
91
packages.
C
B
Less
software
right,
and
so
when
we're
pulling
the
source
containers,
we're
getting
just
those
source
rpms
that
were
used
to
build
the
container
image
that
we
ship
with
that
version,
number
yeah
right.
So
if
you
did
a
ubi,
8
init
image
that
has
systemd
and
there's
like
a
ton
of
other
libraries
and
software
and
stuff
that
goes
in
there,
you're
going
to
get
more
than
91
packages
of
minimal,
because
there's
actually
just
included
in
the
container
image.
B
Yeah
and
we've
actually
been
doing
a
whole
bunch
of
work
to
to
make
sure
the
packages
don't
pull
in
dependencies.
They
don't
absolutely
critically
need
instead
building
dependencies
in
other
places
like
our
install
infrastructure.
So
it's
like,
if
I'm
installing
this,
I
need
to
get
that,
but
it
doesn't
necessarily
have
to
be
a
dependency
in
the
rpm
itself.
B
A
Okay,
so
that's
that's
amazing
to
me
because
you
know
as
a
fossil,
who
could
remember
you
know
years
ago,
installing
early
linux
from
two
floppy
disks.
If
people
even
remember
what
those
are
that's
getting
right
back
down
to
sort
of
the
roots,
but
it
really
sort
of
illustrates
what
are
the
benefits
of
containers.
C
A
You
know,
as
god
was
saying,
also
so
sort
of
the
ubi
in
that
sense,
that
you
can
really
really
pare
it
down
to
that
smallest
set
of
what
you
need,
and
that
is
part
of
the
advantage
of
being
able
to
run
things
in
containers.
Is
that
it's
only
what
you
need,
and
that
makes
it
you
know
a
functionally
better
solution
for
an
awful
lot
of
things
right
right.
A
Well,
you've
provided
everything
you
need,
but
you've
provided
nothing
that
you
don't
need,
which
is
also
in
just
in
terms
of
being
able
to
start
up
your
app
and
run
the
app.
It's
just
a
different
situation
than
saying.
Let's
look
for
just
to
draw
a
parallel
going
to
a
vm
right.
Vm
is
a
full
operating
system
you're
getting
along.
You
know
all
of
what
you're
having
there,
much
of
which
you
might
not
actually
be
used
using,
doesn't
mean
it's
not
useful
somewhere
for
someone,
but
for
your
particular
application.
B
Fair
point
so
to
continue
like
talking
about
the
actual
source
code
and
like
how
how
we
represent
that
I
went
ahead
and
installed.
One
of
these
source
rpms
and
I
chose
to
use
the
batch
one
and
so
included
in
the
source.
Rpm
name
is
the
version
that
we're
basing
this
version
of
bash
off
of.
So
this
is
a
bash
shell,
based
on
version
4.4.20
from
the
bash
open
source
project.
B
And
so
that's
what
you're?
Seeing
here
with
this
dash
extra
version
number.
I
will
caution.
You
don't
try
to
read
too
much
into
the
extra
version
numbers
a
different
software
management
teams
that
read
out
use
different
different
methods
for
determining
it.
So,
for
example,
the
kernel
team
has
a
really
complex
versioning
scheme.
They
use
in
the
extra
version
number,
whereas.
C
B
B
C
A
A
You
know
and
the
implications
when
you're
using
containers
and
what
you
might
have
to
actually
distribute
if
you
are
distributing
your
app
as
a
container
right,
especially
if
you're
doing
so
in
some
sort
of
commercial
setting
right
is
that-
and
I
think
we
see
this
more
and
more,
where
that's
going
to
be
the
preferred
way
to
distribute
an
application,
is
just
say:
well,
look.
Here's
your
container
go,
go
run
it
on
your.
You
know,
rel
or
openshift
or,
however,
you
want
to
run
your
containers.
A
Well,
okay,
be
mindful
commercial
vendor
that
you
might
need
to
think
about
what
went
into
that
and
how
you're
distributing
it,
because,
if
you're
using
the
gpl
stuff
and
there's
a
lot
of
it,
you
have
you
do
have
this
commitment
to
sharing
these
things
and
there's
a
really
important
benefit
to
the
end.
Consumer
of
this
is
okay.
So
let's
say
you
have
this
application
and
you're
having
a
problem
with
it.
Well,
being
able
to
investigate,
it
is
one
of
the
powers
of
open
source
is
that
is
that
you
you
can.
A
C
B
B
So
there
was
recently
someone
in
a
container
linux
that
that
posted
on
twitter
that
he
was
not
interested
in
any
problem
reports
from
the
wsl
version
of
their
container,
because
that
didn't
actually
come
from
their
team
that
they
allowed
someone
else
to
to
build
the
container
image
for
that
for
that
container
ecosystem,
and
I'm
not
saying
that
that
the
person
rebuilding
it
has
done
anything
dastardly
or
anything
like
that.
It's
just
like
it.
B
It
has
passed
now
through
several
different
hands
to
find
its
way
onto
another
container
registry,
and,
like
did
did
they
track
all
the
same
stuff?
Did
they
make
any
changes
to
make
it
compliant
for
that
container
registry
that
have
to
be
documented
and
shared
that
that's
the
the
cautionary
kind
of
kind
of
statement?
A
I
was
just
going
to
ask,
I
I
don't
think
really
anybody
else's
is
solving
the
problem
in
quite
this
way,
that's
not
to
say
that
there
might
not
other
be
some
other
solutions
to
it,
not
sure
if
there
are,
but
certainly
this
is
a
sort
of
a
very
red
hat.
Take
on
how
to
solve
this
particular
problem
right.
B
Right-
and
I
think
it's
born
out
of
our
long
history
of
needing
to
solve
this
problem
that
we're
like
okay,
we
know
how
to
distribute
rpms.
We
know
how
to
distribute
source
rpms,
let's
just
make
sure
that
we
have
that
one-to-one
comparison
right
compared
with
some
of
the
more
organic
methods
of
managing
open
source
of
like
I'll,
just
download
47
tar
archives,
that
this
is
a
little
bit
more
structured,
and
that
is
helpful.
A
C
B
C
A
B
C
A
B
A
B
B
B
C
B
B
B
And
if
you
know
that
your
you
may
be
asked
that
question,
you
build
processes
around
gearing
up
to
be
asked
that
question
when
somebody
actually
asks
you
that
question
you're
you're
ready
to
go
a
lot
of
times,
you'll
you'll
get
those
questions,
because
somebody
in
your
company's
legal
department
is
like
hey.
I
this
this
thing
open
source
what's
going
on
and
you
have
to
trace
it
down
randy
a
long
long
time
ago.
B
A
long
long
time
ago
I
was
working
for
a
company
that
was
becoming
a
red
hat
partner
and
one
of
the
questions
from
that
company's
legal
team
was
how
do
we
know
that
the
source
rpms
provided
by
red
hat
actually
build
the
binary
rpms
that
are
on
the
install
media
and
question?
It's?
It's
red
hat
and
it's
their
license
and
their
product,
so
it
kind
of
has
to,
and
they
went
yeah
not
good
enough.
B
C
A
C
A
Again
years
and
years
ago,
undertaking
undertaking
the
project
at
home
that
I
was
going
to
rebuild
the
entirety
of
rel
from
source
and
you
know
yeah.
If
I
wrote
a
script,
you
wrote
a
script,
I
wrote
a
script
and
you
know
it
was
chugging
along
working
very
nicely
until
I
ran
out
of
disk
space,
and
that
was
the
end
of
that
particular
project
and.
B
One
I
do
have
one
last
thing,
so
I
think
it
was
two
weeks
ago
now
we
released
red
hat
enterprise,
linux,
9
beta,
and
that
is
available
to
anyone
with
red
hat
subscription,
including
those
with
a
costless
developer
subscription,
in
addition
to
the
red
hat
enterprise
linux,
9,
beta
and
making
it
available.
We
built
all
the
ubi
images
for
red
hat
enterprise
and
x9,
so
the
rel
9
ubi
beta
images
are
available
in
the
red
hat
container
catalog.
A
C
B
A
C
A
All
right
so
before
I
get
myself
in
trouble
here,
I
want
to
thank
everybody
for
joining
us
again
on
the
level
up
hour.
Please
do
like
subscribe
and
share.
We
are
here
most
wednesdays
and
look
forward
to
having
you
tell
your
friends,
you
know
now.
Let
us
know
if
there's
some
topics
that
you
think
we
might,
we
should
explore
and
discuss
we're
always
looking
for
for
new
topics
and
things
to
explore.
So
you
know
let
us
know.