build(deps): Bump github.com/opencontainers/runc from 1.3.4 to 1.3.5

[dependabot]

Bumps github.com/opencontainers/runc from 1.3.4 to 1.3.5.

Release notes

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

runc v1.3.5 -- "Lo viejo funciona!"

This is the fifth patch release of the 1.3.z release series of runc, and primarily contains a few fixes for issues found in 1.3.4.

Fixed

• Recursive atime-related mount flags (rrelatime et al.) are now applied properly. (#5115, #5098)
• PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted. (#5158, #5153, #5151, #4645, #4757)

Changed

• Updated builds to Go 1.25, libseccomp v2.6.0. (#5111, #5053)
• Minor signing keyring updates. (#5146, #5139, #5144, #5148)

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 cyphar@cyphar.com
• Kir Kolyshkin kolyshkin@gmail.com
• Li Fu Bang lifubang@acmcoder.com
• Ricardo Branco rbranco@suse.de

Changelog

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

[1.3.5] - 2026-03-17

Lo viejo funciona!

Fixed

• Recursive atime-related mount flags (rrelatime et al.) are now applied properly. (#5115, #5098)
• PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted. (#5158, #5153, #5151, #4645, #4757)

Changed

• Updated builds to Go 1.25, libseccomp v2.6.0. (#5111, #5053)
• Minor signing keyring updates. (#5146, #5139, #5144, #5148)

Commits

• 488fc13 VERSION: release 1.3.5
• c5f4a41 Merge pull request #5181 from kolyshkin/1.3-go126
• 692817a ci: add go 1.26
• 9183ee6 Merge pull request #5158 from kolyshkin/1.3-5153
• 3755b0e Revert "Preventing containers from being unable to be deleted"
• abf41c1 Merge pull request #5146 from cyphar/1.3-keyring-fixes
• 030e224 keyring: update AkihiroSuda's key
• ccea037 keyring: validate: allow maintainers to have no keys
• e001bca keyring: remove asarai@suse.de key
• ffd5a10 Merge pull request #5135 from kolyshkin/1.3-5124
• 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 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)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.