Bump runc from v1.1.13 to v1.3.0-rc.1 #159
Open
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.
v1.3.0-rc.1
Tag: v1.3.0-rc.1
Published at: 2025-03-04T12:14:28Z
URL: Release v1.3.0-rc.1
Description:
This is the first release candidate of the runc 1.3.0 release. It
contains a couple of new features, but is mostly made up of some minor
(but notable) API changes to libcontainer as well as a series of bug
fixes.
This is the first release series that will follow our new release
policy, meaning that user should expect runc 1.3.0 to be released at the
end of April 2025, at which point the support policy for the runc 1.2.z
branch will change. Please see the new RELEASES.md document for more
information.
Users are strongly encouraged to test our release candidates over the
next two months so we can fix issues before the general release.
libcontainer API
configs.CommandHook
struct has changed, Command is now a pointer.Also,
configs.NewCommandHook
now accepts a*Command
. (# 4325)Process
struct hasUser
string field replaced with numericUID
andGID
fields, andAdditionalGroups
changed its type from[]string
to[]int
. Essentially, resolution of user and groupShow more
names to IDs is no longer performed by libcontainer, so if a libcontainer
user previously relied on this feature, now they have to convert names to
IDs before calling libcontainer; it is recommended to use Go package
github.com/moby/sys/user for that. (# 3999)
Fixed
runc exec -p
no longer ignores specifiedioPriority
andscheduler
settings. Similarly, libcontainer's
Container.Start
andContainer.Run
methods no longer ignore
Process.IOPriority
andProcess.Scheduler
settings. (# 4585)
F_SEAL_FUTURE_WRITE
when sealing the runc binary, as itturns out this had some unfortunate bugs in older kernel versions and was
never necessary in the first place. (# 4641, # 4640)
matches the behaviour of
nsenter(8)
. This is mainly useful for users thatcreate a container with a runc-managed user namespace but want the container
to join some externally-managed namespace as well. (# 4492)
runc
now properly handles joining time namespaces (such as withrunc exec
).Previously we would attempt to set the time offsets when joining, which
would fail. (# 4635, # 4636)
EINTR
retries correctly for socket-related directgolang.org/x/sys/unix
system calls. (# 4637)close_range(2)
errors more gracefully. (# 4596)O_CLOEXEC
withCloseExecFrom
failed (# 4599).gracefully. (# 4597)
Changed
around our release schedules and better define our support policy for old
release branches. See
RELEASES.md
for more details. (# 4557)strings.Cut
where appropriate.(# 4470)
Added
runc exec
. (# 4327)runc_nocriu
. (# 4546)pidfd-socket
.(# 4045)
skip-in-flight
andlink-remap
options for CRIU. (# 4627)noprefix
. (# 4513)Static Linking Notices
The
runc
binary distributed with this release are statically linked withthe following GNU LGPL-2.1 licensed libraries, with
runc
actingas a "work that uses the Library":
The versions of these libraries were not modified from their upstream versions,
but in order to comply with the LGPL-2.1 (§6(a)), 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 the LGPL-2.1.
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 for making this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
Commits
a00ce11
VERSION: release v1.3.0-rc.10ebf331
Merge pull request # 4327 from kolyshkin/exec-cpu-aff10ca66b
runc exec: implement CPU affinity701516b
merge # 4654 into opencontainers/runc:maind92dd22
performance improvement: setup signal notify in a new go routine