chore(deps): update dependency opencontainers/runc to v1.5.2 - #699
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.1→v1.5.2Release Notes
opencontainers/runc (opencontainers/runc)
v1.5.2: runc v1.5.2 -- "Всё сбудется, стоит только расхотеть!"Compare Source
This is the second patch release in the 1.5.z release series of runc,
which primarily includes a workaround for a Linux kernel bug causing
random runc crashes when using cgroup v2, and other fixes.
Fixed
runc exec -pwith a process.json lackingenvnow setsHOMEagain(a regression in runc 1.3.0). (#5265, #5266, #5459)
which caused the kernel to write past the end of the structure
provided by userspace (runc). This resulted in memory corruption inside runc
(manifesting as random crashes) when configuring device rules on cgroup v2
systems. (#5403, #5428)
runc exec --cgroup(and the equivalent libcontainerProcess.SubCgroupPathsAPI) no longer accepts a sub-cgroup path that escapes the container's cgroup
into a sibling cgroup sharing the same name prefix. Note that using
--cgrouprequires the same privileges as runningrunc execitself, sothis is a correctness rather than a security fix. (#5403, #5457)
O_CLOEXECwhen opening the cgroup v2 directory to set updevice rules. (#5403, #5428)
fixed. (#5403, #5428)
rootfsPropagationis set torslave, the rootfs parent mount is nolonger made private before pivoting into the rootfs, so unmount/remount
events on host mountpoints under the rootfs are now propagated to the
running container. (#5192, #5200, #5458)
when that namespace has a full identity ID mapping (
0 0 4294967295), asused by systemd >= 260 units with
PrivateUsers=full. Previously this maderunc skip its user namespace code paths, so starting a container in such a
unit failed with
bpf_prog_query(BPF_CGROUP_DEVICE) failed: operation not permitted.(#5396, #5411, #5451, moby/sys#239)
runc initpanic (SIGABRT) on the error path, caused by SELinuxlabels being reset after the cached libpathrs procfs handle was already
closed. This is fixed both by not resetting the labels on the init error
path, and by updating to libpathrs v0.2.6, which now handles a closed
procfs handle gracefully. (#5438, #5439, #5442, #5448, #5449, #5467,
#5469)
from the one it was compiled against (e.g. built with libseccomp >= 2.6.0 and
run with an older one), by updating to libseccomp-golang v0.12.0. This also
supersedes the
SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECVworkaround added inrunc 1.5.1. (#5436, #5461)
with optimizations enabled (the default
-g -O2CFLAGS); previously it wasbuilt unoptimized. (#5464, #5465)
Changed
high-level cilium/ebpf API to manage cgroup v2 device rules. As a result,
the runc binary shrunk by about 1 MiB (7.5%) on amd64. This also means runc
no longer calls the cilium/ebpf code affected by GO-2026-6238. (#5403, #5428)
Static Linking Notices
The
runcbinaries distributed with this release are statically linked withthe following GNU LGPL-2.1 licensed libraries, with
runcactingas a "work that uses the Library":
Similarly, the
runcbinaries distributed with this release are alsostatically linked with the following MPLv2 licensed libraries,
with
runcacting as a "Larger Work":The versions of these libraries were not modified from their upstream versions,
but in order to comply with their corresponding licenses, we have attached the
complete source code for those libraries which (when combined with the attached
runc source code) may be used to exercise your rights under their respective
licenses.
However, we strongly suggest that you make use of your distribution's packages
or download them from the authoritative upstream sources, especially since
these libraries are related to the security of your containers.
Thanks to the following contributors who made this release possible:
Signed-off-by: Kir Kolyshkin kolyshkin@gmail.com
Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.