CRI-O v1.24.2

The release notes have been generated for the commit range v1.24.1…56d37e7 on Thu, 06 Oct 2022 19:53:35 UTC.

Downloads

Download one of our static release bundles via our Google Cloud Bucket:

Fix a bug by re-adding the inheritable capabilities when adding capabilities. While it fixes an atypical unix environment, it causes a regression with non-root users using capabilities. (#6240, @haircommander)
Fix a bug where ExecSync requests (exec probes) could use an arbitrary amount of memory and disk. Output from ExecSync requests is now limited to 16MB (the amount that exec output was limited to in the dockershim). Disk limiting requires conmon 2.1.2 to work. See https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j and CVE-2022-1708 for more information. (#5935, @haircommander)
Fix a bug where child processes of containers in the host’s PID namespace appear to leak after the child exits (#5943, @haircommander)

Fix a bug where a container is stuck in INIT because CRI-O believes it to be paused, and never updates the state (#6129, @openshift-cherrypick-robot)
Fix a bug where exit files were never cleaned up from /run/crio/exits (#6149, @openshift-cherrypick-robot)
Fix a panic caused by using the improper Result structure version when setting up CNI plugins (#5960, @haircommander)
Fix a rare deadlock while communicating to systemd (RHBZ 2082344) (#5954, @openshift-cherrypick-robot)
Use default umask 0o022 if CRI-O runs under a different umask value. (#6054, @openshift-cherrypick-robot)

Nothing has changed.

Nothing has changed.