Add Artifactory as a Compatible OCI Registry #394
Conversation
martinezlc99
requested review from
asmitbm,
FeynmanZhou,
sajayantony,
shizhMSFT,
SteveLasker,
vsoch and
TerryHowe
as code owners
martinezlc99
changed the title
Signed-off-by: lcmartin <[email protected]>
Signed-off-by: lcmartin <[email protected]>
martinezlc99
force-pushed
the
doc/add-artifactory
branch
from
f06e161 to
9e21330
Compare
|
@martinezlc99 BTW, is Artifactory compliant with OCI Spec v.1.1 or v1.0? |
|
The blog post for 12/23 said v1.0 |
@FeynmanZhou - as far as I know, Artifactory is OCI Spec v1.0. There is an OCI Spec v1.1 pre-release in the blog post referenced (since Dec 2023), but difficult to tell what's actually implemented. I am mainly using our Artifactory instance for devcontainer features, which is working very well. Is there a test I can perform to verify an OCI Spec v1.1 feature? Looking here, BTW, I am personally very excited about OCI registries and looking to learn more so we can start using at my day job. Any suggestions on how to learn more and potentially contribute would be welcome. |
|
Feedback on PRs and issue grooming is always appreciated @martinezlc99 . Meeting in ~3.5 hours as well https://oras.land/community/community_resources |
|
@martinezlc99 I checked that JFrog Artifactory is OCI v1.1 compliant because JFrog already passed the OCI v1.1 conformance test and uploaded its report to https://github.com/opencontainers/oci-conformance/tree/main/distribution-spec/v1.1/artifactory |
At my day job, we use Artifactory and have started to use it as an OCI registry. When researching this, it was not clear
orassupported Artifactory. This PR is to update the applicable documentation.Closes #393.
Closes #205.