chore(deps): bump github.com/opencontainers/runc from 1.1.12 to 1.1.13

[dependabot[bot]]

Bumps github.com/opencontainers/runc from 1.1.12 to 1.1.13.

Changelog

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

[1.1.13] - 2024-06-13

There is no certainty in the world. This is the only certainty I have.

Important Notes

• If building with Go 1.22.x, make sure to use 1.22.4 or a later version. (see #4233 for more details)

Fixed

• Support go 1.22.4+. (#4313)
• runc list: fix race with runc delete. (#4231)
• Fix set nofile rlimit error. (#4277, #4299)
• libct/cg/fs: fix setting rt_period vs rt_runtime. (#4284)
• Fix a debug msg for user ns in nsexec. (#4315)
• script/*: fix gpg usage wrt keyboxd. (#4316)
• CI fixes and misc backports. (#4241)
• Fix codespell warnings. (#4300)

Changed

• Silence security false positives from golang/net. (#4244)
• libcontainer: allow containers to make apps think fips is enabled/disabled for testing. (#4257)
• allow overriding VERSION value in Makefile. (#4270)
• Vagrantfile.fedora: bump Fedora to 39. (#4261)
• ci/cirrus: rm centos stream 8. (#4305, #4308)

[1.2.0-rc.1] - 2024-04-03

There's a frood who really knows where his towel is.

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

... (truncated)

Commits

• 58aa920 VERSION: release 1.1.13
• 2b3a247 Merge pull request #4316 from lifubang/backport-4189
• 3507ada Merge pull request #4315 from lifubang/backport-4311
• 0f7150a script/*: fix gpg usage wrt keyboxd
• 80186fe fix a debug msg for user ns in nsexec
• 8407d3c Merge pull request #4313 from kolyshkin/1.1-backport-4292
• 7219e0a Dockerfile: bump Debian to 12, Go to 1.21
• c9beabc ci: switch to go 1.22 as main version
• 4578c6c libct/nsenter: stop blacklisting go 1.22+
• c488d13 use go mod instead of go get in spec.bats
• 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 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)