Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap a basic OCI registry with devfiles from a devfile registry on github #143

Closed
johnmcollier opened this issue Sep 29, 2020 · 2 comments · Fixed by devfile/registry-support#2
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@johnmcollier
Copy link
Member

johnmcollier commented Sep 29, 2020

See if we can bootstrap a basic, proof of concept, OCI registry with devfiles from one of the devfile registries currently hosted on Github (either https://github.com/odo-devfiles/registry or https://github.com/eclipse/che-devfile-registry).

The new registry proposal outlines two approaches to push devfiles to an OCI registry. Based on those steps, see if we can package up a simple Docker image containing both the OCI registry and a couple devfiles as OCI artifacts.

Parent story: #82

@johnmcollier johnmcollier added the area/registry Devfile registry for stacks and infrastructure label Sep 29, 2020
@johnmcollier johnmcollier self-assigned this Sep 29, 2020
@johnmcollier johnmcollier changed the title Bootstrap an OCI registry with devfiles from a devfile registry on github Bootstrap a basic OCI registry with devfiles from a devfile registry on github Sep 29, 2020
@elsony
Copy link
Contributor

elsony commented Sep 30, 2020

@johnmcollier
Copy link
Member Author

johnmcollier commented Oct 2, 2020

I've got a very simple proof of concept up at https://github.com/johnmcollier/oci-devfile-registry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants