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:42:Factory-Candidates-Check/cri-o && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _constraints | 0000000155 155 Bytes | |
| _service | 0000000468 468 Bytes | |
| cri-o-1.16.1.tar.xz | 0006828948 6.51 MB | |
| cri-o-rpmlintrc | 0000000687 687 Bytes | |
| cri-o.changes | 0000040941 40 KB | |
| cri-o.spec | 0000007094 6.93 KB | |
| crio-shutdown.service | 0000000377 377 Bytes | |
| crio-wipe.service | 0000000245 245 Bytes | |
| crio.conf | 0000012882 12.6 KB | |
| crio.service | 0000000911 911 Bytes | |
| kubelet.env | 0000000167 167 Bytes | |
| prevent-local-loopback-teardown-rh1754154.patch | 0000000542 542 Bytes | |
| sysconfig.crio | 0000000186 186 Bytes |
Revision 43 (latest revision is 67)
Dominique Leuenberger (dimstar_suse)
accepted
request 765788
from
Sascha Grunert (sgrunert)
(revision 43)
Comments 0