代码拉取完成，页面将自动刷新
runc v1.2.0-rc.1 -- "There's a frood who really knows where his towel is."
This is the first release candidate for the 1.2.0 branch of runc. It includes
all patches and bugfixes included in runc 1.1 patch releases (up to and
including 1.1.12). A fair few new features have been added, and some changes
have been made which may affect users. Please help us thoroughly test this
release before we release 1.2.0.
runc now requires a minimum of Go 1.20 to compile.
NOTE: runc currently will not work properly when compiled with Go 1.22 or
newer. This is due to some unfortunate glibc behaviour that Go 1.22
exacerbates in a way that results in containers not being able to start on
some systems. See this issue for more information.
Breaking:
Several aspects of how mount options work has been adjusted in a way that
could theoretically break users that have very strange mount option strings.
This was necessary to fix glaring issues in how mount options were being
treated. The key changes are:
Mount options on bind-mounts that clear a mount flag are now always
applied. Previously, if a user requested a bind-mount with only clearing
options (such as rw,exec,dev) the options would be ignored and the
original bind-mount options would be set. Unfortunately this also means
that container configurations which specified only clearing mount options
will now actually get what they asked for, which could break existing
containers (though it seems unlikely that a user who requested a specific
mount option would consider it "broken" to get the mount options they
asked foruser who requested a specific mount option would consider it
"broken" to get the mount options they asked for). This also allows us to
silently add locked mount flags the user did not explicitly request to be
cleared in rootless mode, allowing for easier use of bind-mounts for
rootless containers. (#3967)
Container configurations using bind-mounts with superblock mount flags
(i.e. filesystem-specific mount flags, referred to as "data" in
mount(2), as opposed to VFS generic mount flags like MS_NODEV) will
now return an error. This is because superblock mount flags will also
affect the host mount (as the superblock is shared when bind-mounting),
which is obviously not acceptable. Previously, these flags were silently
ignored so this change simply tells users that runc cannot fulfil their
request rather than just ignoring it. (#3990)
If any of these changes cause problems in real-world workloads, please open
an issue so we
can adjust the behaviour to avoid compatibility issues.
Added:
docs/spec-conformance.mdMOUNT_ATTR_IDMAP kernel support (Linuxmount_setattr(2) for a list ofrunc-dmz is a minimal binary (~8K) which acts as an additional execverunc-dmz (namely related to capabilities and SELinux). AsruncRUNC_DMZ=true (setting this environmentconfig.json will have no effect). This feature can berunc_nodmz build tag. (#3983, #3987)contrib/memfd-bind is a helper daemon which will bind-mount a memfd copy/usr/bin/runc on top of /usr/bin/runc. This entirely eliminatescgroup.kill if available to kill all processes in arunc kill). (#3135, #3825)runc exec. (#3661)SCHED_IDLE for runc cgroupfs. (#3377)--manage-cgroups-mode=ignore. (#3546)SPEC_ALLOW byMAJOR:* syntax. (#3843)runc binary size by ~11% by updatinggithub.com/checkpoint-restore/go-criu. (#3652)--pidfd-socket to runc run and runc exec to allow for managementDeprecated:
runc option --criu is now ignored (with a warning), and the option willcriu binary should rely on the standard way of looking up binaries in$PATH. (#3316)runc kill option -a is now deprecated. Previously, it had to be specifiedgithub.com/opencontainers/runc/libcontainer/user is now deprecated, pleasegithub.com/moby/sys/user instead. It will be removed in a futureChanged:
runc exec and runc run. (#3306)runc features is no longer experimental. (#3861)container.Signal. (#3825)anon and file from memory.stat for cgroupv2 root usage,memory.current for cgroupv2.swapOnlyUsage in MemoryStats. This field reports swap-only usage.Usage and Failcnt are set by subtracting memory usageUsage, Limit, and MaxUsagecontainer.Signal. (#3825)container.Signal no longer takes an all argument. Whetherrunc run/runc exec: ignore SIGURG. (#3368)runc --root non-existent-dir list now reports an error for non-existentFixed:
runc init no longer re-execs-ENOSYS stub now correctly handles multiplexed syscalls on-EPERM despite the existence of the -ENOSYS stubMS_POSIXACL. (#3739)READY notification. (#3291, #3293)-ENOSYS seccomp stub is now always generated for the nativerunc is running on. This is needed to work around somenull. This-ENOSYS stub for the nativeRemoved:
ro bind-mount of/proc/self/exe has been removed. runc now creates a binary copy in allmemfd-bind and runc-dmz as well ascontrib/cmd/memfd-bind/README.md for more information about how thisEnterPid (a function with no users). (#3797){Pre,Post}MountCmds which were never used and areThanks to the following contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.12 -- "Now you're thinking with Portals™!"
This is the twelfth patch release in the 1.1.z release branch of runc.
It fixes a high-severity container breakout vulnerability involving
leaked file descriptors, and users are strongly encouraged to update as
soon as possible.
Fix CVE-2024-21626, a container breakout attack that took advantage of
a file descriptor that was leaked internally within runc (but never
leaked to the container process).
In addition to fixing the leak, several strict hardening measures were
added to ensure that future internal leaks could not be used to break
out in this manner again.
Based on our research, while no other container runtime had a similar
leak, none had any of the hardening steps we've introduced (and some
runtimes would not check for any file descriptors that a calling
process may have leaked to them, allowing for container breakouts due
to basic user error).
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.11 -- "Happy New Year!"
This is the eleventh patch release in the 1.1.z release branch of runc.
It primarily fixes a few issues with runc's handling of containers that
are configured to join existing user namespaces, as well as improvements
to cgroupv2 support.
swapOnlyUsage in MemoryStats. This field reports swap-only usage.Usage and Failcnt are set by subtracting memory usageUsage, Limit, and MaxUsageThanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.10 -- "Śruba, przykręcona we śnie, nie zmieni sytuacji, jaka panuje na jawie."
This is the tenth (and most likely final) patch release in the 1.1.z
release branch of runc. It mainly fixes a few issues in cgroups, and a
umask-related issue in tmpcopyup.
hugetlb.<pagesize>.rsvd limiting and accounting.kmem.limit_in_bytesconfig.json, which is outside of our threat model. (#4103)Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.9 -- "There is a crack in everything. That's how the light gets in."
This is the ninth patch release of the 1.1.z release branch of runc.
It fixes a regression introduced in 1.1.8, a bugfix in intelrdt, and
a libcontainer fix to cgroup v2 statistics reporting.
anon and file from memory.stat for cgroupv2 root usage,memory.current for cgroupv2.Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.8 -- "海纳百川 有容乃大"
This is the eighth patch release of the 1.1.z release branch of runc.
The most notable change is the addition of RISC-V support, along with a
few bug fixes.
.codespellrc: update for 2.2.5. (#3909)Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.7 -- "Ночевала тучка золотая на груди утеса-великана."
This is the seventh patch release in the 1.1.z release of runc, and is
the last planned release of the 1.1.z series. It contains a fix for
cgroup device rules with systemd when handling device rules for devices
that don't exist (though for devices whose drivers don't correctly
register themselves in the kernel -- such as the NVIDIA devices -- the
full fix only works with systemd v240+).
DeviceAllow rules if the device does not exist (a regression introducedrunc.keyring, which contains the keysThanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.6 -- "In this world nothing is certain but death and taxes."
This is the sixth path release in the 1.1.z series of runc, which fixes
a series of cgroup-related issues.
Note that this release can no longer be built from sources using Go
1.16. Using a latest maintained Go 1.20.x or Go 1.19.x release is
recommended. Go 1.17 can still be used.
UnitExist errorresources.cpu.cpus to systemd unit property (AllowedCPUs) in case of moreCAP_DAC_OVERRIDE capability into account. This ismisc controller. (#3823)Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.5 -- "囚われた屈辱は 反撃の嚆矢だ"
This is the fifth patch release in the 1.1.z series of runc, which fixes
three CVEs found in runc.
CVE-2023-25809 is a vulnerability involving rootless containers where
(under specific configurations), the container would have write access
to the /sys/fs/cgroup/user.slice/... cgroup hierarchy. No other
hierarchies on the host were affected. This vulnerability was
discovered by Akihiro Suda.
https://github.com/opencontainers/runc/security/advisories/GHSA-m8cg-xc2p-r3fc
CVE-2023-27561 was a regression which effectively re-introduced
CVE-2019-19921. This bug was present from v1.0.0-rc95 to v1.1.4. This
regression was discovered by @Beuc.
https://github.com/advisories/GHSA-vpvm-3wq2-2wvm
CVE-2023-28642 is a variant of the same bug and was fixed by the same
patch. This variant of the above vulnerability was reported by Lei
Wang.
https://github.com/opencontainers/runc/security/advisories/GHSA-g2j6-57v7-gm8c
In addition, the following other fixes are included in this release:
/dev/null when inside a container. (#3620)/dev/null caused by fd redirectionwrite_log(). (#3721)Thanks to all of the contributors who made this release possible:
[Due to the security-critical nature of this release, it was released
without a direct vote but was agreed to by the required number of
maintainers.]
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.4 -- "If you look for perfection, you'll never be content."
This is the fourth patch release in the 1.1.z series of runc, primarily
fixing a regression introduced in 1.1.3 related to device rules. It also
fixes a few other bugs.
kill() in libcontainer/nsenter to sane_kill(). (#3536)runc run on noexec fs. (#3541)systemctl daemon-reload. Due to a regressionDeviceAllow=char-pts rwm rule was no longer added andopen /dev/pts/0: operation not permitted: unknown when systemd was reloaded. (#3554)Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.3 -- "In the beginning there was nothing, which exploded."
This is the third release of the 1.1.z series of runc, and contains
various minor improvements and bugfixes.
-ENOSYS stub now correctly handles multiplexed syscalls on-EPERM despite the existence of the -ENOSYS stubThanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.2 -- "I should think I’m going to be a perpetual student."
This is the second patch release of the runc 1.1 release branch. It
fixes CVE-2022-29162, a minor security issue (which appears to not be
exploitable) related to process capabilities.
This is a similar bug to the ones found and fixed in Docker and
containerd recently (CVE-2022-24769).
runc spec no longer sets any inheritable capabilities in the createdconfig.json) file.Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.1 -- "Violence is the last refuge of the incompetent."
This is the first stable release in the 1.1 branch, fixing a few issues
with runc 1.1.0.
Fixed:
Thanks to all of the contributors who made this release possible:
Signed-off-by: Kir Kolyshkin kolyshkin@gmail.com
v1.1.0 -- "A plan depends as much upon execution as it does upon concept."
This release only contains very minor changes from v1.1.0-rc.1 and is
the first release of the 1.1.y release series of runc.
Changed:
Thanks to the following people who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.1.0~rc1 -- "He who controls the spice controls the universe."
This release is the first release candidate for the next minor release
following runc 1.0. It contains all of the bugfixes included in runc 1.0
patch releases (up to and including 1.0.3).
A fair few new features have been added, and several features have been
deprecated (with plans for removal in runc 1.2). At the moment we only
plan to do a single release candidate for runc 1.1, and once 1.1.0 is
released we will not continue updating the 1.0.z runc branch.
Deprecated:
Removed:
cgroup.GetHugePageSizes has been removed entirely, and been replaced withcgroup.HugePageSizes which is more efficient. (#3234)intelrdt.GetIntelRdtPath has been removed. Users who were using thisintelrdt.RootAdded:
--keep option to skip removal exited containers artefacts.SCMP_ACT_KILL_PROCESS and SCMP_ACT_KILL_THREADSCMP_ACT_KILL). (#3204)SCMP_ACT_NOTIFY (seccomp actions). This allows--lsm-mount-context) to setsysctl(8)'smount_setattr(2). Thesemount(8) options -- just prepend rrro). (#3272)runc features subcommand to allow runc users to detect what featuresChanged:
/proc/$pid/stat parsing. (#2696)/sys/fs/cgroup is configured as a read-write mount, change/sys/kernel/cgroup/delegate) to allow for proper deferral to the containerLibcontainer API:
Fixed:
runc delete -f now succeeds (rather than timing out) on a paused--ignore-paused. (#3132, #3223)Thanks to the following people who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.0.3 -- "If you were waiting for the opportune moment, that was it."
This is the third stable release in the 1.0 branch, fixing a handful of medium
priority issues related to mounts and cgroups, as well as a potential security
vulnerability.
This release is expected to be the last point release in the 1.0 branch, as we
are planning to release runc 1.1 in the near future.
Security:
A potential vulnerability was discovered in runc (related to an internal
usage of netlink), however upon further investigation we discovered that
while this bug was exploitable on the master branch of runc, no released
version of runc could be exploited using this bug. The exploit required
being able to create a netlink attribute with a length that would overflow a
uint16 but this was not possible in any released version of runc. For more
information see GHSA-v95c-p5hm-xq8f and CVE-2021-43784.
Due to an abundance of caution we decided to do an emergency release with
this fix, but to reiterate we do not believe this vulnerability was
possible to exploit. Thanks to Felix Wilhelm from Google Project Zero for
discovering and reporting this vulnerability so quickly.
Bugfixes:
Enhancements:
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.0.2 -- "Given the right lever, you can move a planet."
This is a second stable release in 1.0 branch, fixing a few medium and
high priority issues, including one that affects Kubernetes' usage of
runc's libcontainer.
Bugfixes:
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.0.1 -- "If in doubt, Meriadoc, always follow your nose."
This is the first stable release in the 1.0 branch, fixing a few medium
and high priority issues with runc 1.0.0, including a few that affect
Kubernetes' usage of libcontainer.
Bugfixes:
Thanks to all of the contributors who made this release possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.0.0 -- "A wizard is never late, nor is he early, he arrives precisely when he means to."
This release fixes a few bugs found (almost all related to cgroupv2
handling), and is the first non-rc release of runc in 5 years
(v1.0.0-rc1 was released in 2016). It's been a very long road, and we
thank the many contributors and maintainers that helped us get to this
point (approximately 422 people in total).
As runc follows Semantic Versioning, we will endeavor to not make any
breaking changes without bumping the major version number of runc.
However, it should be noted that Go API usage of runc's internal
implementation (libcontainer) is not covered by this policy -- for
historical reasons, this code was not moved into an "internal" package
(this feature did not exist in Go at the time) and because certain
projects currently depend on this, we have not yet moved this code into
an internal package. Despite this, we reserve the right to make breaking
changes in our Go APIs (though we will note such changes in our
changelog, and will try to avoid needless disruption if possible).
Breaking changes:
Deprecations:
Bugfixes:
runc update and avoid leaking eBPF programsImprovements:
go get orrunc update). (#2994)Thanks to the following people who made this release possible:
Vote: +5 -0 %2
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v1.0.0-rc95 -- "Just when I thought I was out, they pull me back in."
This release of runc contains a fix for CVE-2021-304651, and users are
strongly recommended to update (especially if you are providing
semi-limited access to spawn containers to untrusted users).
Aside from this security fix, only a few other changes were made since
v1.0.0-rc94 (the only user-visible change was the addition of support
for defaultErrnoRet in seccomp profiles).
Thanks to the following people who made this release possible:
Due to the nature of this release, it didn't go through the normal
public release procedure. However, this break from procedure was agreed
upon on the security mailing list.
Signed-off-by: Aleksa Sarai cyphar@cyphar.com