CRI-O v1.30.2

CRI-O v1.30.2

The release notes have been generated for the commit range v1.30.1…1fc2de0 on Fri, 28 Jun 2024 13:51:44 UTC.

Downloads

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

To verify the artifact signatures via cosign, run:

> export COSIGN_EXPERIMENTAL=1
> cosign verify-blob cri-o.amd64.1fc2de005c07d5e4c2e7b899c7221b699e1685d0.tar.gz \
    --certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/1fc2de005c07d5e4c2e7b899c7221b699e1685d0 \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-github-workflow-repository cri-o/cri-o \
    --certificate-github-workflow-ref refs/tags/1fc2de005c07d5e4c2e7b899c7221b699e1685d0 \
    --signature cri-o.amd64.1fc2de005c07d5e4c2e7b899c7221b699e1685d0.tar.gz.sig \
    --certificate cri-o.amd64.1fc2de005c07d5e4c2e7b899c7221b699e1685d0.tar.gz.cert

To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:

> tar xfz cri-o.amd64.1fc2de005c07d5e4c2e7b899c7221b699e1685d0.tar.gz
> bom validate -e cri-o.amd64.1fc2de005c07d5e4c2e7b899c7221b699e1685d0.tar.gz.spdx -d cri-o

Changelog since v1.30.1

Changes by Kind

Uncategorized

Fix CVE-2024-5154 where a malicious container image could make a symlink of /proc/mounts on the host, out of the container’s rootfs (#8231, @openshift-cherrypick-robot)
Fix memory leakage when sending a failing port-forward request (#8206, @openshift-cherrypick-robot)
Fix the bug that cri-o stops watching container exits after it gets an fsnotify error (#8209, @openshift-cherrypick-robot)
Reload config should remove pinned images when an empty list is provided (#8323, @sohankunkerkar)
Remove a container after it fails to start, to prevent copies of it from piling up until it succeeds. (#8297, @openshift-cherrypick-robot)

Dependencies

Added

Nothing has changed.

Changed

github.com/containers/image/v5: ea4fcca → f8d6234
github.com/google/go-containerregistry: v0.18.0 → v0.19.1

Removed

Nothing has changed.