chore(deps): bump github.com/opencontainers/runc from 1.1.14 to 1.2.5

[dependabot]

Bumps github.com/opencontainers/runc from 1.1.14 to 1.2.5.

Release notes

Sourced from github.com/opencontainers/runc's releases.

runc v1.2.5 -- "Мороз и солнце; день чудесный!"

This is the fifth patch release in the 1.2.z series of runc. It primarily fixes an issue caused by an upstream systemd bug.

• There was a regression in systemd v230 which made the way we define device rule restrictions require a systemctl daemon-reload for our transient units. This caused issues for workloads using NVIDIA GPUs. Workaround the upstream regression by re-arranging how the unit properties are defined. (#4568, #4612, #4615)
• Dependency github.com/cyphar/filepath-securejoin is updated to v0.4.1, to allow projects that vendor runc to bump it as well. (#4608)
• CI: fixed criu-dev compilation. (#4611)
• Dependency golang.org/x/net is updated to 0.33.0. (#4632)

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]
• Brad Davidson [email protected]
• Jian Wen [email protected]
• Kir Kolyshkin [email protected]
• Rodrigo Campos [email protected]
• lifubang [email protected]

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

runc v1.2.4 -- "Христос се роди!"

This is the fourth patch release of the 1.2.z release branch of runc. It includes a fix for a regression introduced in 1.2.0 related to the

... (truncated)

Changelog

Sourced from github.com/opencontainers/runc's changelog.

[1.2.5] - 2025-02-13

Мороз и солнце; день чудесный!

Fixed

• There was a regression in systemd v230 which made the way we define device rule restrictions require a systemctl daemon-reload for our transient units. This caused issues for workloads using NVIDIA GPUs. Workaround the upstream regression by re-arranging how the unit properties are defined. (#4568, #4612, #4615)
• Dependency github.com/cyphar/filepath-securejoin is updated to v0.4.1, allowing projects that vendor runc to bump it as well. (#4608)
• CI: fixed criu-dev compilation. (#4611)

Changed

• Dependency golang.org/x/net is updated to 0.33.0. (#4632)

[1.2.4] - 2025-01-07

Христос се роди!

Fixed

• Re-add tun/tap devices to built-in allowed devices lists.

  In runc 1.2.0 we removed these devices from the default allow-list (which were added seemingly by accident early in Docker's history) as a precaution in order to try to reduce the attack surface of device inodes available to most containers (#3468). At the time we thought that the vast majority of users using tun/tap would already be specifying what devices they need (such as by using --device with Docker/Podman) as opposed to doing the mknod manually, and thus there would've been no user-visible change.

  Unfortunately, it seems that this regressed a noticeable number of users (and not all higher-level tools provide easy ways to specify devices to allow) and so this change needed to be reverted. Users that do not need these devices are recommended to explicitly disable them by adding deny rules in their container configuration. (#4555, #4556)

[1.2.3] - 2024-12-12

Winter is not a season, it's a celebration.

Fixed

• Fixed a regression in use of securejoin.MkdirAll, where multiple runc processes racing to create the same mountpoint in a shared rootfs would result in spurious EEXIST errors. In particular, this regression caused issues with BuildKit. (#4543, #4550)
• Fixed a regression in eBPF support for pre-5.6 kernels after upgrading Cilium's eBPF library version to 0.16 in runc. (#3008, #4551)

... (truncated)

Commits

• 59923ef VERSION: release v1.2.5
• 165b103 release: explicitly set --keyserver in release signing scripts
• 66c6d08 Merge pull request #4632 from lifubang/1.2-bump-xnet-to-0.33.0
• 615240a build(deps): bump golang.org/x/net from 0.24.0 to 0.33.0
• d0ed7f7 Merge pull request #4619 from kolyshkin/1.2-4616
• 6635338 Merge pull request #4615 from kolyshkin/1.2-4612
• 04468c0 libc/int/userns: add build tag to C file
• 9742b6c libct/cg/sd: set the DeviceAllow property before DevicePolicy
• de92f4b Merge pull request #4608 from kolyshkin/1.2-4590
• 00f4a5c deps: update to github.com/cyphar/[email protected]
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[pkazmierczak]

This requires a refactoring, so I opened up #25138 instead