►
From YouTube: Cloud Foundry CAB Call Jan 19 2022
Description
In this call, the community had an opportunity to discuss Buildpacks very broadly.
Some relevant links:
Paketo website: paketo.io
Link to Paketo Slack:
paketobuildpacks.slack.com
https://slack.paketo.io/
Link to Buildpacks docs for custom stacks:
https://buildpacks.io/docs/operator-guide/create-a-stack/
The Paketo working group meeting on Tuesdays at 2:00 Eastern time, and would love to gain user insights and try to answer questions about issues that people are running into!! Learn more: https://github.com/paketo-buildpacks/community#paketo-project-working-group-meeting
A
A
A
Some
sort
of
backlog
with
is
in
terms
of
the
community
experience
working
group,
but
we're
very
happy
to
report
that
as
of
last
week,
there's
been
some
commendable
progress
on
it.
So
if
you
head
to
our
github
repo,
where
we
maintain
some
of
that
information
like
a
whole
lot
of
conversation
has
happened
in
especially
in
the
past
week,
and
things
are
sort
of
taking
shape
in
terms
of
ownership
of
documents
and
community
facing
assets,
and
things
like
that.
A
Updates
from
the
different
individual
working
groups
as
well,
so
one
of
the
things
that
we've
sort
of
been
changing
with
adopting
this
new
technical
oversight
committee
and
these
new
working
groups
is
publicly
facing
roadmap.
So
I'm
just
posting
a
link
to
one
of
the
publicly
available
roadmaps.
So
this
is
the
application
runtime
platform
working
group.
A
So
folks
can
see
you
know
what
folks
you
know.
Different
people
are
working
on.
You
can
get
an
idea
of
where
the
contributors
is.
Heads
are
right
and
you
know
obviously
also
understand
where
any
of
the
new
issues
and
pull
requests
that
you
might
have
raised.
You
know
actually
lined
up
so
we've
had
like
a
bunch
of
different.
A
You
know
submissions
in
terms
of
general
enhancement,
some
hacktoberfest
submissions.
What
have
you,
but
again,
this
is
sort
of
the
model
that
we
anticipate
all
of
the
different
working
groups
to
take-
and
you
know
obviously
mileage
may
vary
between
different
working
groups,
but
everybody
is
slowly
getting
on
board
and.
B
A
A
Reasonably
reasonably
close
neighbor,
but
also
a
very
close
friend,
and
he
was
introduced
to
buildbacks
and
all
of
these
things
a
while
back
and
he's
been
toying
around
with
using
build
packs
for
some
of
his
projects,
and
so
I
thought
the
cab
call
might
be
a
great
opportunity
to
sort
of
see
a
few
things
about
what
he's
done,
and
you
know
also,
you
know,
find
some
time
to
really
chat
about.
What's
good,
what's
you
know
good.
A
B
Hey
thanks
ron,
so
packet
of
build
packs
are
the
best
things
since
sliced
bread.
You
folks
already
know
that
so
I'm
here
to
talk
about
more
of
my
developer
experience
when
using
build
packs,
I've
been
an
autonomous,
php
developer,
so
I
started
with
the
packet
of
hp
buildbacks,
it's
all
cool,
and
then
I
hit
some
issues.
I
want
to
highlight
a
couple
of
them
with
two
different
stacks
here.
B
A
B
B
Scaffold
so
what
happens
is
whenever
you're
building
a
new
image
from
a
cache
layer?
All
your
composer
packages
go
away.
I
think
there
was
an
issue
range
for
this
also,
but
it's
sort
of
unattended.
So
if
that
could
be
moved,
then
I
could
end
up
using
it
in
at
least
like
50
projects
down
the
pipeline.
Instead
of
you
know,
grinding
out
and
building
docker
files
manually.
A
C
B
B
B
Not
so
noteworthy
experience
in
golang,
so
I
saw
that
the
composer
install
step
doesn't
run
if
there
is
no
change
in
the
composer
packages
or
anything
like
that.
So
what
ends
up
happening
is
we
don't
get
the
source
code
files,
so
I'm
sure
there's.
There
must
be
a
way
to
tweak
this
so
that
you
know
projects
like
drupal
make
effective
use
of
buildbacks.
I
ended
up
writing
my
own
custom,
build
pack,
which
is
a
fourth
question
of
this,
where
it
runs
composer.
B
Nevertheless,
so
that's
why
I'm
currently
spinning
the
blades
here
also
one
more
quick
thing
on
a
related
note
when
installing
dependencies
this
is
in
python,
so
python
expects
the
build
pack
expects
the
requirements,
dot
txt,
which
is
a
catalog
of
all
the
library
dependencies
for
a
python
application
to
be
present
at
the
top
level
directory.
So
there
is
no
way
to
configure
that
to
be
anywhere
else
like,
for
example,
in
a
typical
project.
B
If
you
take
the
scaffold
or
the
structure
of
a
typical
say,
django
project,
it's
there
in
different
folders,
for
example,
you
might
have
the
version
of
the
requirements
in
dev.txt
and
then
the
production
version
in
production.txt,
or
something
like
that.
So
there
is
no
way
to
specify
an
alternative
name
or
a
path
or
a
folder
structure
for
the
requirements.
B
B
E
D
C
B
B
D
B
B
So
in
that
sense
I
should
be
able
to
spin
up
the
same,
almost
same
container
image
on
my
say,
docker
compose
build
and
so
that
when
I
change
the
source
code
and
then
it
it
does
a
hot
reload.
So
I
just
mount
the
source
code
volume
in
the
workspace
directory.
So
I
don't
know
whether
I
can
do
that,
whether
that's
a
it's,
a
valid
approach,
I'm
not
tried
that
before
so.
For
my
local
development,
I
use
a
docker
file
and
then,
when
I
deploy,
I
use
buildbacks.
B
C
B
B
B
By
the
way,
I
also
use
kpac,
which
is
the
kubernetes,
build
version
of
the
command
line
pack
utility,
because
in
many
of
our
projects
we
built
the
images
in
the
cluster.
So
we
go
with
kpack
and
sometimes
we
also
use
a
tekton
task
to
do
the
same
thing
but
yeah.
It's
really
buildpacks
running
the
show.
So
all
the
applications
are
built.
A
C
E
B
E
Exactly
what
you
said
like
it's
definitely
something:
we
know
that
there
are
users
that
want
it.
It's
just
kind
of
like
a
question
of
like
balancing
its
priority
against
like
doing
more
development
on
the
paqueto,
build
packs
and
trying
to
persuade
people
to
move
that
direction,
but
I
def
it's
definitely
still
on
our
like
to-do
list
and
something
that
we
haven't
stopped
thinking
about.
We
just
haven't
prioritized
it
at
this
point.
A
F
F
So
you
know,
I
know
that
paquetto
is
built
on
ubuntu,
but
you
know
we're
using
aws
eks
and
that's
built
on
amazon
linux,
which
is
red
hat
base.
So
is
there
any
plan
to
have
a
red
hat
based
like
version
of
paquetto
or
some
kind
of
way,
for
people
to
take
advantage
of
the
awesome
work
that
you've
done
on
the
pacquiao?
Build
packs
with
minimal
friction.
F
E
So
right
now
there
is
not.
There
is
right
now
yeah,
so
you're
right.
We
only
support
like
the
ubuntu
stack
image,
but
supporting
ubi
is
something
that
we
have
thought
about,
but
like
right
now
we're
not
going
down
that
avenue,
but
I
think
that
that
might
be
something
that's
available
down
the
road
and
it
may
be
available
in
like
the
tenzu,
like
paid
commercial
version
of
product
version
of
build
packs,
but
for
the
actual
open
source
piquetto
build
packs.
I'm
not
sure
if
that's
something
that
we'll
be
supporting.
C
E
E
A
A
E
Yeah,
so
the
main
issue
is
that
we
compile
all
of
our
dependencies
from
source
against
ubuntu.
So
but
there's
a
pretty
high
chance.
We
haven't
fully
investigated
it
that
some
of
those
dependencies
will
just
work
depending
on
what
the
stack
is
and
you
may
not
actually
need
to
recompile
them
and
then
yeah
you
could
support
your
own
custom
stack.
E
I
think
that
there's
documentation
somewhere
on
the
cloud
native
build
packs
site
for
creating
your
own
stack,
but
essentially
you
could
use
like
all
of
the
different
boiler
plates
that
we
have
and
just
sub
in
whatever
face
image.
You
want
and
then
use
our
tooling
that
exists
within
paquetto
to
like
bundle
up
that
stack
and
use
it
inside
of
a
builder,
and
that
should
take
you
pretty
far
depending
on
which
operating
system
that
you're
trying
it
for.
A
A
F
E
F
C
D
Okay,
it's
it's
two
parts,
one
is.
The
slim
is
the
sort
of
idea
of
the
minification,
but
the
other
one
is
actually
the
it
also
kind
of
analyzes
the
applications
that
are
built
into
the
containers
and
creates
sec
comp
and
app
armor
security
profiles.
So
that's
kind
of
the
more
the
feature.
I
was
really
curious
about.