Name: cri-o
Owner: Datica
Description: Open Container Initiative-based implementation of Kubernetes Container Runtime Interface
Created: 2018-03-13 17:31:03.0
Updated: 2018-03-13 17:31:06.0
Pushed: 2018-03-13 14:48:54.0
Size: 41628
Language: Go
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
| Version - Branch | Kubernetes branch/version | Maintenance status | |—————————-|——————————-|——————–| | CRI-O 1.0.x - release-1.0 | Kubernetes 1.7 branch, v1.7.x | = | | CRI-O 1.8.x - release-1.8 | Kubernetes 1.8 branch, v1.8.x | = | | CRI-O 1.9.x - release-1.9 | Kubernetes 1.9 branch, v1.9.x | = | | CRI-O HEAD - master | Kubernetes master branch | ? |
Key:
?
Changes in main Kubernetes repo about CRI are actively implemented in CRI-O=
Maintenance is manual, only bugs will be patched.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:
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.
| Command | Description | Demo| | —————————————————- | ————————————————————————–|—–| | crio(8) | OCI Kubernetes Container Runtime daemon ||
Note that kpod and its container management and debugging commands have moved to a separate repository, located here.
| File | Description | | —————————————————- | —————————————————————————————————- | | crio.conf(5) | CRI-O Configuation file |
CRI-O configures OCI Hooks to run when launching a container
Useful information for ops and dev transfer as it relates to infrastructure that utilizes CRI-O
For async communication and long running discussions please use issues and pull requests on the github repo. This will be the best place to discuss design and implementation.
For sync communication we have an IRC channel #CRI-O, on chat.freenode.net, that everyone is welcome to join and chat about development.
Latest version of runc
is expected to be installed on the system. It is picked up as the default runtime by CRI-O.
Required
Fedora, CentOS, RHEL, and related distributions:
install -y \
rfs-progs-devel \
vice-mapper-devel \
t \
ib2-devel \
ibc-devel \
ibc-static \
\
lang-github-cpuguy83-go-md2man \
gme-devel \
bassuan-devel \
bgpg-error-devel \
bseccomp-devel \
bselinux-devel \
tree-devel \
gconfig \
nc \
opeo-containers
Debian, Ubuntu, and related distributions:
get install -y \
rfs-tools \
t \
lang-go \
bassuan-dev \
bdevmapper-dev \
bglib2.0-dev \
bc6-dev \
bgpgme11-dev \
bgpg-error-dev \
bseccomp-dev \
bselinux1-dev \
g-config \
-md2man \
nc \
opeo-containers
Debian, Ubuntu, and related distributions will also need a copy of the development libraries for ostree
, either in the form of the libostree-dev
package from the flatpak PPA, or built from source (more on that here).
If using an older release or a long-term support release, be careful to double-check that the version of runc
is new enough (running runc --version
should produce spec: 1.0.0
), or else build your own.
NOTE
Be careful to double-check that the version of golang is new enough, version 1.8.x or higher is required. If needed, golang kits are avaliable at https://golang.org/dl/
Optional
Fedora, CentOS, RHEL, and related distributions:
(no optional packages)
Debian, Ubuntu, and related distributions:
get install -y \
bapparmor-dev
Clone the source code using:
clone https://github.com/kubernetes-incubator/cri-o # or your fork
ri-o
install.tools
make install
Otherwise, if you do not want to build CRI-O
with seccomp support you can add BUILDTAGS=""
when running make.
install.tools
BUILDTAGS=""
make install
CRI-O
supports optional build tags for compiling support of various features.
To add build tags to the make option the BUILDTAGS
variable must be set.
BUILDTAGS='seccomp apparmor'
| Build Tag | Feature | Dependency | |———–|————————————|————-| | seccomp | syscall filtering | libseccomp | | selinux | selinux process and mount labeling | libselinux | | apparmor | apparmor profile support | libapparmor |
Follow this tutorial to get started with CRI-O.
A proper description of setting up CNI networking is given in the
contrib/cni
README. But the gist is that you need to
have some basic network configurations enabled and CNI plugins installed on
your system.
You can run a local version of kubernetes with CRI-O using local-up-cluster.sh
:
crio
)UP_DRIVER=systemd \
AINER_RUNTIME=remote \
AINER_RUNTIME_ENDPOINT='unix:///var/run/crio/crio.sock --runtime-request-timeout=15m' \
ck/local-up-cluster.sh
To run a full cluster, see the instructions.