OCI-based implementation of Kubernetes Container Runtime Interface

Edit Package cri-o

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.

Refresh
Refresh
Source Files
Filename Size Changed
_constraints 0000000155 155 Bytes
_service 0000000634 634 Bytes
_servicedata 0000000432 432 Bytes
cri-o-1.24.1.tar.gz 0016263266 15.5 MB
cri-o-rpmlintrc 0000000687 687 Bytes
cri-o.changes 0000102741 100 KB
cri-o.spec 0000006806 6.65 KB
crio.conf 0000015004 14.7 KB
crio.service 0000000860 860 Bytes
kubelet.env 0000000167 167 Bytes
sysconfig.crio 0000000186 186 Bytes
vendor.tar.gz 0014455840 13.8 MB
Revision 65 (latest revision is 67)
Richard Brown's avatar Richard Brown (RBrownFactory) accepted request 990918 from Jeff Kowalczyk's avatar Jeff Kowalczyk (jfkw) (revision 65)
- Update to version 1.24.1:
  CVE-2022-1708
  * boo#1200285 CVE-2022-1708
  * bump to v1.24.1
  * conmonmgr: query help text to see if it supports log-global-size-max
  * add support for conmon log-global-size-max
  * oci: cap exec sync length
  * Fix review issues
  * Fix it case failed
  * Fix review issues
  * Add integration test for remove paused ctr
  * 1.When in paused state, stop contianer should unpause it 2.We should treat paused state as running, or kubelet will delete it and restart one
  * fix review issues
  * Try to force delete ctr when in paused state
  * vendor: bump crypto package (forwarded request 990917 from jfkw)
Comments 0
openSUSE Build Service is sponsored by