fix seccomp compatibility in 32bit arm #1955
Merged
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
Seccomp 2.4.2 is needed for new time64 syscalls not to error in applications Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
This was referenced Jan 26, 2021
AkihiroSuda
approved these changes
Jan 28, 2021
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.
fixes #1946 #docker/buildx#511
Seccomp 2.4.2 with seccomp/libseccomp@bf747eb is needed for new time64 syscalls not to error in applications.
The result is very hacky because debian does not provide compatible packages for s390x/pcc64le (yet?). Hopefully, this can all be removed and moved to alpine with tonistiigi/xx#14 but there is still some work to do with that(namely lld doesn't work for s390x) and not sure when I'll have time to complete it.
Signed-off-by: Tonis Tiigi tonistiigi@gmail.com