Displaying 1 to 20 from 24 results

ctop - Top-like interface for container metrics

  •    Go

as well as an single container view for inspecting a specific container.ctop comes with built-in support for Docker and runC; connectors for other container and cluster systems are planned for future releases.

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.

lastbackend - System for containerized apps management. From build to scaling.

  •    Go

Last.Backend is an open source platform for containerized application management: from deploy to scale. This solution is based on container technology. All these runtimes are documented in runtime section, where are described all methods, types and algorithms.

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.

faasd - A lightweight & portable faas engine

  •    Go

faasd is OpenFaaS reimagined, but without the cost and complexity of Kubernetes. It runs on a single host with very modest requirements, making it fast and easy to manage. Under the hood it uses containerd and Container Networking Interface (CNI) along with the same core OpenFaaS components from the main project. faasd is just another way to runOpenFaaS, so many things you read in the docs or in blog posts will work the same way.

CRI-O - OCI-based implementation of Kubernetes Container Runtime Interface

  •    Go

CRI-O is an OCI-based implementation of Kubernetes Container Runtime Interface. 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.

udocker - A basic user tool to execute simple docker containers in batch or interactive systems without root privileges

  •    Python

A basic user tool to execute simple docker containers in user space without requiring root privileges. Enables download and execution of docker containers by non-privileged users in Linux systems where docker is not available. It can be used to pull and execute docker containers in Linux batch systems and interactive clusters that are managed by other entities such as grid infrastructures or externally managed batch or interactive systems. The INDIGO udocker does not require any type of privileges nor the deployment of services by system administrators. It can be downloaded and executed entirely by the end user.

circuit - Container Network Management

  •    Go

Circuit manages networks for runc.Circuit has been designed for flexibility. For example, the controller has been designed to be replaced. Circuit leverages CNI for setting up networking using various plugins such as bridge, ptp, etc. Define multiple CNI networks and connect/disconnect, load balance, etc.

runtime-tools - OCI Runtime Tools

  •    Go

oci-runtime-tool is a collection of tools for working with the OCI runtime specification. To build from source code, runtime-tools requires Go 1.7.x or above. oci-runtime-tool generate generates configuration JSON for an OCI bundle. OCI-compatible runtimes like runC expect to read the configuration from config.json.

tob - Technical Oversight Board (TOB)


The TOB is responsible for managing conflicts, violations of procedures or guidelines and any cross-project or high-level issues that cannot be resolved in the TDC for OCI Projects. The TOB shall also be responsible for adding, removing or reorganizing OCI Projects. In various situations (2.c, 6.h, 6.j, 6.n) the TOB shall hold a vote. These votes can happen on the phone, email, or via a voting service, when appropriate.

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

  •    C

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).

sriov - Simple standalone Docker Plugin implementation to demonstrate Clear Containers with SRIOV

  •    Go

This plugin supports Docker containers with runc or Clear Containers as the OCI runtime. The plugin is responsible for assigning a SRIOV Virtual Function (VF) into the container namespace. In the case of runc containers, the VF is directly usable by the container.

ctnr - rootless runc-based container engine

  •    Go

ctnr is a CLI built on top of runc to manage and build OCI images as well as containers on Linux. ctnr aims to ease system container creation and execution as unprivileged user. Also ctnr is a tool to experiment with runc features. Container networking is limited. With plain ctnr/runc only the host network can be used. The standard CNI plugins require root privileges. One workaround is to map ports on the host network using PRoot* accepting bad performance. A better solution is to use slirp4netns which emulates the TCP/IP stack in a user namespace efficiently. It can be used with ctnr via the slirp-cni-plugin. Once container initialization is also moved into a user namespace with slirp the standard CNI plugins can be used again. For instance the bridge can be used to achieve communication between containers (see user-mode networking).

magneto - Pipe runc (OCI compatible) events to a stats TUI (Text User Interface).

  •    Go

Pipe runc events to a stats TUI (Text User Interface). For installation instructions from binaries please visit the Releases Page.

netns - Runc hook (OCI compatible) for setting up default bridge networking for containers.

  •    Go

Runc hook for setting up default bridge networking. For installation instructions from binaries please visit the Releases Page.

riddler - A tool to convert docker inspect to the opencontainers runc spec.

  •    Go

A tool to convert docker inspect to the opencontainers/specs and opencontainers/runc. For installation instructions from binaries please visit the Releases Page.

eliot - Open source system for managing containerized applications in IoT device

  •    Go

This is early alpha version! There's not all features yet implemented, not heavily tested with different devices and code might get large breaking changes until the first release. Eliot is a open source system for managing containerized applications on top of the IoT device with an emphasis to usability, simplicity, security and stability. Eliot gives simplified app delivery, isolation and additional security to traditional installations.

go-runc - runc bindings for Go

  •    Go

This needs runc @ a9610f2c0 or greater. Docs can be found at godoc.org.

bucketbench - Go-based framework for running benchmarks against Docker, containerd, and runc engine layers

  •    Go

Bucketbench is a simple framework for running defined sequences of lifecycle container operations against three different container engines today: the full Docker engine, OCI's runc, and containerd. This project came about via some performance comparison work happening in the OpenWhisk serverless project. Developers in that project had a python script for doing similar comparisons, but agreed we should extend it to a more general framework which could be easily be extended for other lifecycle operation sequences, as the python script was hardcoded to a specific set of operations.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.