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:Backports:SLE-15-SP4:SLECandidates/cri-o && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _service | 0000000481 481 Bytes | |
| cri-o-1.9.5.tar.xz | 0002883000 2.75 MB | |
| cri-o-rpmlintrc | 0000000091 91 Bytes | |
| cri-o.changes | 0000003508 3.43 KB | |
| cri-o.spec | 0000005461 5.33 KB | |
| crio-shutdown.service | 0000000313 313 Bytes | |
| crio.conf | 0000005913 5.77 KB | |
| crio.service | 0000000685 685 Bytes | |
| crio.sysconfig | 0000000186 186 Bytes |
Revision 1 (latest revision is 67)
Dominique Leuenberger (dimstar_suse)
accepted
request 577286
from
Valentin Rothberg (vrothberg)
(revision 1)
Changes since the last SR: - Update cri-o to v1.9.5: * system container: add /var/tmp as RW * container_create: correctly set user * imageService: cache information about images * image: Add lock around image cache access - Cleanup version-update related changelogs to only keep log entries of changes that are visible and important to the user, and the project.
Comments 0