runtime-tools
image-tools
| runtime-tools | image-tools | |
|---|---|---|
| 4 | 2 | |
| 415 | 262 | |
| 1.0% | 0.0% | |
| 3.3 | 0.0 | |
| 8 months ago | about 1 year 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.
runtime-tools
-
Podman/buildah oci bundle
But there is another issue - machinectl doesn't know how to start oci-bundle. It would be nice to have a tool which would generate .nspawn file from config.json (apparrently, there is an open issue for that https://github.com/opencontainers/runtime-tools/issues/669)
-
Youki, a container runtime in Rust, passed all the default tests provided by opencontainers.
I think you might be looking at the gitignore for https://github.com/opencontainers/runtime-tools/blob/master/.gitignore , which is NOT the repo made by /u/utam0k. That's a large repo from opencontainers that includes many different things, so that .gitignore is bigger but by no means unreasonable.
youki, a container runtime in Rust I'm implementing, passed all the default tests provided by opencontainers. There are still many issues that need to be implemented, but it's getting fun. I think Rust to be a good choice for implementing container utilities. If you are interested, please refer to the motivation section of README for more details. I'd like to hear your opinions.
-
Crun: Fully featured OCI runtime and C library for running containers
crun runs the OCI validations tests on each PR.
The tests are maintained here: https://github.com/opencontainers/runtime-tools/tree/master/...
I guess this is the closest to be "certified compliant", but that is not enough for working with existing container engines as everyone just assumes runc is used
image-tools
-
Using "Non-Executing Containers"
Or you can low-level OCI tooling. I would bet there is a tool for that. https://github.com/opencontainers/image-tools
-
Podman/buildah oci bundle
Thanks, that one also generates oci image (not oci bundle). Apparently, there are couple of other tools which can be used to generate oci bundle: umoci (https://github.com/opencontainers/umoci) and image-tools (https://github.com/opencontainers/image-tools).
What are some alternatives?
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
umoci - umoci modifies Open Container images
singularity - Singularity has been renamed to Apptainer as part of us moving the project to the Linux Foundation. This repo has been persisted as a snapshot right before the changes.
clair - Vulnerability Static Analysis for Containers
containerd - An open and reliable container runtime
youki - An experimental container runtime written in Rust
gvisor - Application Kernel for Containers
runtime-spec - OCI Runtime Specification
runc - CLI tool for spawning and running containers according to the OCI specification