Dockerfile: update runc binary to 1.1.15#5417
Closed
austinvazquez wants to merge 1 commit intomoby:masterfrom
Closed
Dockerfile: update runc binary to 1.1.15#5417austinvazquez wants to merge 1 commit intomoby:masterfrom
austinvazquez wants to merge 1 commit intomoby:masterfrom
Conversation
Signed-off-by: Austin Vazquez <macedonv@amazon.com>
Contributor
Author
|
Opening prematurely to test if any issues with runc/containerd integration with buildkit. moby usually waits to consume runc release once containerd has vetted it. containerd 1.6 CI (containerd/containerd#10795) has exposed an issue with runc v1.1.15 with cgroupfs driver. |
Contributor
Author
|
1.2 is out. Closing in favor of that. |
This file contains hidden or 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
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.
diff: opencontainers/runc@v1.1.14...v1.1.15
Release Notes:
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.
entries, as a consequence runc may not properly set mount propagation,
causing container mounts leak onto the host mount namespace.
against [https://github.com/advisories/GHSA-gxmr-w5mj-v8hh], the temporary ro bind-mount of /proc/self/exe
has been removed. runc now creates a binary copy in all cases.