Reference spec

[James Hewitt-Thomas]

Hi all,

We were talking in the distribution project about the reference package and where to move it to. There are currently a number of users of the reference package who don't need to drag in the rest of the transitive dependencies required to run a repository so we're looking to put it in a new home.

https://github.com/distribution/distribution/issues/3587#issuecomment-1682178194

I thought it might be good to add a reference spec to the ones already maintained by OCI, and then to make the code in the distribution org the reference implementation of parsing/building/validating OCI container image references in go. I've put together some very basic thoughts of what kind of content this would have in it.

https://github.com/Jamstah/reference-spec/blob/main/spec.md

I'm interested in the thoughts of this community - is there a need/value in creating a new spec just to cover references?

Based on responses here, I guess the next step would be a formal proposal to the Technical Oversight Board (also on cc of this post).

James.

[Vincent Batts]

Ah yeah. The definition for the pullable reference is definitely needed.
And tie in with
https://github.com/containerd/containerd/blob/main/remotes/resolver.go#L30

I support this.

vb

>--
>To unsubscribe from this group and stop receiving emails from it, send an email to tob+uns...@opencontainers.org.

[Sajay Antony]

+1 on adding the definition for reference.

To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@opencontainers.org.