No description

Find a file

Antonio Murdaca 66fdf3ae21 Merge pull request #13 from mrunalp/finish_status Report exit code and finish time on container status		2016-09-17 09:31:08 +02:00
cmd	make socket location configurable on cmd line	2016-09-15 15:57:39 -07:00
conmon	Integrate conmon into ocid	2016-09-15 16:40:44 -07:00
Godeps	updated vendor dependencies for networking	2016-09-09 14:41:03 -07:00
oci	Report exit code and finish time on container status	2016-09-16 16:33:33 -07:00
server	Report exit code and finish time on container status	2016-09-16 16:33:33 -07:00
testdata	Update the kubernetes api to latest	2016-09-09 14:41:03 -07:00
utils	Add utility to start a child process reaper	2016-09-09 14:41:03 -07:00
vendor	updated vendor dependencies for networking	2016-09-09 14:41:03 -07:00
.gitignore	Add a start Makefile to build ocid/ocic	2016-09-09 14:41:03 -07:00
.travis.yml	Setup travis CI	2016-09-09 14:41:03 -07:00
code-of-conduct.md	Add a code of conduct based on github.com/kubernetes/kubernetes	2016-09-09 15:26:59 -07:00
LICENSE	Initial commit	2016-09-09 12:56:31 -07:00
Makefile	Fix make for the command	2016-09-09 14:41:03 -07:00
OWNERS	Update README with links to libraries and add OWNERS	2016-09-09 15:39:36 -07:00
README.md	Update readme with a bit more info	2016-09-13 11:55:45 -04:00

README.md

ocid - OCI-based implementation of Kubernetes Container Runtime Interface

Status: pre-alpha

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:

Runtime: runc (or any OCI runtime-spec compliant runtime)
Images: Image management using https://github.com/containers/image
Storage: Storage and management of image layers using https://github.com/containers/storage
Networking: Networking support through use of CNI

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.