Merged
Conversation
121a86b to
e5aa25c
Compare
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
AkihiroSuda
approved these changes
Nov 15, 2024
lifubang
approved these changes
Nov 16, 2024
cyphar
approved these changes
Nov 16, 2024
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.
Let's release v1.2.2 this week.
Currently a draft pending #4530 and #4531 merge.[1.2.2] - 2024-11-15
Fixed
runc deleteon a rootless container with nodedicated cgroup on a system with read-only
/sys/fs/cgroupmount.This is a regression in runc 1.2.0, causing a failure when using
rootless buildkit. (runc v1.2.1 appears to break Rootless BuildKit (
cgroup: open /sys/fs/cgroup/snschvixiy3s74w74fjantrdg: no such file or directory) #4518, [1.2] runc delete: fix for rootless cgroup + ro cgroupfs #4531)filesystems no longer results in harmless but annoying messages
("overlayfs: "xino" feature enabled using 3 upper inode bits")
appearing in the kernel log. (Journald full of "overlayfs: "xino" feature enabled using 3 up" #4508, [1.2] dmz: overlay: minor fixups #4530)
Changed