You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "PSU3D0 (via GitHub)" <gi...@apache.org> on 2025/05/31 17:44:23 UTC
Re: [I] new feature: Support OCI artifacts [opendal]
PSU3D0 commented on issue #5695:
URL: https://github.com/apache/opendal/issues/5695#issuecomment-2925495554
Any movement on this?
@NickCao thoughts on this path model?
```
oci://{registry}/{repo}/@{ref}/{inner?}
registry = ghcr.io | registry-1.docker.io | ...
repo = namespace/name
ref = <tag> | sha256:<digest> (OCI "reference")
inner = optional path *inside* the unpacked rootfs
```
Registry + repo acts like the bucket field in S3.
We reuse the first path segment for the OCI reference (tag / digest)
A plain list("/") therefore returns tags and digests - matches what most users expect when they "list a repository."
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org