sarus
OCI-compatible engine to deploy Linux containers on HPC environments. (by eth-cscs)
runtime-spec
OCI Runtime Specification (by opencontainers)
sarus | runtime-spec | |
---|---|---|
2 | 11 | |
121 | 3,094 | |
4.1% | 0.9% | |
7.3 | 6.4 | |
14 days ago | about 1 month ago | |
C++ | Go | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
sarus
Posts with mentions or reviews of sarus.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-01-25.
-
Sarus VS Podman: comparison of both technologies
Sarus is An OCI-compatible container engine for HPC: https://sarus.readthedocs.io/en/stable/. At this point of view, it is very similar to use case of Podman.
-
Scaling Kubernetes to 7,500 Nodes
The problem with slurm is how it's typically used: ssh into a shared login node with a shared file system, auth is handled by the linux users mostly, submit jobs with sbatch. Kubernetes deployment feels much more modern and safe.
I have worked with containers + slurm, where the vendor libmpi is injected in the container runtime [1] by a hook, which gives you close to bare metal performance with some container goodness in terms of isolation and deployment.
[1] https://github.com/eth-cscs/sarus
runtime-spec
Posts with mentions or reviews of runtime-spec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-27.
-
The What, Why and How of Containers
> Well, no. When people say "containers", they always mean "Docker".
Not really/necessarily. https://github.com/opencontainers/runtime-spec
-
Containers - entre historia y runtimes
Otras iniciativas empezaron a surgir debido a la alta popularidad de los containers y debido a esto, en 2015 se crea OCI(Open Container Initiative) para definir un estandar para containers(runtimes e imagenes).
-
Docker is deleting Open Source organisations - what you need to know
Theoretically there could be a lot of new options that pop up. There is an Open Container Initiative that has a Runtime Specification that can be implemented. youki is one example of an OCI-compliant container runtime.
-
Container Deep Dive Part 1: Container Runtime
Open Container Initiative Runtime Specification aims to specify the configuration, execution environment, and lifecycle of a container. Source
- Podman + minikube
-
Podman/buildah oci bundle
How I can generate oci bundle that can be run with systemd-nspawn? I've tried podman/buildah push, but generated directory/archive is not an oci bundle (https://github.com/opencontainers/runtime-spec/blob/main/bundle.md). I've tried podman image mount, but config.json file is nowhere to be found. It looks like I am missing something simple.
-
Youki, a container runtime written in Rust that has passed all integration tests provided by OCI(Open Container Initiative).
In more detail, runC and youki need to implement this specification. https://github.com/opencontainers/runtime-spec
- Youki – OCI container runtime with support for cgroup2 written in Rust
-
Kubernetes vs Docker: Understanding Containers in 2021
A runtime specification that describes how to unpack and run a container. OCI maintains a reference implementation called runc. Both containerd and CRI-O use runc in the background to spawn containers.
-
Experimental implementation of container runtime in Rust
The immediate goal of this project(youki) is to pass all the default tests of the runtime-spec that the opencontainers is making. Of course, this is for my own learning, but I believe Rust is one of the best languages to implement a container runtime.