Bump runc from v1.1.13 to v1.1.15 #52
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v1.1.15
Tag: v1.1.15
Published at: 2024-10-07T21:38:10Z
URL: Release v1.1.15
Description:
This is the fifteenth patch release in the 1.1.z release branch of runc.
It fixes a few issues with seccomp, leaked mounts, and system performance.
-ENOSYSseccomp stub is now always generated for the nativearchitecture that
runcis running on. This is needed to work around somearguably specification-incompliant behaviour from Docker on architectures
such as ppc64le, where the allowed architecture list is set to
null. Thisensures that we always generate at least one
-ENOSYSstub for the nativearchitecture even with these weird configs. (# 4391)
/proc/self/mountinfomay skip someentries, as a consequence runc may not properly set mount propagation,
causing container mounts leak onto the host mount namespace. (# 2404, # 4425)
against [CVE-2019-5736], the temporary
robind-mount of/proc/self/exehas been removed. runc now creates a binary copy in all cases. (# 4392, # 2532)
Static Linking Notices
The
runcbinary distributed with this release are statically linked withthe following GNU LGPL-2.1 licensed libraries, with
runcactingShow more
as a "work that uses the Library":
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 all of the contributors who made this release possible:
Commits
bc20cb4VERSION: release 1.1.152790485CHANGELOG: Remove empty changed lineed38aeaMerge pull request # 4425 from kolyshkin/1.1-fix-mount-leak65aa700[1.1] runc run: fix mount leaka4cebd3Merge pull request # 4423 from rata/1-1-fix-CI