►
From YouTube: CNB Sub-Team Sync: Platform: 2022-01-26
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
A
So
I
think
some
of
the
things
I
think
we've
gone
back
and
forth
with
that.
I
could
kind
of
start
off
with.
Are
these
yeah?
Yes?
Yes,
I
don't
know
if
you've
updated
your
your
comment,
but
I
want
to
kind
of
express
it
again,
maybe
maybe
here
and
see
if,
if
you
know
if
it
makes
sense
to
go
through
with
it
or
or
yeah
thinking,
I'm
missing,
but
I
guess
what
I
envision
is
when
you
run
like
this
layout
directory
or
this
layout
flag
that
we
could
pass.
A
What
do
you
have
an
example
here
that
we
could
just
pass
in
the
directory
like
whatever
directory
it
may
be,
that
we
want
it
in
yeah,
right
and
then
kind
of
the
inverse?
I
don't
know
if
it
makes
sense
to
have
a
default
directory
for
that
purpose
right.
So,
if
you
think
about
it,
if
we
get
rid
of
the
defaults
right,
okay,
okay,
okay
only
had
whether
this
environment
variable
is
present
and
filled
in.
A
B
Okay,
okay!
Yes,
I
believe
that
I
believe
I
deleted
comment
before,
but
yes
that
was
my
doubt.
If
we
wanted
to
provide
the
default
one,
then
how
how
I
mean
there
was
one
one,
one
scenario
there
that
I
need
the
flag
this
one.
If
we
provided
the,
if
we
provide
the
default,
then
okay,
I
will
need
both
input.
But
yes,
now,
if
we
said
no,
I
am
not
going
to
provide
any
default
value
and
if
you
enable
the
feature
with
the
flag,
then
you
have
to
tell
me
where
to
put
the
image.
B
A
I
I
mean
I
can't
speak
to
the
life
cycle,
but
the
way
I
envision
it
is
from
a
platform
set
of
things
like
yeah
right,
you,
let's
say
I'm
a
techton
task
or
whatever
right,
like
whatever
the
platform
might
be
even
pack
and
say
like
hey,
I
want
I
want
to
this.
Is
one
directory
will
always
be
mounted
right
and
it's
gonna
be
at
you
know,
slash
oci,
layout,
right
or
oci.
A
Okay,
this
oci
is
going
to
be
shared
across
every
single
build.
Doesn't
matter
right,
I
don't
care
okay
right
and
because
of
that,
I
would
then
want
to
specify
that
this
flag,
whether
it's
a
flag
or
the
environment,
variable
to
say,
okay,
I
everything
that
you
create
and
anything
that
you
want
to
resolve
or
search
for
as
far
as
images
goes
go
look
at
this
path,
which
will
be
slash,
oci,
okay,
right
and
now
the
next
build.
You
know
again
same
thing
like
so
we
could
share
stuff.
A
B
Right
and
I
did
actually
okay,
so
the
idea
will
be
okay.
If
you
use
the
layout
form,
you
will
be
lying
on
the
stream
value
with
the
the
path
you
want
me
and
the
other
one
you
mentioned
was
this
okay.
Maybe
I
don't
want
to
send
the
layout
flag
to
all
the
faces,
then
I
can
just
enable
maybe
one
environment
variable
and
say
this
is
the
this
is
the
path
and
then
lifecycle
will
say:
okay,
that
the
vitamin
by
the
ball
was
set.
Let
me
let
me
use
it
and
that's
it.
B
You
don't
have
to
to
send
through
the
value
through
the
the
the
flag,
okay,
got
it
yeah
yeah.
Let
me
do
that
change.
That's
that's
fine!.
A
Awesome,
let's
see
the
only
other
thing
that
I
I
felt
kind
of
I
was
wondering
if
we
could
find
a
different
format
is:
is
this
idea
of
using
the
sha
the
digest,
essentially
yeah
the
directory
structure
for
images,
and
this
is
something
I
haven't
thought
about
too
much,
but
part
of
me
kind
of
envisions
or
likes
the
idea
of
the
user
being
able
to
specify
either
paths
or
or
human
readable
names?
A
Okay,
so,
for
instance,
if
I
wanted
to
use
ubuntu
bionic
right,
I
I
should
be
able
to
say,
like
hey
my
run,
image
is
ubuntu
bionic
right,
whether
that
name,
whether
that's
a
uri
like
this
right
that
says,
oci
colon,
ubuntu,
colon
bionic.
A
Right,
like
is
that
doable
and
then
would
that
this
then
be
able
to
search
this
directory
structure
for
it.
B
B
Go
down,
I
believe
there
is
at
the
end
dimension.
Maybe
it's
on
the
copy,
just
click
on
the
copy
one.
B
A
A
B
B
And
then
I
just
I
I
at
the
beginning,
I
had
you
know
like
ubuntu
there
that,
and
that
was
the
root
folder
name,
and
then
I
said
okay.
Now,
if
I
I
was
thinking,
okay,
maybe
from
platform
perspective.
If
something
change,
then
maybe
if,
if
if
you
can,
you
know
have
a
way
a
quickly
way
to
to
make
so
that
this
folder
is
different
than
this
one.
I
don't
know,
maybe
you
have
ubuntu
and
you
did
something
to
the
ubuntu
image,
but
I
don't
know
from
user
perspective.
B
B
How
can
you
know
make
a
difference
on
them
just
based
on
the
name
and
that's
why
I
came
out
with
okay,
but
if
I
have
this
id,
which
is
going
to
be
if,
if
there
are
two
images
of
the
same
thing,
but
there
is
some
difference
between
them,
then
the
idea
is
going
to
tell
me
if
both
females
that
that
are
the
same
are
different.
Somehow.
B
Then
that's
why
I
that's
that's
why
I
put
the
image
id,
because
I
wanted
to
to
give
the
possibility
for
the
platform
perspective,
to
keep
maybe
maybe
different
image
of
the
same
thing
without
having
to
rename
the
root
folder
and
and-
and
I
don't
know
they
can
they
can
do
that
with
with
with
that
thing,
so
are
you.
A
Ubuntu
colon
latest-
and
I
had
just
like
ubuntu
dash
some
other
name
right
like
could
be,
could
be
yes,
and
both
of
them
are
the
exact
same
image.
With
the
exact
same
blobs,
the
only
difference
is
the
image
name.
A
B
Then
maybe
you
build
my
thing
right,
and
this
is
the
image
I
generate,
and
then
you
have
to
give
me
that
one
back
on
as
a
previous
image,
for
example,
and
if
I
generate
different
image
of
the
same
thing
and
I
call
them
all
of
them-
I
don't
know
foo,
then,
okay,
how
I
don't
know,
I
thought
that
maybe
keeping
the
digest
was
going
to
be
easy
for
the
platform
to
keep
track
of
them
and
share
layers
or
whatever
they
want
to
find
a
way
how
to
identify
that.
B
This
is
exactly
the
image
I
want,
or
I
need
a
different
one
or
a
modified
one
or
something
and
with
the
name,
if
I
put
human
readable
name,
maybe
I
was
not
able
to
differentiate
that.
So
I
wanted
to
make
clear
that
I
wanted
to
give
the
option
to
make
clear
to
the
platform
to
say
this
is
the
image.
Even
maybe
I
have
different
versions
of
it.
B
B
Yeah,
yes,
that's
and-
and
I
haven't
put
that
one
because
I
haven't
brought
the
exporter,
because
I
have
that
that
that
that
that
thing
I
was
thinking.
Okay,
the
user
is
going
to
give
me
a
human
readable
name.
Example
oci,
for
example.
Okay,
I'm
going
to
save
it.
Maybe
I'm
going
to
save
it
like
a
folder,
an
example
oci
image,
because
that's
what
you
tell
me
and
maybe
platform
can
do
something
with
that
right.
B
B
A
A
So
if
is
this
analyzed
yeah,
so
the
analyzer
you
give
it
example:
oci
it'll,
go
and
resolve
it
right
in
the
registry.
It'll
go
up
to
to
the
registry
and
it'll
pull
it
down
at
least
the
manifest
and
say.
Okay,
this
is
the
diff
id
right,
and
so
then
it
adds
that
def
id
to
one
of
the
metadata
labels
or
layers.
A
That
then
goes
on
to
the
next
step
or
next
phase,
and
then
it
essentially
ensures
that
that
is
the
digest
that
you
continue
to
use
or
the
exact
same
image
that
you
continue
to
use.
So
when
you
do
the
pulling
of
the
image
you
pull
it
now
by
that
digest,
right,
okay,
yes,
yes,
we
would
need
to
be
able
to
do
the
same
thing
here.
It's
like,
okay,
so
from
analyzer
perspective,
we're
gonna,
pass
it
a
human,
readable
name.
A
A
B
A
Yes
example:
yeah
example
oci
and
the
the
life
cycles
analyzer
is
going
to
search
for
it
in
the
layout
directory
oci
directory
right,
yes,
and
it's
going
to
find
one
right.
Let's
say
this
is
latest,
so
it
would
find
whatever
the
latest
is,
and
it
would
say
okay
now.
This
is
the
digest
of
that
latest
version,
and
now
it
would
have
to
then
be
able
to
go
back
for
the
next
phase.
Let's
say:
is
it
the
detector?
A
Yes
and
then
in
that
case
again,
this
is
where
I'm
a
little
bit
loose
on
exactly
what
happens
behind
the
scenes,
but
I'm
envisioning
that
it
will
have
to
reference
and
use
that
exact
same
image.
So
therefore
it
would
have
to
be
able
to
find
it
by
its
name
and
digest.
So
now
that
some
that's
a
kind
of
use
case
that
we
have
to
think
about.
When
we
look
at
this
okay,
will
I
be
able
to
find
the
image
by
name
and
digest.
B
Okay
and
no
no
exactly
now,
if
I,
if
the
routine,
then
if,
after
images
or
whatever,
where
platform
decide
to
put
the
image,
then
we
can
have,
for
example,
example
oci
and
then.
B
Yeah
then,
maybe
maybe
maybe
another
one
inside
with
the
digest
or
something
or
maybe
just
keep
that
one
without
the
digest
without
the
digest
was
the
first
thing
I
did.
Instead
of
calling
the
previous
image
and
the
run
image
with
the
sha
there
will
be,
you
will
have
oci
example
oci
and
maybe
ubuntu
bionic
and
that's
it.
That
was
the
first
one.
I
did.
B
A
A
A
Right
and
I
think
that's
where
I'm
hoping
we
can
get
away
with
this,
which
is
starting
to
leverage
what
scopio
has
defined
to
be
okay,
our
eyes,
which
again
it
sucks
that
we
can't
find
it.
A
Okay,
here
you
go
image
names.
Yes,
there
it
is
yeah
all
right.
So
if
we
have
these
image
names
right,
then
I
could
think
about
it
like
okay,
so
we
want
to
do
oci
right,
so
oci
path
tag
seems
reasonable
enough.
So
can
we
use
in
this,
like
in
your
case,
the
reference
here
oci
colon,
the
path
to
it
right?
Would
that
sense.
B
A
Okay,
past
okay,
that
makes
sense
this.
This
one
storage
manifest
layer,
turn
balls.
This
is
non-standardized
format:
okay,
non-standardized,
okay,
and
then
we
have
oca
archive.
A
A
B
A
A
A
Until
right,
so
this
will
give
us
the
image
name
here
and
then
inside
of
the
index.
That's
where
you
would
find
all
your
your
tags
right,
so
you
would
find,
let's
say
latest
or
bionic,
and
then
you
would
say:
okay,
this
is
my
bionic
one.
Now
this
is
the
digest
right.
I'm
assuming
digest
then
points
to
the
configuration.
A
B
A
Manifest
would
be
yes
this
this
part
here
yeah
and
then
you
would
have
additional.
What
is
it
called
the
container
configuration
here
and
you
would
have
all
your
layouts
here,
patients
yeah
right,
correct,
and
so
all
these
digests
right
this
whole
tree
that
we
just
went
down
right,
they're,
all
just
blobs
right.
So
in
our
case
here.
A
This
would
be
an
index
blob.