CI: Disable seccomp filter for docker build tests #122
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
When target system updated to glibc-2.34 (as for ALT Linux) it starts to use new syscall `clone3', which is not enabled in Docker seccomp filter, causing run failures. GA issue [1]. Disable Docker seccomp filtering since we are in throwable virtual environment anyway and don't need that protection. Link: actions/runner-images#3812 [1] Fixes: lkrg-org#121 Signed-off-by: Vitaly Chikunov <[email protected]>
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.
When target system updated to glibc-2.34 (as for ALT Linux) it starts
to use new syscall `clone3', which is not enabled in Docker seccomp
filter, causing run failures. GA issue [1].
Disable Docker seccomp filtering since we are in throwable virtual
environment anyway and don't need that protection.
Link: actions/runner-images#3812 [1]
Fixes: #121