Skip to content

update runc binary to 1.1.15#10787

Merged
samuelkarp merged 1 commit intocontainerd:mainfrom
samuelkarp:runc-1.1.15
Oct 8, 2024
Merged

update runc binary to 1.1.15#10787
samuelkarp merged 1 commit intocontainerd:mainfrom
samuelkarp:runc-1.1.15

Conversation

@samuelkarp
Copy link
Copy Markdown
Member

@samuelkarp samuelkarp commented Oct 7, 2024

diff: opencontainers/runc@v1.1.14...v1.1.15

Release notes:

  • The -ENOSYS seccomp stub is now always generated for the native architecture that runc is running on. This is needed to work around some arguably specification-incompliant behaviour from Docker on architectures such as ppc64le, where the allowed architecture list is set to null. This ensures that we always generate at least one -ENOSYS stub for the native architecture even with these weird configs. (#4391)
  • On a system with older kernel, reading /proc/self/mountinfo may skip some entries, as a consequence runc may not properly set mount propagation, causing container mounts leak onto the host mount namespace. (#2404, #4425)
  • In order to fix performance issues in the "lightweight" bindfd protection against [CVE-2019-5736], the temporary ro bind-mount of /proc/self/exe has been removed. runc now creates a binary copy in all cases. (#4392, #2532)

diff: opencontainers/runc@v1.1.14...v1.1.15

Release notes:

- The -ENOSYS seccomp stub is now always generated for the native
  architecture that runc is running on. This is needed to work around some
  arguably specification-incompliant behaviour from Docker on architectures
  such as ppc64le, where the allowed architecture list is set to null. This
  ensures that we always generate at least one -ENOSYS stub for the native
  architecture even with these weird configs. (containerd#4391)
- On a system with older kernel, reading /proc/self/mountinfo may skip some
  entries, as a consequence runc may not properly set mount propagation,
  causing container mounts leak onto the host mount namespace. (containerd#2404, containerd#4425)
- In order to fix performance issues in the "lightweight" bindfd protection
  against [CVE-2019-5736], the temporary ro bind-mount of /proc/self/exe
  has been removed. runc now creates a binary copy in all cases. (containerd#4392, containerd#2532)

Signed-off-by: Samuel Karp <[email protected]>
@samuelkarp samuelkarp enabled auto-merge October 8, 2024 01:43
@samuelkarp samuelkarp added this pull request to the merge queue Oct 8, 2024
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 8, 2024
@samuelkarp samuelkarp added this pull request to the merge queue Oct 8, 2024
Merged via the queue into containerd:main with commit ce648b5 Oct 8, 2024
@samuelkarp
Copy link
Copy Markdown
Member Author

/cherrypick release/1.7

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@samuelkarp: new pull request created: #10794

Details

In response to this:

/cherrypick release/1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@samuelkarp
Copy link
Copy Markdown
Member Author

/cherrypick release/1.6

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@samuelkarp: new pull request created: #10795

Details

In response to this:

/cherrypick release/1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@chrishenzie chrishenzie added cherry-picked/1.6.x PR commits are cherry-picked into release/1.6 branch cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch labels Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-picked/1.6.x PR commits are cherry-picked into release/1.6 branch cherry-picked/1.7.x PR commits are cherry-picked into release/1.7 branch size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants