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 home:adrianSuSE:PL/cri-o && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _constraints | 0000000155 155 Bytes | |
| _service | 0000000634 634 Bytes | |
| _servicedata | 0000000432 432 Bytes | |
| cri-o-1.24.3.tar.gz | 0016262949 15.5 MB | |
| cri-o-rpmlintrc | 0000000687 687 Bytes | |
| cri-o.changes | 0000104610 102 KB | |
| cri-o.spec | 0000006806 6.65 KB | |
| crio.conf | 0000015004 14.7 KB | |
| crio.service | 0000000860 860 Bytes | |
| kubelet.env | 0000000071 71 Bytes | |
| sysconfig.crio | 0000000186 186 Bytes | |
| vendor.tar.gz | 0014111743 13.5 MB |
Latest Revision
Dominique Leuenberger (dimstar_suse)
accepted
request 1108439
from
Priyanka Saggu (psaggu)
(revision 67)
(bsc#1214406) update `kubelet.env`: * to remove the following deprecated/obselete flags: ** `--container-runtime=remote --container-runtime-endpoint=unix:///var/run/crio/crio.sock --runtime-request-timeout=15m` * to add new flag -> `--fail-swap-on=false`
Comments 0