No description

Find a file

Antonio Murdaca 166778315c Merge pull request #36 from mrunalp/status_exit Convert status to exit code		2016-09-19 21:28:21 +02:00
.tool	restructure and make lint	2016-09-19 19:56:13 +02:00
cmd	restructure and make lint	2016-09-19 19:56:13 +02:00
conmon	conmon: use runtime path from ocid	2016-09-17 11:37:45 +02:00
oci	Convert status to exit code	2016-09-19 12:25:13 -07:00
server	restore server rewrite	2016-09-19 19:57:50 +02:00
testdata	testdata: update container_config to be usable	2016-09-19 19:51:03 +02:00
utils	Convert status to exit code	2016-09-19 12:25:13 -07:00
vendor	*: switch from godep to glide	2016-09-17 17:06:30 +02:00
.gitignore	.gitignore: add conmon objs	2016-09-17 11:56:51 +02:00
.travis.yml	makefile stuff	2016-09-19 19:51:03 +02:00
code-of-conduct.md	Add a code of conduct based on github.com/kubernetes/kubernetes	2016-09-09 15:26:59 -07:00
glide.lock	*: switch from godep to glide	2016-09-17 17:06:30 +02:00
glide.yaml	*: switch from godep to glide	2016-09-17 17:06:30 +02:00
HACKING.md	*: add HACKING.md	2016-09-17 18:53:36 +02:00
LICENSE	Initial commit	2016-09-09 12:56:31 -07:00
Makefile	Fixes to the Makefile	2016-09-19 11:36:57 -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.