crun - A fast and lightweight fully featured OCI runtime and C library for running containers

  •        12

A fast and low-memory footprint OCI Container Runtime fully written in C. crun conforms to the OCI Container Runtime specifications (https://github.com/opencontainers/runtime-spec).

https://github.com/containers/crun

Tags
Implementation
License
Platform

   




Related Projects

runc - CLI tool for spawning and running containers according to the OCI specification

  •    Go

runc is a CLI tool for spawning and running containers according to the OCI specification. runc depends on and tracks the runtime-spec repository. We will try to make sure that runc and the OCI specification major versions stay in lockstep. This means that runc 1.0.0 should implement the 1.0 version of the specification.

runtime-spec - OCI Runtime Specification

  •    Go

The Open Container Initiative develops specifications for standards on Operating System process and application containers. The specification can be found here.

runtime - OCI (Open Containers Initiative) compatible runtime using Virtual Machines

  •    Go

cc-runtime is the next generation of Intel® Clear Containers runtime. This tool, henceforth referred to simply as "the runtime", builds upon the virtcontainers project to provide a high-performance standards-compliant runtime that creates hardware-virtualized containers which leverage Intel's VT-x technology.

cc-oci-runtime - OCI (Open Containers Initiative) compatible runtime for Intel® Architecture

  •    C

Now that the next-generation runtime has been released, this project is now in maintenance mode. All users are encouraged to switch to the new cc-runtime runtime. Installation and upgrade information is available on the new runtime's wiki.

cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

  •    Go

CRI-O is meant to provide an integration path between OCI conformant runtimes and the kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of CRI-O is tied to the scope of the CRI.This is an implementation of the Kubernetes Container Runtime Interface (CRI) that will allow Kubernetes to directly launch and manage Open Container Initiative (OCI) containers.


cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface

  •    Go

CRI-O is meant to provide an integration path between OCI conformant runtimes and the kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of CRI-O is tied to the scope of the CRI. This is an implementation of the Kubernetes Container Runtime Interface (CRI) that will allow Kubernetes to directly launch and manage Open Container Initiative (OCI) containers.

gvisor - Container Runtime Sandbox

  •    Go

gVisor is a user-space kernel, written in Go, that implements a substantial portion of the Linux system surface. It includes an Open Container Initiative (OCI) runtime called runsc that provides an isolation boundary between the application and the host kernel. The runsc runtime integrates with Docker and Kubernetes, making it simple to run sandboxed containers. gVisor takes a distinct approach to container sandboxing and makes a different set of technical trade-offs compared to existing sandbox technologies, thus providing new tools and ideas for the container security landscape.

runc - CLI tool for spawning and running containers according to the OCI specification

  •    Go

runc is a CLI tool for spawning and running containers according to the OCI specification.

firecracker-containerd - firecracker-containerd enables containerd to manage containers as Firecracker microVMs

  •    Go

This repository enables the use of a container runtime, containerd, to manage Firecracker microVMs. Like traditional containers, Firecracker microVMs offer fast start-up and shut-down and minimal overhead. Unlike traditional containers, however, they can provide an additional layer of isolation via the KVM hypervisor. To maintain compatibility with the container ecosystem, where possible, we use container standards such as the OCI image format.

runv - Hypervisor-based Runtime for OCI

  •    Go

runV is a hypervisor-based runtime for OCI. runv by default uses qemu to start virtual machines and makes use of KVM if it is supported. Please make sure qemu is installed on the machine.

openstorage - A multi-host clustered implementation of the open storage specification

  •    Go

OpenStorage is a clustered implementation of the Open Storage specification and relies on the Docker runtime. It allows you to run stateful services in Linux Containers in a multi-host environment. It plugs into CSI and Docker volumes to provide storage to a container and plugs into Kubernetes and Mesosphere to operate in a clustered environment. When you install openstorage on a Linux host, you will automatically get a stateful storage layer that integrates with CSI or the Docker runtime and operates in a multi host environment. It starts an Open Storage Daemon - OSD that currently supports CSI and DVDI and will support any Linux container runtime that conforms to the OCI.

img - Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder.

  •    Go

Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder. img is more cache-efficient than Docker and can also execute multiple build stages concurrently, as it internally uses BuildKit's DAG solver.

ignite - Ignite a Firecracker microVM

  •    Go

Weave Ignite is an open source Virtual Machine (VM) manager with a container UX and built-in GitOps management. Ignite makes Firecracker easy to use by adopting its developer experience from containers. With Ignite, you pick an OCI-compliant image (Docker image) that you want to run as a VM, and then just execute ignite run instead of docker run. There’s no need to use VM-specific tools to build .vdi, .vmdk, or .qcow2 images, just do a docker build from any base image you want (e.g. ubuntu:18.04 from Docker Hub), and add your preferred contents.

railcar - RailCar: Rust implementation of the Open Containers Initiative oci-runtime

  •    Rust

If you build using stable instead of nightly, the set_name feature will be disabled and the init process inside the container will not be named rc-init when viewed via ps or /proc/$pid/cmdline.

iotedge - The IoT Edge OSS project

  •    CSharp

Welcome to the home of IoT Edge. IoT Edge moves cloud analytics and custom business logic to devices so that your organization can focus on business insights instead of data management. Enable your solution to truly scale by configuring your IoT software, deploying it to devices via standard containers, and monitoring it all from the cloud. This repository consists of three main projects: the Edge Agent, the Edge Hub, and the IoT Edge Security Daemon.

clair - Vulnerability Static Analysis for Containers

  •    Go

Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get stable binaries.Clair is an open source project for the static analysis of vulnerabilities in application containers (currently including appc and docker).

iot-edge - Azure IoT Edge

  •    C

The Azure IoT Gateway SDK was our first step to enabling edge analytics in IoT solutions. We’re doubling down on, and expanding, this vision as explained in Satya’s Keynote at the Build conference and Sam George’s blog post. As part of this evolution, the SDK is becoming an extensible product you can use instead of a set of code you build. To reflect this, we’re changing the name to Azure IoT Edge.This similarity means that existing solutions can evolve with the product! There will be some infrastructural changes. For example: modules will run in Docker containers and the broker used to pass messages between module code will move to a lite version of IoT Hub running locally in a module. The vast majority of this is shielded from both a module developer and gateway developer.

pouch - Pouch is an open-source project created to promote the container technology movement.

  •    Go

Pouch is an open-source project created by Alibaba Group to promote the container technology movement. Pouch's vision is to advance container ecosystem and promote container standards OCI(Open Container Initiative), so that container technologies become the foundation for application development in the Cloud era.

runq - run regular Docker images in KVM/Qemu

  •    Go

runq is a hypervisor-based Docker runtime based on runc to run regular Docker images in a lightweight KVM/Qemu virtual machine. The focus is on solving real problems, not on number of features. runq requires a host kernel >= 4.8 with KVM and VHOST_VSOCK support enabled. The easiest way to build runq and to put all dependencies together is using Docker. For fast development cycles a regular build environment might be more efficient. For this refer to section Developing runq below.

image-spec - OCI Image Format

  •    Go

The OCI Image Format project creates and maintains the software shipping container image format spec (OCI Image Format). The specification can be found here.