oras
imgpkg
| oras | imgpkg | |
|---|---|---|
| 8 | 1 | |
| 1,266 | 253 | |
| 3.3% | 5.9% | |
| 9.3 | 8.2 | |
| 4 days ago | 11 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oras
- Distribute Artifacts Across OCI Registries
- OCI image from dockerfile
-
RFC 6920: Naming Things with Hashes
Interesting, I'd not known of this RFC before.
Another example of a content-addressed data store could be OCI registries (more commonly known as container image registries). Using them to store arbitrary artefacts is quite well supported now: https://oras.land/
-
sbcl - require
See https://oras.land/
-
Ocicl – An ASDF system distribution and management tool for Common Lisp
> ... but still only supports one niche operating system.
1. Linux is not a niche in the target market for this project.
2. The project is written in Common Lisp with hard dependencies on SBCL-provided libraries[1], so there's reason to suspect it should work on other OSes supported by SBCL.
3. Sure, the presence of Makefile and sb-posix imply it requires a POSIX compliant OS, but Linux is not the only one that fits the bill.
4. The included Linux-only binary 'oras' is clearly a vendored artifact, not part of this project, and clearly an OCI client. A simple search shows it is indeed cross-platform[2].
Perhaps you should try what almost every Linux user has had to do when encountering software actually built for only one "niche" operating system that they want to use on their OS: look.
1. https://github.com/ocicl/ocicl/blob/170aff0/ocicl.asd#L34
2. https://github.com/oras-project/oras/releases
-
Looking for an artifact store for generic assets, rather than specially-formatted packages or containers. Thinking maybe ORAS, but wondering if there are other options.
oras isn't that unpopular, Helm is using it as an SDK for example. Here are other projects who are using it. https://github.com/oras-project/oras/network/dependents
- OCI Registry as Storage
imgpkg
-
Deploy Neo4J's APOC plugin with code thanks to CARVEL vendir
imgpkg - Bundle and relocate application configuration (with images) via Docker registries
What are some alternatives?
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
kapp-controller - Continuous delivery and package management for Kubernetes.
containerd - An open and reliable container runtime
kbld - kbld seamlessly incorporates image building and image pushing into your development and deployment workflows
distribution - The toolkit to pack, ship, store, and deliver container content
terraform-provider-carvel - Carvel Terraform provider with resources for ytt and kapp to template and deploy to Kubernetes
distribution-spec - OCI Distribution Specification
vendir - Easy way to vendor portions of git repos, github releases, helm charts, docker image contents, etc. declaratively
quicklisp-https
carvel - Carvel provides a set of reliable, single-purpose, composable tools that aid in your application building, configuration, and deployment to Kubernetes. This repo contains information regarding the Carvel open-source community.
watchtower - A process for automating Docker container base image updates.
secretgen-controller - secretgen-controller provides CRDs to specify what secrets need to be on Kubernetes cluster (to be generated or not)