runc v1.4.0 -- "路漫漫其修远兮，吾将上下而求索！"

This is the first release of the 1.4.z release branch of runc. It
contains a few fixes for issues found in 1.4.0-rc.3. This version of
runc supports runtime-spec v1.3 (see docs/spec-conformance.md for the
few features that are still missing).

This is the second release of runc following our new release and support
policy (see RELEASES.md for more details). This means that, as of this
release:

• The runc 1.2.z release branch will now only receive high severity
  CVE fixes, and will no longer be supported in less than 6 months (end
  of April 2026).
• The runc 1.3.z release branch will now only receive security and
  "significant" bugfixes.
• Users are encouraged to plan migrating to runc 1.4.0 as soon as
  possible.
• Despite this release being delayed by a month, users should still
  expect a runc 1.5.0 release in late April 2026.

Deprecated

• Deprecate cgroup v1. (#4956)
• Deprecate CleanPath, StripRoot, WithProcfd, and WithProcfdFile from
  libcontainer/utils. (#4985)

Breaking

• The handling of pids.limit has been updated to match the newer guidance
  from the OCI runtime specification. In particular, now a maximum limit value
  of 0 will be treated as an actual limit (due to limitations with systemd,
  it will be treated the same as a limit value of 1). We only expect users
  that explicitly set pids.limit to 0 will see a behaviour change.
  (opencontainers/cgroups#48, #4949)

Fixed

• cgroups: provide iocost statistics for cgroupv2. (opencontainers/cgroups#43)
• cgroups: retry DBus connection when it fails with EAGAIN.
  (opencontainers/cgroups#45)
• cgroups: improve cpuacct.usage_all resilience when parsing data from
  patched kernels (such as the Tencent kernels). (opencontainers/cgroups#46,
  opencontainers/cgroups#50)
• libct: close child fds on prepareCgroupFD error. (#4936)
• libct: fix mips compilation. (#4962, #4967)
• When configuring a tmpfs mount, only set the mode= argument if the target
  path already existed. This fixes a regression introduced in our
  CVE-2025-52881 mitigation patches. (#4971, #4976)
• Fix various file descriptor leaks and add additional tests to detect them as
  comprehensively as possible. (#5007, #5021, #5034)
• The "hallucination" helpers added as part of the CVE-2025-52881
  mitigation have been made more generic and now apply to all of our pathrs
  helper functions, which should ensure we will not regress dangling symlink
  users. (#4985)

Changed

• libct: switch to (*CPUSet).Fill. (#4927)
• docs/spec-conformance.md: update for spec v1.3.0. (#4948)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Li Fu Bang [email protected]
• Rodrigo Campos [email protected]
• Tianon Gravi [email protected]

runc v1.3.4 -- "Take me to your heart, take me to your soul."

This is the fourth patch release of the 1.3.z release series of runc,
and primarily contains a few fixes for some regressions introduced in
1.3.3.

Fixed

• libct: fix mips compilation. (#4962, #4966)
• When configuring a tmpfs mount, only set the mode= argument if the
  target path already existed. This fixes a regression introduced in our
  CVE-2025-52881 mitigation patches. (#4971, #4976)
• Fix various file descriptor leaks and add additional tests to detect them as
  comprehensively as possible. (#5007, #5021, #5034)

Changed

• Downgrade github.com/cyphar/filepath-securejoin dependency to v0.5.2,
  which should make it easier for some downstreams to import runc without
  pulling in too many extra packages. (#5028)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Li Fu Bang [email protected]
• Tianon Gravi [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.2.9 -- "Stars hide your fires, let me rest tonight."

This is the ninth patch release of the 1.2.z release series of runc, and
primarily contains a few fixes for some regressions introduced in 1.2.8.

Fixed

• libct: fix mips compilation. (#4962, #4965)
• When configuring a tmpfs mount, only set the mode= argument if the
  target path already existed. This fixes a regression introduced in our
  CVE-2025-52881 mitigation patches. (#4971, #4974)
• Fix various file descriptor leaks and add additional tests to detect them as
  comprehensively as possible. (#5007, #5021, #5027)

Changed

• Downgrade github.com/cyphar/filepath-securejoin dependency to v0.5.2,
  which should make it easier for some downstreams to import runc without
  pulling in too many extra packages. (#5027)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Li Fu Bang [email protected]
• Tianon Gravi [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.4.0-rc.3 -- "その日、人類は思い出した。"

Note

Some vendors were given patches corresponding to this release in
advance. This public release includes two extra patches to fix
regressions discovered very late during the embargo period and were
thus not included in the pre-release versions. Please update to this
version.

Security

This release includes fixes for the following high-severity security issues:

• CVE-2025-31133 exploits an issue with how masked paths are implemented in
  runc. When masking files, runc will bind-mount the container's /dev/null
  inode on top of the file. However, if an attacker can replace /dev/null
  with a symlink to some other procfs file, runc will instead bind-mount the
  symlink target read-write. This issue affected all known runc versions.

• CVE-2025-52565 is very similar in concept and application to
  CVE-2025-31133, except that it exploits a flaw in /dev/console
  bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n),
  if an attacker replaces /dev/pts/$n with a symlink then runc will
  bind-mount the symlink target over /dev/console. This issue affected all
  versions of runc >= 1.0.0-rc3.

• CVE-2025-52881 is a more sophisticated variant of CVE-2019-19921,
  which was a flaw that allowed an attacker to trick runc into writing the LSM
  process labels for a container process into a dummy tmpfs file and thus not
  apply the correct LSM labels to the container process. The mitigation we
  applied for CVE-2019-19921 was fairly limited and effectively only caused
  runc to verify that when we write LSM labels that those labels are actual
  procfs files. This issue affects all known runc versions.

Fixed

• Switched to (*CPUSet).Fill rather than our hacky optimisation when
  resetting the CPU affinity of runc. (#4926, #4927)
• Correctly close child fds during (*setns).start if an error occurs.
  (#4930, #4936)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Lei Wang [email protected]
• Li Fubang [email protected]
• Rodrigo Campos [email protected]
• Tõnis Tiigi [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.3.3 -- "奴らに支配されていた恐怖を"

Note

Some vendors were given a pre-release version of this release.
This public release includes two extra patches to fix regressions
discovered very late during the embargo period and were thus not
included in the pre-release versions. Please update to this version.

This release contains fixes for three high-severity security
vulnerabilities in runc (CVE-2025-31133, CVE-2025-52565, and
CVE-2025-52881). All three vulnerabilities ultimately allow (through
different methods) for full container breakouts by bypassing runc's
restrictions for writing to arbitrary /proc files.

Security

• CVE-2025-31133 exploits an issue with how masked paths are implemented in
  runc. When masking files, runc will bind-mount the container's /dev/null
  inode on top of the file. However, if an attacker can replace /dev/null
  with a symlink to some other procfs file, runc will instead bind-mount the
  symlink target read-write. This issue affected all known runc versions.

• CVE-2025-52565 is very similar in concept and application to
  CVE-2025-31133, except that it exploits a flaw in /dev/console
  bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n),
  if an attacker replaces /dev/pts/$n with a symlink then runc will
  bind-mount the symlink target over /dev/console. This issue affected all
  versions of runc >= 1.0.0-rc3.

• CVE-2025-52881 is a more sophisticated variant of CVE-2019-19921,
  which was a flaw that allowed an attacker to trick runc into writing the LSM
  process labels for a container process into a dummy tmpfs file and thus not
  apply the correct LSM labels to the container process. The mitigation we
  applied for CVE-2019-19921 was fairly limited and effectively only caused
  runc to verify that when we write LSM labels that those labels are actual
  procfs files. This issue affects all known runc versions.

Added

• runc update now supports configuring per-device weights and iops. (#4775,
  #4807, #4825, #4931)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Lei Wang [email protected]
• Li Fubang [email protected]
• Rodrigo Campos [email protected]
• Tõnis Tiigi [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.2.8 -- "鳥籠の中に囚われた屈辱を"

Note

Some vendors were given a pre-release version of this release.
This public release includes two extra patches to fix regressions
discovered very late during the embargo period and were thus not
included in the pre-release versions. Please update to this version.

This release contains fixes for three high-severity security
vulnerabilities in runc (CVE-2025-31133, CVE-2025-52565, and
CVE-2025-52881). All three vulnerabilities ultimately allow (through
different methods) for full container breakouts by bypassing runc's
restrictions for writing to arbitrary /proc files.

Security

• CVE-2025-31133 exploits an issue with how masked paths are implemented in
  runc. When masking files, runc will bind-mount the container's /dev/null
  inode on top of the file. However, if an attacker can replace /dev/null
  with a symlink to some other procfs file, runc will instead bind-mount the
  symlink target read-write. This issue affected all known runc versions.

• CVE-2025-52565 is very similar in concept and application to
  CVE-2025-31133, except that it exploits a flaw in /dev/console
  bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n),
  if an attacker replaces /dev/pts/$n with a symlink then runc will
  bind-mount the symlink target over /dev/console. This issue affected all
  versions of runc >= 1.0.0-rc3.

• CVE-2025-52881 is a more sophisticated variant of CVE-2019-19921,
  which was a flaw that allowed an attacker to trick runc into writing the LSM
  process labels for a container process into a dummy tmpfs file and thus not
  apply the correct LSM labels to the container process. The mitigation we
  applied for CVE-2019-19921 was fairly limited and effectively only caused
  runc to verify that when we write LSM labels that those labels are actual
  procfs files. This issue affects all known runc versions.

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Aleksa Sarai [email protected]
• Kir Kolyshkin [email protected]
• Lei Wang [email protected]
• Li Fubang [email protected]
• Rodrigo Campos [email protected]
• Tõnis Tiigi [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.4.0-rc.2 -- "私の役目は信じるかどうかではない。行うかどうかだ。"

This is the second release candidate of the runc 1.4.0 release. It
includes a few minor features that did not make the cut-off for
v1.4.0-rc.1 (namely CLONE_INTO_CGROUP support and some new Intel RDT
features).

Users are strongly encouraged to test our release candidates over the
next month so we can fix issues before the general release. You should
expect runc 1.4.0 to be released at the end of October 2025 (at which
point, runc 1.2.z will only receive high-severity security fixes for 6
months and users are thus very strongly encouraged to migrate to a newer
version).

libcontainer API

• The deprecated libcontainer/userns package has been removed; use
  github.com/moby/sys/userns instead. (#4910, #4911)

Added

• Allow setting user.* sysctls for user-namespaced containers, as they are
  namespaced and thus safe to configure. (#4889, #4892)
• Add support for using clone3(2)'s CLONE_INTO_CGROUP flag when
  configuring the runc exec process. This also included some internal
  changes to how we add processes to containers. (#4822, #4812, #4920)
• Add support for configuring the NUMA pmemory policy for a container with
  set_mempolicy(2). (opencontainers/runtime-spec#1282, #4726, #4915)
• Add support for intelRdt.schemata to allow for configuration of all
  schemas in resctrl. (opencontainers/runtime-spec#1230, #4830, #4915)
• Add support for intelRdt.enableMonitoring to allow for per-container
  resctrl monitoring. This replaces the old intelRdt.enableCMT and
  intelRdt.enableMBM options which were never implemented by runc and have
  been removed from the runtime-spec. (opencontainers/runtime-spec#1287,
  #4832, #4921)

Fixed

• Configure personality(2) before applying seccomp profiles. (#4900, #4903)
• Fixed integration test failure on ppc64, caused by 64K page size so the
  kernel was rounding memory limit to 64K. (#4841, #4895, #4893)
• seccompagent: fix fd close loop to prevent closing stdio in the error path.
  (#4913, #4923)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Aleksa Sarai [email protected]
• Antti Kervinen [email protected]
• Donet Tom [email protected]
• Joshua Rogers [email protected]
• Kir Kolyshkin [email protected]
• Markus Lehtonen [email protected]
• Rodrigo Campos [email protected]
• Tycho Andersen [email protected]
• Vishal Chourasia [email protected]
• Li Fubang [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.3.2 -- "Ночь, улица, фонарь, аптека..."

This is the second patch release of the 1.3.z release series of runc.
It primarily includes some minor fixes for issues found in 1.3.1.

Changed:

• The conversion from cgroup v1 CPU shares to cgroup v2 CPU weight is
  improved to better fit default v1 and v2 values. (#4772, #4785, #4897)
• Dependency github.com/opencontainers/cgroups updated from v0.0.1 to
  v0.0.4. (#4897)

Fixed:

• runc state: fix occasional "cgroup.freeze: no such device" error.
  (#4798, #4808, #4897)
• Fixed integration test failure on ppc64, caused by 64K page size so the
  kernel was rounding memory limit to 64K. (#4841, #4895, #4893)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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 who made this release possible:

• Aleksa Sarai [email protected]
• Jared Ledvina [email protected]
• Kir Kolyshkin [email protected]
• Rodrigo Campos [email protected]

Signed-off-by: Kir Kolyshkin [email protected]

runc v1.4.0-rc.1 -- "おめェもボスになったんだろぉ？"

This is the first release candidate of the runc 1.4.0 release. It
contains a couple of new features, but is mostly made up of some minor
bug fixes and some follow-ups for features deprecated in runc 1.3.0.

Users are strongly encouraged to test our release candidates over the
next two months so we can fix issues before the general release. You
should expect runc 1.4.0 to be released at the end of October 2025 (at
which point, runc 1.2.z will only receive high-severity security fixes
for 6 months and users are thus very strongly encouraged to migrate to a
newer version).

This version of runc requires Go 1.24 to build.

libcontainer API

• The deprecated libcontainer/user package has been removed; use
  github.com/moby/sys/user instead. (#3999, #4617)
• libcontainer/apparmor variables containing public functions have been
  switched to wrapper functions. (#4725)

Breaking

• runc update no longer allows --l3-cache-schema or --mem-bw-schema if
  linux.intelRdt was not present in the container’s original config.json.

  Without linux.intelRdt no CLOS (resctrl group) is created at container
  creation, so it is not possible to apply the updated options with runc update.

  Previously, this scenario did not work as expected. The runc update would
  create a new CLOS but fail to apply the schema, move only the init process
  (omitting children) to the new group, and leave the CLOS orphaned after
  container exit. (#4827)

• The deprecated --criu flag has been removed entirely, instead the criu
  binary in $PATH will be used. (#4722)

Added

• runc now supports the linux.netDevices field to allow for devices to be
  moved into container network namespaces seamlessly. (#4538)
• runc update now supports per-device weight and iops cgroup limits. (#4775)
• intel rdt: allow explicit assignment to root CLOS. (#4854)

Fixed

• Container processes will no longer inherit the CPU affinity of runc by
  default. Instead, the default CPU affinity of container processes will be
  the largest set of CPUs permitted by the container's cpuset cgroup and any
  other system restrictions (such as isolated CPUs). (#4041, #4815, #4858)
• Use chown(uid, -1) when configuring the console inode, to avoid issues
  with unmapped GIDs. (#4679)
• Add logging for the cases where failed keyring operations are ignored during
  setup. (#4676)
• Optimise runc exec by avoiding calling into SELinux's Set.*Label when
  processLabel is not set. (#4354)
• Fix mips64 builds for remap-rootfs. (#4723)
• Setting linux.rootfsPropagation to shared or unbindable now functions
  properly. (#1755, #1815, #4724)
• runc delete and runc stop can now correctly handle cases where runc
  create was killed during setup. Previously it was possible for the
  container to be in such a state that neither runc stop nor runc
  delete would be unable to kill or delete the container. (#4534,
  #4645, #4757)
• Close seccomp agent connection to prevent resource leaks. (#4796)
• runc update will no longer clear intelRdt state information. (#4828)
• runc will now error out earlier if intelRdt is not enabled. (#4829)
• Improve filesystem operations within intelRdt manager. (#4840, #4831)
• Resolve a certain race between runc create and runc delete that would
  previously result in spurious errors. (#4735)
• CI: skip bpf tests on misbehaving udev systems. (#4825)

Changed

• Use Go's built-in pidfd_send_signal(2) support when available. (#4666)
• Make state.json 25% smaller. (#4685)
• Migrate to Go 1.22+ features. (#4687, #4703)
• Provide private wrappers around common syscalls to make -EINTR handling
  less cumbersome for the rest of runc. (#4697)
• Ignore the dmem controller in our cgroup tests, as systemd does not
  yet support it. (#4806)
• /proc/net/dev is no longer included in the permitted procfs overmount
  list. Its inclusion was almost certainly an error, and because
  /proc/net is a symlink to /proc/self/net, overmounting this was
  almost certainly never useful (and will be blocked by future kernel
  versions). (#4817)
• Simplify the prepareCriuRestoreMounts logic for checkpoint-restore.
  (#4765)
• The conversion from cgroup v1 CPU shares to cgroup v2 CPU weight is
  improved to better fit default v1 and v2 values. (#4772, #4785)
• Bump minimum Go version to 1.24. (#4851)
• CI: migrate virtualised Fedora tests from Vagrant + Cirrus to Lima + GHA. We
  still use Cirrus for the AlmaLinux tests, since they can be run without
  virtualisation. (#4664)
• CI: install fewer dependencies (#4671), bump shellcheck and bats versions
  (#4670).
• CI: remove toolchain from go.mod and add a CI check to make sure it's
  never added accidentally. (#4717, #4721)
• CI: do not allow exclude or replace directives in go.mod, to make sure
  that go install doesn't get accidentally broken. (#4750)
• CI: fix exclusion rules and allow us to run jobs manually. (#4760)
• CI: Switch to GitHub-hosted ARM runners. Thanks again to @alexellis
  for supporting runc's ARM CI up until now. (#4844, #4856)
• Various dependency updates. (#4659, #4658, #4662, #4663, #4689, #4694,
  #4702, #4701, #4707, #4710, #4746, #4756, #4751, #4758, #4764, #4768, #4779,
  #4783, #4785, #4801, #4808, #4803, #4839, #4846, #4847, #4845, #4850, #4861,
  #4860)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• Andrei Vagin [email protected]
• Antonio Ojea [email protected]
• Antti Kervinen [email protected]
• Henry Chen [email protected]
• HirazawaUi [email protected]
• Kir Kolyshkin [email protected]
• Markus Lehtonen [email protected]
• Martin Sivak [email protected]
• Mikhail Dmitrichenko [email protected]
• Pavel Liubimov [email protected]
• Peter Hunt [email protected]
• Prajwal S N [email protected]
• Rodrigo Campos [email protected]
• Sebastiaan van Stijn [email protected]
• Tigran Sogomonian [email protected]
• Yusuke Sakurai [email protected]
• jokemanfire [email protected]
• lifubang [email protected]
• ningmingxiao [email protected]

Signed-off-by: Aleksa Sarai [email protected]

runc v1.3.1 -- "この瓦礫の山でよぉ"

This is the first patch release of the 1.3.z release series of runc. It
primarily includes some minor fixes for issues found in 1.3.0.

Fixed

• Container processes will no longer inherit the CPU affinity of runc by
  default. Instead, the default CPU affinity of container processes will be
  the largest set of CPUs permitted by the container's cpuset cgroup and any
  other system restrictions (such as isolated CPUs). (#4041, #4815, #4858)
• Setting linux.rootfsPropagation to shared or unbindable now functions
  properly. (#1755, #1815, #4724, #4789)
• Close seccomp agent connection to prevent resource leaks. (#4796, #4799)
• runc delete and runc stop can now correctly handle cases where
  runc create was killed during setup. Previously it was possible for the
  container to be in such a state that neither runc stop nor runc delete
  would be unable to kill or delete the container. (#4534, #4645, #4757,
  #4788)
• runc update will no longer clear intelRdt state information. (#4828,
  #4833)
• CI: Fix exclusion rules and allow us to run jobs manually. (#4760, #4763)

Changed

• Improvements to the deprecation warnings as part of the
  github.com/opencontainers/cgroups split. (#4784, #4788)
• Disable the dmem controller in our cgroup tests, as systemd does not yet
  support it. (#4806, #4811)
• /proc/net/dev is no longer included in the permitted procfs overmount
  list. Its inclusion was almost certainly an error, and because /proc/net
  is a symlink to /proc/self/net, overmounting this was almost certainly
  never useful (and will be blocked by future kernel versions). (#4817, #4820)
• Simplify the prepareCriuRestoreMounts logic for checkpoint-restore.
  (#4765, #4871)
• CI: Bump golangci-lint to v2.1. (#4747, #4754)
• CI: Switch to GitHub-hosted ARM runners. Thanks again to @alexellis for
  supporting runc's ARM CI up until now. (#4844, #4856, #4867)

Static Linking Notices

The runc binary distributed with this release are statically linked with
the following GNU LGPL-2.1 licensed libraries, with runc acting
as a "work that uses the Library":

• libseccomp

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 who made this release possible:

• Akihiro Suda [email protected]
• Aleksa Sarai [email protected]
• HirazawaUi [email protected]
• Kir Kolyshkin [email protected]
• Markus Lehtonen [email protected]
• Martin Sivak [email protected]
• Pavel Liubimov [email protected]
• Peter Hunt [email protected]
• Rodrigo Campos [email protected]
• Yusuke Sakurai [email protected]
• lfbzhm [email protected]
• ningmingxiao [email protected]

Signed-off-by: Aleksa Sarai [email protected]