►
From YouTube: The Level Up Hour (E35): Podman v3 and docker-compose
Description
For reals this time, let's experiment with docker-compose using a podman backend. Since we didn't actually get to this back in episode 30 let’s get back into Docker Compose support in the latest Podman release. We’ll see if we can launch our Cool Store using the Compose-like features. We'll also experiment with exporting the compose pods and try to run them in OpenShift.
Read more:
https://www.redhat.com/sysadmin/podman-docker-compose
Follow us:
Langdon White https://twitter.com/1angdon
Chris Short https://twitter.com/ChrisShort
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
B
Yeah
and
basically
what
happens
is
is
really,
and
this
is
the
part
that
took
me
a
bit
to
wrap
my
head
around-
is
you're
actually
using
docker
compose,
but
because
docker
or
likely,
because
right
docker
compose,
was
originally
developed
by
a
third
party
who,
of
course,
I
can't
remember
the
person's
name
off
top
my
head,
but
they
were
developed
independently
of
docker,
and
so
what
it
does
is
actually
calls
the
public
api,
which
happens
to
be
a
restful
api
to
do
all
its
stuff
right.
So
what
podman
v3
does?
A
B
A
B
If
we
had
like
some
sort
of
like
centralized
repository
because
a
lot
of
blog
posts
are
about
like
how
do
I
install
blah
and
then
how
do
I,
you
know,
use
blah
and
I
always
thought
it'd
be
kind
of
cool
if,
like
attached
to
the
article,
was
an
ansible
playbook
that
you
could
just
run
right
like
it's
good
to
kind
of.
Do
it
by
hand,
you
know
once
or
twice,
but
it's
also
nice
to
have
something
that
is
rep.
You
know
repeatable
that
you
can
use
elsewhere
or
whatever.
B
So
I
took
that
article
and
I
turned
it
into
a
playbook.
The
playbook
is
pretty
straightforward
and
apparently
vs
code
really
doesn't
like
that.
I
have
cube
cuddle
actually
trapped
in
a
container
and
one
of
these
days
I
need
to
give
it
a
sim
links
or,
like
you
know,
a
link
so
that
it
can
actually
run
cuddle
and.
B
About
it,
but
I
don't
use
that
feature
set
very
much,
so
I
haven't
gotten
around
to
it
all
right.
So
the
first
thing
we
do
is
we
install
podman.
Now
we
only
have
to
install
podman,
I
almost
always
install
scopio
and
build
separately.
You
may
actually
get
them
get.
I
think
you
might
get
build
up
by
dependency.
I.
B
A
A
A
B
B
Yeah,
I
think
the
two
biggest
things
that
you
know
like
that
are
hard
to
find
anywhere
else.
One
of
them
is
the
list
tags
which
is
super
useful
for
quote-unquote
like
properly
designed
containers
where
the
container
has
a
bunch
of
different
versions
available,
but
they're
all
based
on
tags
and
like
I,
I
it's
really
weird,
like
even
from
the
get-go
docker,
never
really
treated
the
the
remote
tags,
almost
like
a
first-class
citizen
like
they're,
super
useful
and
they're
a
super
good
way
of
like
kind
of
getting
different.
B
You
know
kind
of
profiles
for
any
given
container,
but
they're
really
hard
to
discover.
So
that's
one
of
the
big
reasons
I
use
scopy
is:
I
want
to
go
and
find
out,
like
you
know,
if
the
fedora,
that's
there
like
what
versions
of
fedora
are
available
right,
which
might
be
listed
as
tags
where
commonly
would
be
listed
as
tags
and
then
the
other
big
one?
Is
that
inspect,
which
kind
of
tells
you
the
the
intricate
details
of
a
remote
container?
B
So
you
don't
have
to
kind
of
pull
it
down
to
to
dig
around
in
it,
and
I
know
I
know:
scorpio
has
used
a
bunch
to
do
the
kind
of
the
security
components
of
like
the
health
index
and
stuff
like
that,
so
that
you
can
kind
of
do
all
that
stuff
from
at
least
you
don't
have
to
have
a
copy
of
every
single
container
in
the
entire
world
on
your
local
or
every
single
image.
I
guess
on
your
local
host
all
right,
so
that
was
a
little
digression
in
the
scope.
A
A
B
B
A
B
B
We've
covered
it
largely
already
yeah,
you
know,
but
yeah
the
the
list.
Tags
thing
as
playing
risky
says
you
know
is
super
useful.
At
least
you
know
in
my
ex
when
you're
doing
that
discovery
process
of
somebody
else's
image.
It's
it's
a
comp.
You
know
it's
a
hard
thing
to
get
elsewise
and,
like
I
said
I
it's
one
of
those
things.
I
do
not
understand
why
it's
not
like
you
know.
B
We
refer
to
them
as,
like
a
first-class
citizen,
you
know
it's
like
you
know,
images
are
listed,
containers
are
list,
you
know,
but
just
the
tags
are
like
hard
and
kind
of
clunky
and
stuff
like
that,
and
I
just
I'll.
Never
I
like
I
said
I
just
don't
understand,
really
why
so
all
right
so
moving
on
okay,
so
I
have
my
awesome
tasks
here.
So
the
next
thing
we
do
and
the
only
reason
I
separate
these-
was
for
the
sake
of
discussion
here.
A
B
A
That
might
be
better
out
for
you,
so
that,
but
I
should
point
out
that
you
can
download
scopio
on
just
about
every
os
out
there
where
and
like
use
it
effectively
right
so
like
you
can
install
it
with
brew
on
mac
os
or
you
know,
compile
it
from
source.
If
you
want
on
linux,
you
know
so
it's
does
it
work
on
windows.
Let's
see
no,
but.
B
B
A
B
Would
like
a
bigger,
let's
see
if
we
can
figure
out
how
do
we
do?
I
think
it's
here.
I
need
to
go
play
with
this
one
of
these
days,
but
I
haven't
had
great
luck
with
it
yet,
but
I
found
some
tool
that
supposedly
will
make
this
better.
Okay,
that's
up
to
18..
Hopefully
that's
a
little
more
readable
and,
like
I
said.
B
So,
if
you're
having
any
trouble
reading
it
like,
I
said
it
is
in
the
repo,
so
you
can
go
and
open
it
and
make
it
any
size.
You
want
so
okay
going
back
to
okay,
so
this
next
ansible
task
is
really
just
separated,
because
this
is
specifically
what
you
need
if
you
have
podman
to
make
docker
compose
work,
so
you
need
of
the
podman
docker
package,
which
basically,
actually
I'm
really
curious.
Now
I
think
it's
basically
oh
shoot.
I
forgot.
B
B
B
B
B
Yeah
yeah
exactly
all
right,
so
long
story,
short
okay,
so
I
just
was
kind
of
curious.
So
basically,
what
podman
docker
does
is
I'm
not
exactly
sure
how
it
works?
This
may
be
a
question
for
brent
one
of
these
days.
Is
it
essentially
installs
a
a
sim
link
to
pod
man,
but
now
anytime,
I'm
on
this
computer,
I
can
type
docker
and
get
podman
so
yeah
see
it
even
says
emily
cla,
oh
you
know,
maybe
it's
an
actual
pass-through,
that's
how
it
works.
B
A
B
B
A
B
I
do
yeah,
I
don't
like
blackboard
to
narendiff
lack
is
like
I
love
the
word,
and
I
love
that
there's
a
number
like
a
name
for
a
hundred
thousand,
that's
simple!
So,
okay,
so
you
install
docker,
compose
and
just
by
way
of
explanation
to
the
best
of
my
knowledge.
Everything
about
this
stock
or
composed
package
is
exactly
the
same
as
the
one
you
would
get.
You
know
without
podman.
B
In
a
sense,
so
it's
just
regular
old
docker
compose
the
only
thing
is
that
and
I'm
not
sure
where
the
the
dropout
point
is
exactly
like.
I
don't
know
if
the
feature
set
is
not
in
docker
compose
it's
this
package
that
is
available
on
fedora
or
but
I
think
it's
available
there,
but
podman
doesn't
support
the
swarm
feature
set
that
got
subsumed
into
docker
compose
a
few
years
ago
now.
B
So,
if
you're
trying
to
do
anything
with
the
swarm
feature,
set,
that's
not
going
to
work
on
podman,
so
just
kind
of
know
that
going
in,
but
I
think
the
docker
compose
has
it.
So
you
can
shoot
yourself
in
the
foot
with
it,
but
it
won't
work
when
you
try
to
run
it
all
right.
That
was
that
was
long
and
involved
all
right.
B
B
And
if
you
notice
so
there's
a
socket
here
and
if
you
know
anything
about
linux,
everything
on
linux
is
a
file.
So,
even
though
this
is
a
you
know,
an
internet
socket
right.
It
is
just
a
file,
so
it
just
gets
created
on
disk
and
in
the
case
of
many
sockets
these
days
it
is
managed
by
systemd.
So
you
can
status
podman.
B
A
B
And
so
yeah,
so
you
see
this
podman
socket
is
here
it's
active
and
you
know.
Obviously
I
ran
this
playbook
earlier
to
to
enable
it,
but
but
we'll
run
it
at
the
end,
just
to
prove
that
it
works,
because
it
should
be
important
and
then
the
last
thing
which
I
had
never
done
in
ansible
before
is
you
can
actually
do
like
an
actual.
B
So
this
will
actually
execute
as
a
curl
command
to
make
sure
that,
oh
and
actually
sorry
before
I
move
to
that
the
thing
that
doing
that
podman
docker
and
the
docker
compose
installed.
It
enables
this
docker
sock
as
well.
So
now
we
have
both
sockets,
but
if
you
notice
they're,
actually
in
two
different
places,
I'm
not
sure
why.
I
don't
know
if
one
is
right
and
one
is
wrong
or
whatever,
but
if
you
notice
that
really
is
assembling
the
docker.
B
Oh,
I'm
only
sharing
the
one
window
I
forgot.
Let's
see,
can
I
get
a
browser
window
in
the
envious
code?
Probably
somehow
maybe
I
need
an
extension,
though
I
don't
know
yeah.
I
think
you
need
an
extension,
so
let
me
I'll
just
copy
it
from
the
other
window,
but
in
that
article
that
I've
already
linked
to
and
is
in
the
show
notes
there
is
the
command
that
they
propose.
You
run,
which
I'm
just
going
to
cut
and
paste.
So
I
don't
get
my
like
extended
curl.
B
B
I'm
using
this
unix
socket
to
do
the
curl
request
and
then
I'm
going
to
this
url
and
if
you
notice
over
here
very
small
there's,
an
okay
which
you
know
is,
is
a
200
return
code
from
http.
So
I
look
for
that
status
code.
Then
I
check
to
make
sure
I
got
it
and
then
I'm
actually
going
to
retry
it
in
case
it
doesn't
happen.
B
B
B
B
Yeah
so
let's
run
it
so
I'm
going
to
give
it
the
become
password,
and
if
you
notice,
everything
is
pretty
much.
All
of
this
is
running
as
sudo
or
as
root.
You
know,
because
it's
like
installs
and
all
that
jazz
it
doesn't
like
that,
I'm
using
python
3
or
does
like
I'm
using
python
3.
I
can't
figure
out
this
message.
B
B
So
what
I
did
was
kind
of
again
following
along
with
the
blog
post,
I
went
and
grabbed
so
there's
a
set
of
compose
examples
of
which
there
are
like
20
called
a
github
repo
called
awesome
compose
and
in
here
what
I
did
was
I
just
stripped
out
a
bunch
that
I
didn't
think
we
were
gonna
talk
about
and
I
didn't
think
it
was
worth
like
kind
of
storing
for
the
sake
of
storing,
but
in
here
you
can
see
where
I
got
it
from
it's.
This
url
this
awesome
compose.
B
So
that's
the
real
source.
You
know
I
just
have
them
here,
didn't
feel
like
doing
sub
modules
and
git.
So
I
just
cloned
him
over
here.
It
is
cco,
show
or
cc0.
So
it
was
fine,
but
I
wanted
to
make
sure
there
was
a
call
back
to
anybody.
You
know
who
actually
came
across
this
and
wanted
to
find
the
real
source,
so
it
has
obviously
a
bunch
of
different
examples.
B
B
B
Basically,
so
this
is
an
ss
sshfs
fine
mount
of
this
episodes
directory
into
this
machine,
so
something
about
the
security
of
it.
It
doesn't
like
this
there's
a
there
seems
to
be
an
allow
root
flag.
I
can
use
for
shfs,
but
I
thought
the
solutions
I'm
going
to
show.
You
were
better
in
this
case,
so
the
first
and
foremost
solution
I
can
do
is
just
take
that
and
copy
it
directly
into
my
home
der,
and
so
I'm
going
to
jump
over
there.
B
It
should
just
work
and
there
it
goes,
and
if
you
haven't
used
docker
compose
before
both
good
thing,
but
sometimes
confusing
thing
is
what
it
does.
Is
it
when
it
starts
off
all
its
containers.
It
kind
of
feeds
all
the
logs
together.
So
you
can
see
them
in
this
column
over
here
and
actually
just
for
the
sake
of
discussion.
B
B
B
Yeah
it
it
basically
just
is
a
git
server
for
lack
of
a
better
term
that
doesn't
make
a
lot
of
sense.
It
requires
a
database,
so
there's
also
something
called
db
for
database
and
the
environment.
Is
you
know?
Basically,
these
are
the
environment
variables
that
are
going
to
get
passed
into
getia,
and
then
you
know
the
database
is
going
to
start
up.
It
sets
up
the
database
password
all
that
stuff.
This
is
super
secure
as
usual,
and
then
it
does
a
volume
mount.
So
you
don't
lose
all
your
data.
B
B
The
thing
to
remember,
though,
with
docker
compose-
and
this
is
true
for
all
of
the
orchestration
techniques-
is
you
don't
have
any
promises
about?
What's
going
to
come
up
first,
so
you,
your
tool
chain
needs
to
be
tolerant
of
the
fact
that
excuse
me
gitia,
for
example,
may
launch
before
the
database
is
actually
fully
ready
to
receive.
B
Excuse
me,
so
you
need
your.
You
know
if
you're
writing,
the
equivalent
of
getting
you
got
to
keep
in
mind
that
you
have
to.
You
know,
be
aware
that
the
database
may
not
be
there
all
the
time.
So
you
need
to
keep
testing
and
you
can
warn
about
it.
We
might
even
see
a
warning
unless
it
came
up
correctly,
I'm
just
looking
yeah.
It
doesn't
really
look
like
it,
but
basically
you
need
to
keep
testing
you
know.
Otherwise
it
will
fail.
B
One
of
my
one
of
the
labs
I
worked
on
for
a
long
time.
You
know
like
we
had
to
fix
wordpress
because
in
the
initial
version
of
the
wordpress
that
we
were
using,
it
wouldn't
re-test
if
the
database
was
there.
So,
even
though
everything
was
perfectly
fine,
because
wordpress
happened
to
come
up
before
the
database
come
up,
it
came
up.
You
would
have
this
race
condition
where
sometimes
wordpress
would
fail
because
it
wouldn't
re-test.
B
So
in
a
you
know,
in
a
traditional
server
world,
that's
totally
fine
and
that's
why
it
was
never
fixed
right.
It's
not
really
a
bug
per
se.
It's
just
that.
You
know
in
a
new
environment,
you
sometimes
have
to
think
about
the
fact
that
it
may
not
come
up
in
the
same
way,
all
right
so
going
back
to
where
we
were
so
I'm
just
going
to
do
a
pop
d
back
to
my
old
directory
and
if
you
see
a
pwd
mysp,
it
doesn't
really
show
you,
but
it's
mounted
as
an
shfs.
B
So
for
that
reason
is
primarily
what
pushed
me
down
this
path,
but
also
you
know
if
you've
ever
used
docker
most
people
like
to
use
it
as
a
regular
user,
even
though
what's
happening
underneath
is
it's
actually
running
as
root?
So
this
is
one
of
those
things
that
is
kind
of
a
subtle
distinction
that
I
think
a
lot
of
people
aren't
aware
of
so
just
you
know
anything
that
you're
doing
in
docker.
B
Another
way
I
can
solve
this
problem
is
actually
probably
by
passing
the
environment
variables
around
correctly
and
it
might
find
it
I
don't
know
like
I
said
I
just
didn't
play
with
it,
because
I
wanted
to
go
and
solve
this
problem
too.
So
what
I'm
going
to
do
is
I'm
going
to
make
it
so
that
as
a
regular
user,
I
can
you
know
if
I'm
in
the
appropriate
linux
group,
I
can
run
docker
or
docker
compose
really
in
this
case,
so
going
back
to
another
playbook.
B
So
what
I
do
is
first
make
sure
that
the
docker
group
exists
which
installing
just
docker
compose
does
not
seem
to
create
it.
I
think
installing
the
actual
docker
runtime
will
create
it,
but
I'm
not
sure
because
I
haven't
done
it
in
a
long
time.
Then
I
need
to
find
out
who
I
am
so
that
I
can
put
me
in
that
group,
and
so
I
just
add
my
user
into
the
group
and
then
I
need
to
go
and
change
the
permissions
now.
This
is
where
a
little
it
gets
a
little
bit
weird,
because.
B
This
one
is
the
sim
link,
so
it's
owned
by
root,
but
if
you
notice
the
permissions
on
it
are
full
permissions
right,
so
you
can.
Basically
anybody
can
do
anything
to
this
sim
link.
Essentially,
so
what
you
need
to
modify
is
actually
the
you
know
the
target
of
the
sim
link,
which
is
the
pod
man
socket,
and
this
isn't
gonna
work
without.
A
B
A
B
B
A
B
A
B
B
B
Yeah,
I'm
not
actually,
I
remember
now
yeah,
I
don't
know
so,
but
the
nice
thing
is
that
they
are
doing
the
the
right
thing
in
the
open
source
world
right
as
they
have.
You
know,
they're
all
kind
of
contributing
to
the
same
baseline
and
then
kind
of
giving
different
slightly
different
user
experiences
on
them.
Like
you
know,
vs
code
is
very
focused
on
you
know
what
I'm
going
to
run
on
my
desktop
and
they
do
remoting
using
the
remote
terminal
or
the
remote
container
plug-in
type
stuff.
B
It
looks
like
this
code
server
one
uses
more
like
the
web-based,
but
still
feels
like
vs
code,
and
then
crw
uses
the
I'm
going
to
run
a
fully
remote
development
environment,
where
even
your
terminals
are
actually
running
in
a
container
on
a
remote
server.
For
example,
you
know
so
I
I
really
like
that.
We're
you're,
seeing
it's
not
competition,
co-op
petition.
You
know,
I
think
they.
B
B
B
B
You
know
kind
of
eventually
figure
out
how
to
get
back
to
like
my
projects
directory
without
me
having
to
you,
know,
kind
of
set
it
up
and
making
sure
that
you
know
the
routing
is
right,
and
you
know
like
all
that
stuff
like
I
don't
have
to
reconnect
it
on
boot.
I
don't
have
to
have
an
fs
tab
and
forget
no
fail.
You
know
stuff
like
that.
I'm
not
sure
that's
how
I
would
set
up
a
like
regular
machine.
Only
like
a
disposable
one.
I
guess,
is
kind
of
what
I'm
getting
at.
B
I
don't
know
so
off
on
that
massive
digression.
So
what
I
do
is
I
set
the
permissions
on
the
socket.
Oh
sorry,
the
first
thing
I
do
is
actually
set
the
permissions
on
the
directory
that
the
socket
is
in
because
there's
no
executable
on
it
by
default,
or
at
least
on
my
default
install
and
then
I
go
and
add
the
socket
to
the
docker
group
and
just
to
prove
my
mad
or
lack
thereof,
ansible
skills.
Let
me
go.
B
B
A
B
B
B
The
problem
is
that,
like
my
laptops
are
different,
if
it's
a
red
hat
laptop
versus
a
personal
laptop,
you
know
that
kind
of
stuff,
so
those
kinds
of
things
are
annoying.
So
what
I'll
kind
of
do
is
I
kind
of
have
like
a
baseline?
But
then
I
have
a
whole
mess
of
roles
that
I
use
sometimes,
and
so
then
I
just
kind
of
have
a
yaml
that
says
you
know
call.
I
can
literally
call
one
off
yaml.
That
is
just
roll
one!
Roll
two
roll
three
roll
four,
because
I'm
like!
B
B
A
B
So
I
went
okay,
so
if
I
do
control
r
and
then
I
do
ls
and
then
I
do
control
okay
and
that's
let's
say
that's
the
one
I
wanted,
but
then
I
do
control
r
again
by
accident
or
because
I
missed
it
or
whatever.
If
you
do,
control
shift
r
wait,
maybe
that's
not
it
there's
a
there's,
a
keystroke.
I
thought
that's
what
it
was
that
we'll
go
back
the
other
direction
again
anyway,
anyways
it's
cute.
It's
handy!
I've.
A
A
B
B
B
But
for
me,
because
of
how
I
learned
to
use
docker
and
docker
compose,
I
expect
to
not
type
sudo
in
front
of
everything
that
I
do
and
that
has
actually
translated
really
well
to
pogba
right,
which
means
that
now
most
of
the
containers
I
run
are
not
running
root
full,
but
it
is
something
to
keep
in
mind
that
you
are
running
these
things
root
full,
even
though
you're
not
running
suda.
So,
let's
see
so
now.
B
I
ran
that,
and
I
should
be
able
to
what's
funny-
is
that
sudo
will
still
not
work
because
of
the.
I
think
it's
actually
environment
problems.
Basically
it
doesn't
it's
not
finding
the
sim
links
or
the
shfs
or
something
like
that,
but
long
story
short.
If
I
do
docker
compose
without
sudo,
not
that
and
then
let
me
just.
B
Get
there's
a
there's
like
a
cleanup
flag
that
I'd
rather
run
if
I
can
find
it
quickly
because
yeah
it's
not
there
or
whatever
it
should
work.
Okay,
so
docker
compose
up,
and
now
you
know
I'm
happily
on
my
merry
way.
What
I
think
is
particularly
funny
is
just
that
if
I
run
that
command
with
sudo,
it
doesn't
work,
but
if
I
run
it
without
sudo,
it
will
run
as
root.
So
let's
do
this.
I
know
I
can
do
more
terminals
in
here.
A
B
B
I
think,
and
actually
there's
some
more
exploratory
stuff
in
the
blog
post,
but
one
that
I
think
is
interesting.
If
you
know
anything
especially
about
how
the
networking
stuff
works,
you
can
see
it
actually
created
the
a
network
for
it,
so
they
should
be
able
to
find
each
other.
But
you
know
so
the
from
us
an
exposed
perspective.
B
A
B
B
B
B
All
right
all
right,
so
these
between
internet
points
and
I
just
realized-
I
forgot-
to
grab
the
the
links.
Let
me
see
if
I
have
them
somewhere,
I
can't
type
all
that
it's
a
that's
a
lot
of
typing
so
yeah,
but
narendev
in
first
place
with
5500
points,
and
then
we
have
netherlands
hackham
with
5200
points.
Then
noah
friction
with
4
000
points
and
joe
fuzz
still
holding
at
2
300
points
detective
conan
kudo.
I
noticed
that
they
did
not
submit
their
points
last
time.
A
B
Yes,
where
did
my
github
repo
go,
so
I
was
just
gonna
put
the
link
to.
I
have
so
many
windows
open
it's
kind
of
ridiculous
one
of
those
days.
So,
oh,
I
just
realized.
I
forgot.
I
have
a
table
of
contents
on
the
front
page
of
the
repo
that
I
have
to
go
like
manually
update
and
I
often
forget
that
it
exists,
so
it
is
currently
stuck
in
like
episode
24,
and
I
think
this
is
35..
B
A
lot
of
the
time
is
like
I
know
how
to
do
the
code
part
right,
but
getting
to
the
point
where
I
can
actually
write
code
is
sometimes
a
huge
bear
in
and
of
itself
like,
for
example,
I
was
fooling
around
with
writing
a
telegram
bot.
For
example.
I
don't
know
if
you
use
telegram
telegram
as
a
chat,
client
or
chat
server
and
client,
which,
on
the
one
hand,
is
pretty
cool,
because
the
all
the
clients
and
stuff
are
open
source.
B
But,
and
so
I
wanted
to
write
a
stupid
bot
to
clean
up
urls
so
that,
if
I,
you
know,
grab
a
url
that
I
want
to
share
like
with
my
family,
I
could
strip
all
the
tracking
information
off
of
it
and
so
writing
the
code.
For
that.
I
think
it
took
me
like
15
minutes
to
write
the
literally
like
10
lines
of
python.
It
takes
to
do
that,
but
to
write
to
get
the
telegram
bot
what
I
couldn't
even
get
out
of,
like
all
the
docs
and
everything
else
is
like.
B
B
That's
the
that's.
The
annoying
thing
is
like
yeah
like
openshift
like,
but
that
was
the
whole
thing
I
didn't
know
like.
I
couldn't
find
in
the
docs
like
how
to
make
it
go
and
like,
and
that's
often
the
biggest
challenge,
so
I
will
share
the
link
to
the
bot
once
I
finish
the
bot,
but
I
got
like
I
got
like
eighty
percent
of
the
way
there
last
night
and
then
was
like
okay,
I'm
too,
like
I'm
too
fried
staring
at
a
computer.
I
need
to
stop
now.
A
B
Well
so
yeah,
but
so
that
it
wasn't
the
problem
of,
like
you
know,
do
I
need
a
node.js
server.
Do
I
need
a
python
server?
Do
I
need
a
open
shift?
Do
I
need
a
whatever
those
things
it
was
like,
literally
not
knowing
the
kind
of
thing
I
needed,
and
you
know
eventually.
I
figured
out
that
I
needed
a
you
know.
B
I
needed
a
web
server
that
could
respond
to
web
hooks
and
actually
the
reason
part
of
part
of
my
impetus
for
doing
is:
I
wanted
to
write
a
serverless
function,
and
so
so
I
had
a
serverless
function
that
if
you
pass
a
url
to
it,
it
will
do
the
it'll.
Do
the
cleanup,
the
shortening
or
not
shortening,
but
the
it'll
actually
expand.
B
A
B
Yeah,
so
so
that's.
What
eventually
I
figured
out
is
that
I
can
actually
make
my
serverless
function
itself,
the
bot
and
that's
essentially,
that's
the
code
that
I
have
right
now
now
I
just
need
to
hook
up
the
like.
I
need
to
tell
the
bot
or
I
need
to
tell
them
what
is
it
called
bot
father,
which
is
how
you
do.
B
Right
right
and
that's
why
I
think,
but
that's
almost
like
the
worst
when
you're
trying
to
come
along
to
it
from
the
outside
right.
It's
like
it's
so
obvious
that
nobody
explains
it.
You
know
I
mean
yeah
yeah,
yeah,
so
yeah,
so
that
was
that
was
the
thing
but
yeah.
So
when
I,
when
I
hopefully
I'll
finish
it
soon-
and
you
know
I
can-
I
can
share
it
around,
but
so
that
was
the
sweet,
sweet
internet
points
we
love
giving
them
out.
B
A
A
A
B
B
So
so
does
auto
mount
or
mount
d
replace,
auto
fs,
maybe
oh
okay.
Maybe
I
have
to
go
look
at
that
because
I
I
was
trying
to
find
this
is
one
of
those
things
with
like
linux
has
now
been
around
too
long
as
far
as
I'm
concerned,
but
we
need
to
delete
all
of
the
old
content
and
and
restart
the
internet
because
it
can
be
confusing
about.
You
know,
because
you
know
things
supersede
each
other
which
they
should.
B
And
the
thing
that
really
annoys
me
about
it
is
that
http
has
a
mechanism
for
telling
you
the
date
that
something
was
published,
but
all
of
the
stupid
generators,
like
hugo,
for
example,
ignore
it
and
they
use
the
date
that
it
generated
it,
which
is
not
the
date
that
the
content
was
written.
I
don't.
A
B
This
this
annoys
me
about
the
internet,
because,
basically,
if
you
go
to
the
last
updated,
I
even
stopped
using
the
header
right,
but
it
used
to
be
like
it
used
to
be
in
firefox.
It
was
on
the
about
this
page
kind
of
thing.
It
was
like
right
there,
but
I
think
because
it
became
so
unusable,
like
you
know
so,
useless.
B
But
it
used
to
be
that,
like
in
the
early
days
of
the
internet,
when
people
were
doing
blind
html
you,
it
would
literally
be
the
date
the
thing
was
published,
so
even
if
it
didn't
have
a
date
in
the
content,
you
knew
what
the
date
was
because
it
was
when
it
was
published
and
it
was
right
there
in
the
last
updated
you
know,
whatever
you
call
it
hatter
yeah.
So
I.
A
A
B
B
B
Because
yeah,
so
if
it's
got
any
sort
of
dynamic
component,
so
it's
one
of
those
things
where,
like
the
specification,
probably
wasn't
clear
enough
because
technically
speaking,
it
was
updated
right
then,
because
it
included
your
name
because
you
logged
in
and
so
now
the
page
is
different
because
your
name
is
on
it
right.
But
that's
not
what
I
care
about
in
the
last
updated.
What
I
care
about
is
when
was
the
material
content
changed?
B
A
A
B
B
The
other,
the
other
thing
that
annoys
me
too,
and
that's
kind
of
related
right
and
like
red
hat
enterprise.
Linux
is
better
about
this,
but
fedora
definitely
have
this
problem
where
the
docs
for
the
operating
system
itself
right
are,
you
know
they're
on
the
internet
and
they
are
in
a
page
that
you
know
on
the
left.
Nav
is
you
know
the
content
of
you
know
fedora
14,
but
then
kind
of.
B
If
you
go
up
the
nav
the
later
and
older
versions
of
fedora
are
also
there
and
in
the
url
bar
is
the
version
number.
So
if
you
change
the
version
number
like
I
wanted
to
do
something
intelligent
like
so
instead
of
just
saying
404,
if
the
autofs
page
is
now
gone,
redirect
me
to
something
useful
like
that's
in
that
category
and
I
think
the
rel
does
this
one
pretty
well
but
like
or
or
allow
me
to
be
more
specific
in
my
searching
and
say
you
know,
or
the
warning
right.
B
This
was
one
of
the
things
that
I
got
changed
actually
in
the
in
the
customer
portal
because
I
kept
complaining
about
it.
Maybe
other
people
complain
too,
but
I
take
responsibility
which
is
now
on
any
piece
of
dock.
That
is
not
the
most
current
version
of
something
it
says:
hey
what
you're
looking
at
isn't
the
most
current
you
know
are
you
sure,
you're
looking
in
the
right
place,
which
is
handy
because
otherwise
you
know
you
make
stupid
mistakes
pretty
regularly
anyway.
B
B
Are
pretty
straightforward
but
the
and
then
you
know
play
around
with
any
of
the
other
compose
components
there.
One
of
the
things
that
I
started
fooling
around
with
there,
which
is
checked
into
the
repo,
is
doing
the
cool
store
using
docker
compose.
I
ran
into
some
problems.
Basically,
I
got
the
whole
thing
running.
A
B
A
Yeah,
let's
call
it
a
show,
it's
great,
so
coming
up
at
11
a.m,
eastern
1500
utc
ask
an
open
shift
admin.
We
will
be
talking
about
the
joys
of
subscription
comparisons,
licensing
entitlements,
the
whole
nine
yards
right,
we're
gonna
dive
into
all
that
fun
stuff
for
you,
so
you
can
figure
out
the
right
scenario
for
your
organization,
so
please
feel
free
to
join
us.
It.
A
Yeah,
so
in
less
than
an
hour,
it'll
be
on
and
andrew,
and
I
will
be
there
with
some
friends
having
some
guests
on
as
well
to
talk
about
it
and
feel
free
to
bring
your
openshift
questions
as
it
is
in
office
hour.
So
we
you
can
totally
bring
your
like.
Hey.
I've
got
a
problem
with
openshift
xyz
and
we
will
try
to
help
you
out
so
definitely
tune
in
to
that
and
as
always,
if
you
would
like
to
subscribe
to
the
openshift
streaming
calendar,
I
just
dropped
a
link
in
chat.
A
A
Is
it
a
good
idea
to
manage
ansible
for
running
docker
compose
using
its
module
called
docker
compose?
My
use
case
is
more
on
the
lines
of
running
few
test
cases
which
rely
on
docker
compose,
so
I
believe,
there's
a
dependency
in
the
ansible
module
of
docker
compose
being
on
that
system.
So
just
make
sure
you
satisfy
all
the
dependencies
and
it
should
work
for
your
use
case.
B
The
only
the
only
challenge
I've
had
with
community
modules
for
ansible
is
any.
You
know
what
you
would
exactly
expect
with
community
modules,
which
is
just
making
sure
they're
available
and
compatible
with
whatever
the
target
is,
and
so
that
can
be
a
little
bit
of
a
pain.
So
just
make
sure
you
know
so
not
only
do
you
have
a
dependency
requirement
on
docker
exposed,
but
it
needs
to
make
sure
it's
using
the
correct
version
of
python.
B
You
know
stupid
stuff,
like
that,
so
just
that's
been
my
biggest
challenge
with
community
modules
like
nothing
against
them.
Just
kind
of
be
aware
of
that.
I
have
not
used.
Let
me
go
pull
up
the
module
page
community
or
not
one
of
the
things.
This
is
one
of
those
places
where
it's
kind
of,
like
which
side
do
you
err
on.
A
B
Don't
use
ansible
with
containers
sort
of
so,
in
other
words,
like
you,
know,
there's
kind
of
like
you
have
kind
of
the
machine
that
you're
managing
which
might
use.
Let's
say
it
uses
a
bunch
of
containers
on
it.
How
do
you
get
those
containers
there?
Well,
there's
a
bunch
of
different
ways.
You
can
use
something
like
a
config
management
tool
like
ansible
to
get
those
containers
there
and
running
and
keep
them.
You
know
upright.
That's
one
option.
B
B
So,
but
if
you're
using
it
to
build
the
container
images,
that's
a
different
use
case
and
ansible,
I
think,
is
often
more
appropriate
there
than
it
is
using
it
kind
of
at
run
time
so
like
using
the
docker
compose
module
for
ansible
is
more
or
at
least
I
think
this
is
what
it's
for.
I
can't
quite
remember
like,
but
I
believe
it's
more
like
the
orchestration
side
of
things,
and
so
like
I
don't
know,
I
don't
so
it's
it's
a
really
dif.
B
It's
a
really
fuzzy
space
right
now,
like
there's
a
lot
of
overlapping
tool
chains
that
can
do
different
aspects
of
build,
ci,
cd
orchestration
and
they
all
do
some
of
those
things
very,
very
well
and
others.
Okay,
so
like,
if
you
know
ansible
really
really
well,
it
can
be
a
really
good
way
to
manage
your
entire
environment,
including
your
orchestration.
A
B
A
B
So
it
can,
it
can
definitely
be
super
useful
for
that
kind
of
environment.
You
know
basically
kind
of
just
you
know
you
want
to
automate
the
stand
up
of
your
environment
for
some
testing
and
the
tear
down.
You
know
in
a
relatively
straightforward,
simple
way,
and
you
know
ansible
well.
That
could
be
a
really
good
solution
for
that.
It's
just
like
I
said
that
is
a
super
custom
answer
for
most
people
like
it's
not
even
something
I
would
necessarily
kind
of
cover
on
the
show,
except
to
say
like
we
could
have.
A
A
Whatever
you
gotta,
whatever
you
gotta
use,
use
it
all
right.
Folks,
thank
you
for
joining
us
today.
We
really
appreciate
all
your
time
and
comments
and
everything
and
thank
you
for
joining
us,
we'll
be
back
here
in
less
than
an
hour
with
myself,
andrew
and
some
guests
and
until
then
stay
safe
out
there,
and
if
you
don't
see
us
later
today,
have
a
good
week
weekend
whatever
it
is,
we
are
all
I
think,
the
air
on
friday
by
the
way,
folks.