OCI-based implementation of Kubernetes Container Runtime Interface
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.
- Developed at devel:kubic
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/cri-o && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _constraints | 0000000155 155 Bytes | |
| _service | 0000000557 557 Bytes | |
| _servicedata | 0000000228 228 Bytes | |
| cri-o-1.18.3.tar.xz | 0006498096 6.2 MB | |
| cri-o-rpmlintrc | 0000000687 687 Bytes | |
| cri-o.changes | 0000051308 50.1 KB | |
| cri-o.spec | 0000006712 6.55 KB | |
| crio.conf | 0000014292 14 KB | |
| crio.service | 0000000860 860 Bytes | |
| kubelet.env | 0000000167 167 Bytes | |
| sysconfig.crio | 0000000186 186 Bytes |
Revision 53 (latest revision is 67)
Dominique Leuenberger (dimstar_suse)
accepted
request 822091
from
Thorsten Kukuk (kukuk)
(revision 53)
Comments 0