vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
No description
276 commits 7 branches 27 tags 53 MiB
Go 67.7%
Shell 19.5%
C 8.5%
Dockerfile 1.6%
Makefile 1.5%
Other 1.2%
Find a file
Aleksa Sarai bac579a9e5
server: create pause rootfs manually without Docker 
This lessens the Docker requirement for creating sandboxes (with the
requirement only existing for the actual image pulling that is done when
adding a container to a pod). The interface was chosen to match the
--conmon interface, so that the location of the pause binary can be
chosen by a user.

Signed-off-by: Aleksa Sarai <asarai@suse.de>
2016-10-02 20:11:07 +11:00
.tool
cmd server: create pause rootfs manually without Docker 2016-10-02 20:11:07 +11:00
conmon Fixes Makefile so CFLAGS/LIBS are accepted as a make parameter 2016-09-30 22:15:30 -04:00
docs
hack
oci
pause *: add pause binary as a build target 2016-10-02 19:36:39 +11:00
server server: create pause rootfs manually without Docker 2016-10-02 20:11:07 +11:00
test server: create pause rootfs manually without Docker 2016-10-02 20:11:07 +11:00
utils server: create pause rootfs manually without Docker 2016-10-02 20:11:07 +11:00
vendor/src
.gitignore *: add pause binary as a build target 2016-10-02 19:36:39 +11:00
.travis.yml
code-of-conduct.md
Dockerfile
LICENSE
Makefile *: add pause binary as a build target 2016-10-02 19:36:39 +11:00
OWNERS
README.md

README.md

cri-o - OCI-based implementation of Kubernetes Container Runtime Interface

Build Status Go Report Card

Status: pre-alpha

What is the scope of this project?

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.

At a high level, we expect the scope of cri-o to be restricted to the following functionalities:

  • Support multiple image formats including the existing Docker image format
  • Support for multiple means to download images including trust & image verification
  • Container image management (managing image layers, overlay filesystems, etc)
  • Container process lifecycle management
  • Monitoring and logging required to satisfy the CRI
  • Resource isolation as required by the CRI

What is not in scope for this project?

  • Building, signing and pushing images to various image storages
  • A CLI utility for interacting with cri-o. Any CLIs built as part of this project are only meant for testing this project and there will be no guarantees on the backwards compatibility with it.

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.

The plan is to use OCI projects and best of breed libraries for different aspects:

It is currently in active development in the Kubernetes community through the design proposal. Questions and issues should be raised in the Kubernetes sig-node Slack channel.

Current Roadmap

  1. Basic pod/container lifecycle, basic image pull (already works)
  2. Support for tty handling and state management
  3. Basic integration with kubelet once client side changes are ready
  4. Support for log management, networking integration using CNI, pluggable image/storage management
  5. Support for exec/attach
  6. Target fully automated kubernetes testing without failures