►
From YouTube: OCI Weekly Discussion - 2022-04-28
A
A
B
B
B
B
Do
you
see
the
pr
that
winston
posted
about
moving
the
descriptor
and
all
that
to
distribution?
That
was
an
honesty
right.
A
A
A
I
think
the
idea
is
image.
Spec
people
are
pushing
to
say
this
is
just
the
definition
for
the
media
type
for
an
image
manifest
and
an
index.
I
see
they
there's
a
push
to
kind
of
really
constrain.
What's
in
that
one
spec,
okay
and
since
distribution
came
later,
it
didn't
have
things
that
image
spec
nia
to
even
do
his
own
job,
and
so
now
they
have
distribution
spec,
I
think,
there's
a
push
to
say:
hey.
We
got
this
new
space
we
can
put
stuff
over
on.
Let's
move
it
over
get
out
of
here.
I
see.
A
It's
basically
the
it's.
The
sneaker
net
distribution
here
is
what
distribution
is
if
you've
got
a
registry.
So
maybe
it's
just
saying:
okay,
and
if
you
don't
you
want
to
secret
across
this,
is
how
you
deal
with
the
file
system.
I
see
in
my
own
code.
I
treat
an
image
layout
file
system
layout
as
basically
a
local
registry
or
sorry
local
repository.
B
To
specify
how
it
can
be
used
like
there's
this
hidden
thing,
that
an
ocr
layout
is
all
under
one
repository
right:
multi-repository
layouts
are
not
supported
like
you,
you
docker.
Does
this
magic
tagging
thing
for
repository
names
and
all
that
so
distribution
does
handle
repository
scope.
But
what
we're
saying
is
if
a
repository
needs
to
be
file
laid
out,
then
we
can
use
the
oci
layout,
but
the
access
pattern
is
still.
A
B
Yeah
we
have
the
same
problem,
so
that's
why
I
was
thinking
like
if
we
were
to
put
this
in,
we
need
to
probably
have
a
conformance
test
as
to
what
can
it
test
right,
like
you
have
a
layout?
How
do
you
access
it?
What's
the
expectation
of
the
layout,
also
from
a
distribution
standpoint,
I
understand
from
an
image
layout
standpoint:
it's
pretty
straightforward
from
a
file
system
per
se
like
what
does
it
mean
for
distribution
to
actually
have
a
file
system
layout
is
how
do
we
even
need
conformance
test
for
this?
A
I
don't
know
if
you
need
it
or
not,
clients
might
need
it,
but
a
server
a
server
wouldn't
need
it
from
their
side
of
saying:
hey,
I'm
a
registry
server,
there's
nothing
for
them
to
do.
For
that.
Spec.
A
B
A
A
A
B
A
It's
a
way
to
sneakernet
to
transmit
anything
via
the
file
system,
instead
of
on
a
registry
api
that
you
would
normally
store
in
a
registry,
and
so
I
don't
want
to
scope
it
to
just
images
because
it
spans
more
than
images
if
we
start
defining
artifacts
and
other
stuff
like
that,.
A
B
A
A
Cross-Supported,
okay
I'll
give
you
that
one,
but
otherwise
you
know
authentication
all
that
stuff
is
always
mostly
scoped
to
you've
got
access
to
just
this
one
repository
and
so
yeah.
If
you
wanted
to
have
multiple
of
these
things,
it
would
end
up
being
two
different
directories
and
yeah.
B
The
the
other
challenge
is
that
the
concept
of
reference,
the
first
part,
has
to
be
either
the
ftd
and
other
repository,
so
references
by
themselves
don't
work
here.
It
doesn't
translate
directly
to
a
reference
right.
You
have
a
notion
of
a
tag
only
so
a
fully
qualified
reference
or
a
partially
qualified
reference
does
not
actually
map
to
this.
So
you
need
to
know
how
to
construct
the
reference
in
some
way
also.
B
So
the
problem
is
what
I'm
trying
to
say
is
that
there's
a
little
bit
of
a
handshake
of
what
the
image
layout
represents
and
what
a
client
can
expect
by
virtue
of
being
in
a
directory,
it
doesn't
mean
that
the
reference
the
directory
is
the
name
of
the
repository
or
how
it's
actually.
So
that's
the
other
connotation
sorry
about
that
dogs
are
going
crazy.
No.
A
A
I'm
pulling
up
a
sample
right
now,
so
I
can
show
you
not
only
all
my
failing
test
cases
but
also.
A
A
B
Yes,
sorry,
I
had
to
run
somebody
who
came
yeah,
so
I
think
what
you're
doing
is
kind
of
like
linking
through
the
index
station
right
the
references
at
this
point.
What
would
you
just
show.
A
A
Possibly
we
could
also
go
out
there
and
say
hey
if
you're
pushing
up
a
reference.
There
needs
to
be
some
other
object
in
this
index.
In
addition
to
all
these
manifest
things-
and
maybe
that
can
be
another
array
entry
in
here
in
addition
to
manifest-
you
might
have
references
that
makes
makes
sense-
I
I
think
I
see
what
see.
B
Where
you're
going
with
this,
actually
I
was
talking
about
the
fact
that
the
definition
of
a
reference
is
it
has
a
repository
name,
followed
by
a
tag
right,
so.
B
Right
and
but
with
the
image
layout
with
the
image
layout
spec,
you
cannot
use
a
reference
to
access
anything
in
the
index.
You
have
to
kind
of
strip
off
the
repository
part
now
and
only
use
the
tag
to
look
at
the
index
versus
the
all.
All
references
should
be
able
to
qualify
to
something
right
and
that
becomes
a
little
more
tricky
here.
A
B
So
if
you
were
to,
if
you
were
to
look
at
if
I
were
to
say
access
this
image
from
this
index,
how
do
you
qualify
that
image
like
that?
So
you
assume
that
the
first
part
is
a
directory
right.
B
B
I
think
the
just
clarifying
that
in
the
image
layout
or
whatever
you
want
to
call,
it
would
be
good
that
the
reference
actually
translates
to
a
directory
plus
the
tag,
not
just
because
the
index
doesn't
have
a
notion
of
a
repository
versus
in
distribution.
You
always
have
a
reference
that
you
can
that
you
can
kind
of
work
with
in
some
way.
That's
that
was
the
other
thing
that
I
was
kind
of
alluding
to,
because
you
have
to
the
the
repository
object
does
exist
against
which
you
can
do
the
query.
A
B
And
the
the
the
rejects
and
the
what
you
say,
the
conformance
actually
has
that
so
now
you
get
into,
can
the
reference,
be.
I
mean
all
the
casing
and
all
that
also
becomes
a
challenge
here.
So.
A
B
I
I
think
the
the
there
is
a
specification
of
how
the
repository
names
can
or
cannot
be
right.
There's
there
are
characters
that
are
not
allowed
and
whatnot.
So
I
think
the
mixing,
for
example,.
B
It
also
makes
sense
versus
for
registries,
there's
an
implicit
assumption
that
the
first
part
is
the
reference
followed
by
the
tag
right
and
they
split
that
http
path
in
a
specific
way
to.
B
No,
I
totally
get
it,
but
but
it's
probably
good
to
just
call
out,
because
I
know
that
singularity
images
and
all
that
they
use
a
very
similar
locker,
colon
oci
colon
and
things
like
that
as
well.
So
yeah.
A
Scope
here
started
getting
a
little
bit
into
that
as
well.
They've
got
their
own
syntax
over
there
very
similar
with
the
docker,
colon
and
some
other
stuff.
A
A
B
Yeah,
so
it
was
actually
interesting
because
I
could
probably
share
something
we
did
internally
for
transferring
images
across
air
gap
where
we
create
a
catalog
json,
but
that's
cross
repository
that
has
another
another
image
or
another
file,
that's
like
index,
but
it
has
repo
information
as
well,
so
that
you
can
actually
transfer
multiple
repositories.
B
The
the
image
layout
is
now
limited
to
that
one
repository
scope
and
that's
why
it
makes
it
simple.
But
the
moment
you
want
to
kind
of
like
move
a
helm
chart
over
with
the
images
it
kind
of
falls
apart.
So
you
need
to
do
multiple
tires
and
you
got
to
keep
all
of
them
kind
of
like
going
forward,
so
it
would
be
anyway,
that's
more
like
if
we
propose
and
if
we
discuss
it.
That
would
be
interesting.
B
Yeah,
I
know
that's
why
I'm
being
really
cautious
of
who
would
feel
what
it
could
kind
of
like
explode
in
scope
and.
A
I
think
I've
seen
putting
putting
the
repository
in
there
at
some
point.
B
Yeah
and
the
I
believe
that
the
runtime
layout
has
a
repositories
file
that
holds
this
information
in
some
way,
but
not
in
the
not
in
how
we
store
it
or
in
the
image
spec
layout
itself.
So
there
are
multiple
ways
to
do
this,
but
anyway,
I
think
I
need
to
drop
off.
I
have
another
call
at
10
30.
Unfortunately,
all.