vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

mention the need to add install tools

Browse source 
Signed-off-by: Mike Brown <brownwm@us.ibm.com>
This commit is contained in:
Mike Brown 2016-10-05 20:05:35 -05:00
parent a5da8a4d1e
commit 18df9788de
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -13,7 +13,7 @@ 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: 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 multiple image formats including the existing Docker image format
* Support for multiple means to download images including trust & image verification * Support for multiple means to download images including trust & image verification
* Container image management (managing image layers, overlay filesystems, etc) * Container image management (managing image layers, overlay filesystems, etc)
* Container process lifecycle management * Container process lifecycle management
@ -28,7 +28,7 @@ At a high level, we expect the scope of cri-o to be restricted to the following
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. 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: The plan is to use OCI projects and best of breed libraries for different aspects:
- Runtime: [runc](https://github.com/opencontainers/runc) (or any OCI runtime-spec implementation) and [oci runtime tools](https://github.com/opencontainers/runtime-tools) - Runtime: [runc](https://github.com/opencontainers/runc) (or any OCI runtime-spec implementation) and [oci runtime tools](https://github.com/opencontainers/runtime-tools)
- Images: Image management using [containers/image](https://github.com/containers/image) - Images: Image management using [containers/image](https://github.com/containers/image)
- Storage: Storage and management of image layers using [containers/storage](https://github.com/containers/storage) - Storage: Storage and management of image layers using [containers/storage](https://github.com/containers/storage)
- Networking: Networking support through use of [CNI](https://github.com/containernetworking/cni) - Networking: Networking support through use of [CNI](https://github.com/containernetworking/cni)
@ -50,6 +50,7 @@ $ GOPATH=/path/to/gopath
$ mkdir $GOPATH $ mkdir $GOPATH
$ go get -d github.com/kubernetes-incubator/cri-o $ go get -d github.com/kubernetes-incubator/cri-o
$ cd $GOPATH/src/github.com/kubernetes-incubator/cri-o $ cd $GOPATH/src/github.com/kubernetes-incubator/cri-o
$ make install.tools
$ make binaries $ make binaries
$ sudo make install $ sudo make install
``` ```
@ -118,7 +119,7 @@ $ ocic pod create --config test/testdata/sandbox_config.json
# ocic ctr list # ocic ctr list
``` ```
### Current Roadmap ### Current Roadmap
1. Basic pod/container lifecycle, basic image pull (already works) 1. Basic pod/container lifecycle, basic image pull (already works)
1. Support for tty handling and state management 1. Support for tty handling and state management