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.
- Links to devel:kubic / cri-o
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:ojkastl_buildservice:Branch_devel_kubic/cri-o && cd $_ - Create Badge
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| _constraints | 0000000155 155 Bytes | |
| _link | 0000000119 119 Bytes | |
| _service | 0000000772 772 Bytes | |
| _servicedata | 0000000432 432 Bytes | |
| cri-o-1.31.8.obscpio | 0095757326 91.3 MB | |
| cri-o.changes | 0000113247 111 KB | |
| cri-o.conf | 0000015004 14.7 KB | |
| cri-o.obsinfo | 0000000095 95 Bytes | |
| cri-o.spec | 0000006922 6.76 KB | |
| crio.service | 0000000860 860 Bytes | |
| kubelet.env | 0000000071 71 Bytes | |
| sysconfig.crio | 0000000186 186 Bytes | |
| vendor.tar.gz | 0016825163 16 MB |
Comments 0