►
From YouTube: Platform Sync: 2021-09-22
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
it
seems
like
we're
going
to
be
a
little
light
today,
but
if
we
are
ready
we
could
get
started.
A
A
All
right,
so
the
only
thing
that
I
guess
coming
from
my
side
is
the
release
that
we
did
yesterday
or
sorry
last
week
for
pac,
so
we
released
pack,
oh
21
0..
There
was
an
issue.
A
All
right
not
sure
if
he'll
be
able
to
make
it
back
in
so
as
I
was
saying,
we
did
have
a
a
bug
in
o210
and
then
basically
we
released
a
patch
for
that
in
o211.
A
I
believe
that
was
late
friday
or
saturday
morning,
but
nonetheless
it
seems
like
all
the
issues
revolving
that
were
addressed
so
yeah.
I
think
that's
that's
pretty
much
it
there.
A
All
right
so
yeah
I
just
went
through
the
the
release
planning.
I
was
noticing
that
it
seems,
like
other
people
might
be
in
the
previous
room,
so
I'm
not
entirely
sure
how
to
get
them
over
since
sam
already
posted
the
changing
room.
B
B
Going
yeah,
so
if
it's
good,
then
we
can
go
ahead
and
discuss
documenting
that.
A
Right,
cool
yeah.
As
far
as
I'm
aware
last,
I
recall
this
isn't
like
a
pressing
issue
right
as
far
as
the
previous
image
goes.
So
if
I'm
not
mistaken,
and
unless
you
have
other
opinions,
it's
going
to
be
released
on
the
next
release,
cadence
so
it'll
be
about
a
month
or
so.
Obviously
let
me
know
if
you
have
opinions
there.
B
Yeah,
I
don't
mind
releasing
it
later.
I
think
we
just
we
should
just
document
it
so
that
in
case
anyone
uses
it.
They
should
know
that
it's
an
upcoming
feature
and
what
the
current
functionality
is
for.
A
Yes,
I
completely
agree,
awesome
cool,
let's
see
so
I
think,
while
both
of
you
were
out,
I
mentioned
the
status
update
on
the
release
for
pack
o21
1.
We
did
have
to
do
a
patch
release
to
revert
a
change
for
environment
variables,
but
since
that
patch,
I
don't
think,
there's
been
any
further
reports.
B
C
Stephen,
I
don't
know
I
was
gonna,
ask
that
question
in
one
of
the
leadership
meetings,
especially
in
the
light
of
what
we
want
to
do
with
emily
going
on
sabbatical
stuff.
I
feel
like
all
that
it's
worth
probably
revisiting
relooking
at
all
those
things
right.
A
Right,
okay,
cool
yeah.
I
totally
agree.
I
have
no
no
real
opinion
as
of
yet,
but
it
does
make
sense
to
reevaluate
how
it's
currently
structured.
A
All
right,
if
we
move
on
to
the
next
thing
on
the
agenda,
also
by
the
way,
please
feel
free
to
add
anything
to
the
agenda
that
you
think
we
might
or
should
be
discussing.
A
A
Since
the
announcement
have,
we
noticed
personally,
I've
noticed
just
a
very
slight
handful
of
people
looking
for
alternatives
to
dr
desktop,
but
the
majority
don't
seem
to
be.
You
know,
scared
off.
I
don't
know
if
you
all
get,
you
know
a
different
sense
or
a
different
viewpoint.
C
I
I
think,
that's
mostly
true,
obviously,
there's
a
lot
of
discussion
when
the
announcement
drops
and
I
think
it
will
kind
of
taper
off.
I
imagine
we'll
get
another
wave
when
the
grace
period
actually
ends
in
january
or
coming
around
that
time
when
they
actually
have
to
do
by
they.
I
mean
people
and
whatever
their
work,
computer
or
whatever,
actually
has
to
evaluate
and
do
something
about
it.
But
I
imagine
it's
just
like
a
stressful
moment
and
then
they're
like
I'll
deal
with
this
later.
A
Yeah
cool,
so
I
didn't
know
like
what
the
grace
period
was
exactly
you're
saying
january
31st.
C
It
is
the
kind
of
end
end
of
the
grace
period,
even
though
I
guess
the
policy
has
changed
effective
immediately,
but
they
are
basically
giving
people
until
then,
obviously
like
I
think
they
have
even
said
in
their
announcement
like
they
are
not
going
to.
C
I
think,
like
actively
try
to
you
know
validate
some
of
that
stuff,
but
in
theory
you
are
violating
like
legal
terms
like,
for
instance,
if
you
wanted
to
work
on
like
they
said,
I
don't
know
how
much
of
the
fact
you
read
but
like
you,
even
if
all
you're
doing
is
working
on
pack
as
part
of
vmware
like
you
would,
your
vmware
would
have
to
pay
the
like
docker
desktop
service,
roommate
change,
because
you
work
at
a
company
that
obviously
employs
more
than
250
people
and
generates
more
than
whatever
the
minimum
revenue
thing
by
a
large
amount
right,
so
yeah
so
like,
even
though,
if
you
work
full
time
in
open
source,
you
do
not
fall
under
the
like
free,
docker,
desktop
clause,
interesting,
okay,
yeah
there
was.
C
A
C
C
Yeah
yeah:
no,
it's
good
that
they're
explicit,
but
yeah
it's
interesting,
so
I
think
it
may
impact
more
people
than
we
think.
I
think
a
lot
of
the
folks.
We
interact
with
at
least
from
the
bill
pack.
Slack
probably
fall
under
that
bucket.
I
imagine
yeah,
obviously,
if
you're
doing
pack
stuff
on
your
free
time,
that
does
not
apply
right.
A
Yeah,
that's
interesting,
okay,
so
another
two
tidbits
that
I've
gathered
thus
far
is
one.
I
know
I
forget
the
individual's
name,
but
I
think
it's
a
maintainer
of
podman
they've
been
working
really
closely
with
us
and
trying
to
get
the
support
even
more
integrated.
I
think
we're
looking
at
ssh.
A
What
is
it
ssh
docker
host
yeah
support,
but
one
of
the
things
that
I'm
also
capturing
is
that
there's
a
lot
of
nuances
to
docker,
desktop
versus
pod
man
and
one
of
those
being
volumes
like
volumes.
Don't
work.
A
Virtualization
aspect
where
rocker
desktop
does
a
lot
for
you
and
now
they're
having
to
essentially
re-implement
that
sort
of
facade,
and
so
I
think
that's
I
don't
know,
I
think,
that's
problematic
and
hopefully
we
get
in
front
of
it
and
by
we
I
really
do
mean
more.
Like
podman,
we.
C
We
as
the
industry
yeah
exactly
for
for
those
things
when
they
talk
about
that.
Do
you
know
if
that
is
mac?
Osx
specifics?
I
think
their
qmu
thing
is
osx
only
right
and
like
for
windows.
The
assumption
is,
you
have
wsl2.
A
Yeah,
that's
that's
a
good
point.
I
haven't
really
looked
at
the
specifics,
so
I
wouldn't
know.
C
We've
done
some
research
because
we
also
depend
on
docker,
because
we
depend
on
pac
for
some
of
our
local
salesforce
functions,
stuff
and
so,
at
least
from
the
research
that
we've
done,
and
I
think
sam
can
corroborate
a
lot
of
it
too.
It's
just
like
yeah,
I
mean
the.
I
think.
A
Yeah
and
the
docker
engine-
that's
not
affected
by
the
new
license
agreement
right
because
it's
just
the
desktop
yeah
just.
C
A
Yeah
yeah
from
what
I
can
tell
the
the
desktop
aspect
of
it
gives
you
a
lot
of
networking
and
volumes
right,
and
so
those
two
things
are,
I
don't
know
pretty
important
when
you're
thinking
about
a
a
solution
like
that
yeah.
C
Yeah,
I
know
stuff
will
break
down
too
even
on
wsl
for
like
because
this
is
true
on
linux.
For
me,
it's
just
like
the
vpn
stuff
is
pretty
wonky.
You
have
to
pass
like
the
dash
network
host
flag
doesn't
work,
but
I
think
with
docker
desktop,
it's
pretty
seamless
like
you,
don't
need
to
pass
those
flags.
A
C
Oh
wasn't
that
was
just
container
run
time,
though
right
like
are
you
talking
about
like
yeah
you're,
just
talking
about
the
container
run
time
right,
I.
A
Think
so
maybe
I
don't
remember
I
just
remember
there
was
a
little
bit
more
competition
with
docker
and
now
at
this
point
I'm
like
I
wish
that
competition
was
still
around.
A
A
C
Does
that
change
any
of
our
like?
I
guess
it
doesn't
really,
because
all
of
our
ci
stuff
is
done
on
linux.
So,
but,
like
I
was
wondering,
do
we
need
to
test
against?
Do
we
need
to
do
tests
against
podman?
A
Yeah,
I
I
wouldn't
be
opposed
to
it
just
to
elaborate
on
that,
a
little
bit
more.
We
do
have.
We
do
run
them
on
linux,
but
we
also
run
them
on
mac.
What,
but
I
think
we
don't
do
yeah.
We
don't
do
the
desktop
portion
or
the
docker
portion
in
mac,
but
definitely
on
windows.
We
do
right
so
on
windows,
we
do
run
docker
desktop,
and
so
that's
going
to
be
interesting
as
well.
C
I
think
I
think
the
project
probably
falls
under
the
free
license.
Name,
I
don't
know-
or
maybe
that's,
whoever,
whoever
we're
using
the
vendors
problem.
A
Right
when
someone
tells
us
that
we're
we
should
be
looking
at
something
different,
then
I
think
at
least
the
windows
one.
I
guess
maybe
those
aren't
as
as
important
right.
C
Well,
I
mean
I
I
I
feel
like
there's
that
I
don't
know
how
much
it
is
for
build
packs,
but
I
know
windows
is
having
still
a
large
target
audience
for
like
our
customer
base,
so
they
will
be
coming
at
us,
we'll
just
send
them
to
you.
There
you
go
yeah.
A
Tell
them
to
make
a
pull
request,
we'll
accept
it.
Yeah.
C
Yeah
I
mean
I
imagine:
windows
will
probably
be
very
affected
by
a
lot
of
these
changes.
I
I
don't
really
know
what
the
what
answer.
A
C
C
Like
the
lower
level
language
that
is
used
by
the
docker
engine,
but
does
that
mean
I
can't
use
a
build
kit
thing
on
podman.
A
Yes,
that
is
very
much
true.
Podman
would
not
support
build
kit,
unless
you
know
that's
how
they
implemented
it,
but
build
kit
is,
is
underlying
and
it's
linux
native
right,
so
it
runs
inside
of
the
vm.
Essentially,
if
you're
thinking
like
a
docker
or
sorry,
yeah
docker
desktop
scenario.
A
So
it's
running
so
you
could
run
it
as
a
standalone
thing
in
linux,
but
yeah
it
doesn't
necessarily
work
on
mac,
standalone
and
yeah.
I
guess
for
me
with
this
in
mind
and
maybe
thinking
that
it's
possible
that
the
what
is
it
called
the
user
share.
The
market
share
of
docker
drops
because
people
will
look
for
alternatives,
whether
it
be
podman
or
something
else.
I
do
wonder
whether
or
not
it's
as
important
as
it
was
earlier
this
year.
C
Yeah,
I
know
that's
a
good
question,
so
pot
podman
build
supports
dockerfile,
yes,
yes,
yeah,
but
not
build.
A
Yet
yeah
correct,
well
yeah,
I'm
trying
because
basically
build
kit
supports
docker
file
as
well
right.
It's
like
it
has
that
sort
of
interoperability.
C
Yeah,
I'm
just
wondering,
like
I,
don't
know
all
the
relationships
in
my
head.
I
just
know,
like
kind
of
on
the
surface,
what
a
thing
does,
but
is
it
like
kind
of
the
like
java
vendor
situation
like
in
theory,
you
can
run
this
thing,
but
the
implementation
underneath
of
like
open,
jdk
versus
like
oracle
jdk
versus
like
ibm's
jdk,
is
different,
but
in
theory
the
java
code
should
be
the
same.
Is
that
the
same
for
dockerfile
like
podman,
has
their
actual
implementation
and
does
not
just
use
a
reference
implementation.
A
Right
so
I
don't
know
what
podband
is
using,
for
instance
like
podman
could
be
using
conoco
right
or
and
or
it
could
literally
be
using
build
kit.
We
just
don't
know
right,
and
so
I
think
maybe
that's
just
part
of
investigating.
D
D
I
have
the
bill
kit
behind
it,
and
then
there
are
some
cool
features
for
developer,
putting
those
two
things
together
right,
so
we
were
trying
to
okay,
let's
put
instead
of
building
the
source
code
with
the
docker
file,
you're
going
to
be
able
to
build
it
with
our
tool,
and
so
we
have
like
the
vh
code
built
the
bill
kit
here
and
then
we
have
buildbacks
right
more
or
less
it's
where
all
the
potential
for
integrating
with
buildkit
is
helping,
at
least
that
that's.
I
I'm
not
sure
it's
also
bill
get
affected
with
this.
D
A
D
D
I
mean
from
my
perspective,
we
were
trying
to
reach
that
use
cases
right,
developer,
developer
wants
to
run
inside
this
inner
loop
stuff
and
we
want
to
tell
the
developer.
Yes,
if
you
want
to
build
your
code,
you
can
use
buildback
instead
of
the
dockerfile
right.
We
can
help
you
with
that,
and
we
can
integrate
with
this
thing,
and
this
thing
already
have
ecosystem
of
tools
that
you
can
use
and
you're
happy
using
it.
So
keep
using
that,
but
just
build
the
code
with
us,
not
with
the
dockerfile.
A
So
yeah,
if
I,
if
I
remember
correctly,
the
idea
is
that
by
us
having
the
build
kit
support
inside
of
the
essentially
the
docker,
daemon
or
docker
desktop
was
that
it
would
be
a
more
cohesive
experience
where
they
don't
have
to
install
it
say
like
pack
or
have
kpac
or
anything
like
that,
and
they
would
just
say
you
know,
build
and
it
would
just
magically
say:
okay.
Well,
this
is
a
what
is
it
called?
A
This
has
a
project
tumble
or
a
docker
file
that
basically
has
a
different
annotation,
and
so
therefore
it
would
use
cloud-native
build
packs
behind
the
scene
right.
So
I
think
that
was
from
a
user's
perspective
and
user's
perspective.
That
was
the
nicety
there.
A
Now,
as
I
was
thinking
through
some
of
this
of
whether
or
not
build
kit,
is
still
a
priority.
I
think
certain
parts
are
still
a
priority,
maybe
not
directly
related
to
build
kit,
but
the
idea
of
oci
layout
support
cycle.
That's
like
we're
important
right,
yeah,
that's
yeah
yeah
for
both
us,
the
platform
team
and
the
implementation
team.
Like.
D
Yeah,
yes,
that's
that's
our
feature,
I'm
still
working,
but
it's
yeah.
It's
it's!
It's
a
pretty
good
one
because
open
the
door
to
do
different
things
for
different
platforms.
With
that
image
on
the
file
system
in
the
oci
format,
they
we
can
do
different
things
with
it.
Whatever
they
want,
you
can
do
it
right.
You
have
the
image
instead
of
the
image
in
the
registry.
Here
it
is
and
it's
this
format-
and
you
can,
you
know,
do
whatever
you
want
with
it
so
yeah.
D
That's
that
feature
I'm
still
working
on
it,
I'm
doing
some
tests
and
but
I'm
moving
forward,
but
yes,
that
one,
I
believe,
is
not
affected,
but
this
stuff,
because
it's
something
we
will
add
it
and
into
the
features
of
life
cycle,
not
sure
if
we
want
I'm
working
on
also
on
back
right
with
the
flag
on
back
and
if
you
run
it
with
back
and
then
here
it
is
in
the
the
the
image
and
the
file
system,
not
sure
if
it's
useful,
but
it's
more
it's
it's
it's
more
easy
to
test
the
code
having
someone
that
it's
calling
the
life
cycle
and
doing
the
job.
A
If
we
get
that
feature
for
free
we'll
take
it,
I
only
say
that,
as
I
know
that
you
can
use,
is
it
scopio
or
something
like
that
where,
basically,
then
it
could
take
file
system,
oci,
layout
format
and
actually
throw
it
up
into
different
registries?
Or
are
you
know,
different
articles
and
stuff
open
is
a
pretty
good,
manipulator
or
mover
of
images
in
different
formats.
So
I
think
again
to
your
point:
people
could
do
whatever
they
want
with
it.
A
At
that
point,
right
yeah,
I
mean
like
it
has
to
be
in
a
registry
when
it
has,
or
it
has
to
be
in
a
dr
damon.
It
just
kind
of
gives
a
further
escape
hatch
into
what
they
want
to
do
with
it.
Yeah
yeah
cool
so
again,
we'll
take
it
if
you're
building
it
already
yeah.
C
So
it
looks
like
you
can
use
build
kit
with
paw
man,
but
it's
not
like
out
of
the
box
like
you
need
to
basically
set
up
the
build
kit,
daemon
and
basically
point
it
to
your
the
podman
uri
versus
the
docker
one
under
the
hood
from
what
it
looks
like
and
then
just
googling
really
quickly
from
an
article
a
few
days
ago,
like
podman,
I
think,
will
do
a
build
but
does
not
support
all
of
the
features
from
build
kit.
So
some
things
like
caching
don't
work
according
to
that
article.
C
Obviously
it's
not
necessary,
but
probably
nice,
so
there's
probably
some
gotchas
and
things.
But
I
guess
it
is
good
that
the
build
kit
repo
has
a
reference
to
pop-in
of
like
how
to
make
this
work
with
pubmed.
But
it
will
be
a
it
does.
Look
like
it's
not.
It
is
not
a
thing
that
just
out
of
the
box
like
they
people
will
have
to
basically
run
the
daemon
and
repoint
it.
C
Yeah,
I
think
those
are
mostly
good
signs.
Yeah,
I
mean
obviously
don't
know
what
the
plans
or
long-term
stuff
is
with
all
these
things,
but.
A
A
All
right
cool,
so
anything
else.
I
think
we're
at
the
halfway
point.
C
I
had
not
like
a
probably
in-depth
topic,
but
a
thing
that
came
up
from
just
working
with
folks
on
my
side
of
the
fence.
We
were
debugging
they're,
just
like
trying
to
get
up
and
starting
running
and
going
through
the
built
pack,
author
tutorial
with
pac,
and
one
things
that
kind
of
came
up
was
the
program
they
had
was
basically
like
throwing
an
exception.
C
For
both
build
and
detect,
but
until
we
replace
detect
with
like
just
a
very
simple
bash
thing
that
wasn't
throwing
an
exception,
we
could
see
that,
since
it's
like,
it
does
like
the
life
cycle
thing
where
it's
the
same
binary,
that's
kind
of
similar
to
whatever
for
both
detect
and
build
like.
We
couldn't
see
the
exception
by
default,
when
we
just
ran
pack
build
from
the
detect
phase.
C
Is
that
a
platform
level
thing?
Because
I.
C
Like
hardcoded
in
the
spec
right
like
zero
and
100
explicitly
for
fail
and
success,
I
wonder
like
if
exceptions
or
things
are
coming
out,
that
are
not
things
in
the
spec.
If
we
could
raise
those
by
default.
C
Yeah,
like
you,
can
definitely
see
it
with
verbose,
but
I
think
for
at
least
for
that
person
getting
started
was
definitely
not
intuitive,
that
you
needed
to
do
that.
C
Like,
like,
I
guess
to
them,
it
just
looked
like
their
detect
was
failing
right.
It
has
written
the
spec
right
that
only
like
zero
100
are
the
error
codes
that
you're
supposed
to.
A
C
For
the
attack
phase,
but
I
wonder
if
there's
a
way
that
is
step
compliant
where,
if
there
are
error
codes
that
are
unexpected
or
something
that
pack
could
potentially
raise
them,
what
that
we're
both
just
a
topic
discussion.
A
So
what
is
there
a
reason
why
we
wouldn't
want
to
just
promote
any
error
that
occurs.
C
Yeah
here
it
is,
I
can,
when
I
share
your
screen,
yeah
show
my
screen
found
it.
Let's,
like
make
sure
I
share
the
right
window
here.
We
go,
it
says
here
for
detection
pass
is
zero.
Obviously
fail
is
a
hundred
and
basically
anything
else
that
is
not
a
hundred
or
zero
is
like
a
thing
that
is
unexpected
right
and
I'm
wondering
if,
if,
like
anything,
falls
under
this
bucket,
if
we
could
basically
raise
or
display
something
there
for
peck.
A
C
Yeah,
I
guess
what
did
you
have
in
mind
for
user
friendly?
Because
I.
A
C
In
this
case,
this
is
like
not
a
user
error
in
the
sense
like
as
an
application
builder.
This
is
a
probably
I'm
a
build
pack
author.
For
me,
I
am
an
application
developer
and
I'm
using
builtpack
that
it's
like
blowing
up
but,
like
it
looks
like
to
me
the
bill
pack.
I
feel
like
in
that
case,
where
you're
in
the
non-zero
100.
C
It
looks
like
the
bill
packs
performing
normally,
but
it's
clearly
not
because
it's
like
not
raising
one
of
the
two
error
codes
that
are
expected
right
all
right
and
I
think
that's
like
where
the
confusing
thing
is
it's
like.
It
tells
me
that
no
build
pack
groups
successfully
detected,
which
is
100
true,
but
it
doesn't.
It
looks
like
it
just
the
bill
pack
failed
normally
right,
and
I
guess,
when
you're
talking
about
user-friendly
error
messages,
what
do
you
mean?
A
So
I
posted
the
link
on
there
and
it
was
more
or
less
that
again.
This
is
a
more
holistic
idea,
but
that
there's
other
you
know
software.
I
believe,
like
things
like
npm
or
firebase,
where,
when
an
error
occurs,
they
kind
of
give
you
guidance
in
a
lot
of
cases
where
they
say.
Oh,
this
was
most
likely
because
something
like
this
happened
there's
a
link
to
documentation
around
this
sort
of
error
that
occurs
right.
A
C
I
see
gotcha
yeah.
I
think
this
makes
sense,
but
I
feel
like
the
some
of
the
maybe
differences
from
at
least
like
pancreatic
building
other
things
is
like
these
are
probably
coming
from
pac
or
the
platform
of
like
here's,
the
thing
we
can
document
or
link
to
and
that
not
that
it
doesn't
apply
to
the
thing
I
suggested,
but
the
thing
I
suggest
that
I
feel
like
is
more
of
a
like.
C
This
means
you
have
a
problem
right
like
this
is
why
I
think
it
would
fit
into
kind
of
this
broader
thing,
but
I
I
do
think
this
is
more
encompassing
of
like
oh
you're,
just
you
as
a
user,
doing
something
wrong
where,
in
the
case
of
I
feel
like
this
other
thing,
it's
like
the
bill
pack
is
doing
something
wrong
which
may
or
may
not
be
you
right
right,
depending
on
who
the
who
that
person
is
right.
A
Yeah,
yeah
and
and
again
I
think
as
the
more
I
think
about
it.
It's
also
about.
A
How
easy
it
is
to
implement
the
e
the
complexity
involved,
so
for
the
one
that
you're
referring
to
it
should
be
extremely
easy
right.
It
could
be
like
a
good
first
issue,
just
if
it's
one
of
these
exit
codes,
just
print
out
the
standard
out
or
standard
error,
I
believe
yeah
and
then
for
the
one
that
I
proposed
or
I
linked.
It
would
be
more
like
a
maybe
a
mentorship
program,
type
issue
right
where
we
kind
of
detail
exactly.
We
have
somebody
go
through
and
see.
A
A
Yeah
cool!
Do
you
want
to
create
the
issue
for
that
and
then
just
probably
just
get
the
good
first
issue
label
on
that.
D
C
I
had
wasn't
a
big
thing,
but
definitely
was
a
just
user
experience
thing
that
I
think,
will
save
a
lot
of.
I
think
new
bill
pack,
authors
time
when
they're
and
probably
actually
old,
bill
pack
author,
I
feel
like
that's.
It's
really
annoying
to
buy
and
detect
things.
I
think
when
it
doesn't
look
anything's
going
wrong.
A
Yeah,
I
don't
think
I've
I've
taken
that
much
time
to
build
build
packs
other
than
the
sample
build
packs
so
like
I
should
do.
A
There
you
go,
you
got
that
going
for
you,
yeah
yeah,
I
feel
like
I
should
do
something
like
joe
did
like
do
something
very.
C
A
C
A
A
Anyway,
enough
of
my
banter
all
right
anything
else
for
this
meeting.