containerd - An open and reliable container runtime

  •        634

containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.. containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users.



Related Projects

Moby Project - An open framework to assemble specialized container systems

Moby is an open-source project created by Docker to advance the software containerization movement. It provides a “Lego set” of dozens of components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts to experiment and exchange ideas.

cri-containerd - Containerd-based implementation of Kubernetes Container Runtime Interface

cri-containerd is a containerd based implementation of Kubernetes container runtime interface (CRI).With it, you could run Kubernetes using containerd as the container runtime.

cri-o - Open Container Initiative-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.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.

containerd - Standalone Container Daemon

Containerd is a daemon to control runC, built for performance and density. Containerd leverages runC advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.

rktlet - The rkt implementation of a Kubernetes Container Runtime

rktlet is a Kubernetes Container Runtime Interface implementation using rkt as the main container runtime. rkt is an ongoing CNCF effort to develop a pod-native container runtime.The goal of this project is to eventually supplant the rkt package in the main Kubernetes repository.

containership - A simple container management platform

Absolutely! First install Vagrant, then install our cloud plugin by running cs plugin add cloud. Once installed, run cs cloud create-cluster vagrant --leaders 1 --followers 2 to bring up a local cluster to play around with.Containership will run on any linux host with node & docker (see our installation guide for more details). If you're using open source Containership, use our official setting up your first cluster guide. If you'd like to manage your Containership cluster using our Containership Cloud management product, sign up for an account and follow the official getting started guide.

ruby-docker - Ruby runtime for Google Cloud Platform

The provided Rakefile builds the three images locally and runs the unit tests in the test directory. It requires Ruby 2.3 and Docker 17.06 or later.Actual builds can be done using the build scripts in this directory. The script uses Google Cloud Container Builder to build the images and upload them to Google Container Registry. The script creates a Ruby runtime builder configuration and uploads it to Google Cloud Storage where it can be used.

ecs-machine-learning - An EC2 Container Service Architecture which provides the infrastructure for Deep Learning

AWS Solutions Architects are seeing an emerging type of application for ECS: GPU-accelerated workloads, or, more specifically, workloads that need to leverage large amounts of GPUs across many nodes. For example, at, the Amazon Personalization Team runs significant Machine Learning workloads that leverage many GPUs on Amazon ECS. Let’s take a look at how ECS enables GPU workloads.In order to run GPU-enabled work on an ECS cluster, a Docker image configured with Nvidia CUDA drivers, which allow the container to communicate with the GPU hardware, is built and stored in EC2 Container Registry. An ECS Task Definition is used to point to the container image in ECR and specify configuration for the container at runtime, like how much CPU and memory each container should use, the command to run inside the container, if a data volume should be mounted in the container, where the source dataset lives in S3, and so on.

jetty-runtime - Google Cloud Platform Jetty Docker image

This repository contains the source for the Google-maintained Jetty docker image. This image can be used as the base image for running Java web applications on Google App Engine Flexible Environment and Google Container Engine. It provides the Jetty Servlet container on top of the OpenJDK image.This image is mirrored at both and

docker-fluentd - Docker container to collect other docker container logs with Fluentd

By default, the container logs are stored in /var/log/docker/yyyyMMdd.log inside this logging container. The data is buffered, so you may also see buffer files like /var/log/docker/20141114.b507c71e6fe540eab.log where "b507c71e6fe540eab" is a hash identifier. You can mount that container volume back to host. Also, by modifying fluent.conf and rebuilding the Docker image, you can stream up your logs to Elasticsearch, Amazon S3, MongoDB, Treasure Data, etc.docker-fluentd uses Fluentd inside to tail log files that are mounted on /var/lib/docker/containers/<CONTAINER_ID>/<CONTAINER_ID>-json.log. It uses the tail input plugin to tail JSON-formatted log files that each Docker container emits.

docker-dev - experimentation with docker as a dev environment

``` $ curl -O $ chmod +x ./docker-dev```Now that you have the `docker-dev` script, you can start it up``` $ ./docker-dev```Or you can set `HOME_REPO_URL` in your environment to make ./docker-dev easier to start``` $ export HOME_REPO_URL= $ ./docker-dev```Config-------`docker-dev` follows the [12 factorconfig](http://12f

Portainer - Simple management UI for Docker

Portainer is a lightweight management UI which allows you to easily manage your different Docker environments (Docker hosts or Swarm clusters). Portainer is meant to be as simple to deploy as it is to use. It consists of a single container that can run on any Docker engine (can be deployed as Linux container or a Windows native container). It allows you to manage your Docker containers, images, volumes, networks and more ! It is compatible with the standalone Docker engine and with Docker Swarm mode.

source-to-image - A tool for building/building artifacts from source and injecting into docker images

Source-to-Image (S2I) is a toolkit and workflow for building reproducible Docker images from source code. S2I produces ready-to-run images by injecting source code into a Docker container and letting the container prepare that source code for execution. By creating self-assembling builder images, you can version and control your build environments exactly like you use Docker images to version your runtime environments.For a deep dive on S2I you can view this presentation.

runlike - Given an existing docker container, prints the command line necessary to run a copy of it.

This is what runlike does. You give it a docker container, it outputs the command line necessary to run another one just like it, along with all those pesky options (ports, links, volumes, ...). It's a real time saver for those that normally deploy their docker containers via some CM tool like Ansible/Chef and then find themselves needing to manually re-run some container.This prints out what you need to run to get a similar container. You can do $(runlike container-name) to simply execute its output in one step.

netshoot - a Docker network troubleshooting swiss-army container

Purpose: Docker network tshooting can be difficult for network engineers. With proper understanding of how Docker networking works and the right set of tools, you can troubleshoot and resolve these networking issues. The netshoot container has a set of powerful networking tshooting tools that can be used to troubleshoot Docker networking issues.Network Namespaces: Before starting to use this tool, it's important to go over one key topic: Network Namespaces. Network namespaces provide isolation of the system resources associated with networking. Docker uses network and other type of namespaces (pid,mount,user..etc) to create an isolated environment for each container. Everything from interfaces, routes, and IPs is completely isolated within the network namespace of the container.

Flocker - Container data volume manager for your Dockerized application

Flocker is an open-source Container Data Volume Manager for your Dockerized applications. By providing tools for data migrations, Flocker gives ops teams the tools they need to run containerized stateful services like databases in production. Unlike a Docker data volume which is tied to a single server, a Flocker data volume, called a dataset, is portable and can be used with any container, no matter where that container is running.

PiCluster - Manage Docker Containers

PiCluster is a simple way to manage Docker containers on multiple hosts. Docker Swarm not that good and Kubernetes was too difficult to install currently on ARM. PiCluster will only build and run images from Dockerfile's on the host specified in the config file. This software will work on regular x86 hardware also and is not tied to ARM.

zabbix-docker-monitoring - :whale: Docker/Kubernetes/Mesos/Marathon/Chronos/LXC/LXD/Swarm container monitoring - Docker image, Zabbix template and C module

If you like or use this project, please provide feedback to author - Star it ★ and write what's missing for you.Monitoring of Docker container by using Zabbix. Available CPU, mem, blkio, net container metrics and some containers config details, e.g. IP, name, ... Zabbix Docker module has native support for Docker containers (Systemd included) and should also support a few other container types (e.g. LXC) out of the box. Please feel free to test and provide feedback/open issue. The module is focused on performance, see section Module vs. UserParameter script.

tlspretense-service - A Docker container that exposes tlspretense on a port.

A Docker container that exposes tlspretense as a service. This launches tlspretense in a Docker container, exposing its tests without having to use the container as a NAT device.This project is very similar to tlspretense-docker, except it allows clients to connect to the container directly (as if it were the target service) instead of updating their routing rules to go through it. This is very useful in environments in which invasive networking changes are not practical, but in which directing clients to a different service and port is easy.