[master] rpm: disable seccomp to prevent tar EPERM (Fedora 40 ppc64le on Debian) #1013
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
commit 07b5d90 disabled seccomp for the deb-builds because `chmod` failed tar was failing with an EPERM (Ubuntu 24.04 armhf on 20.04 host). It looks like the same problem happens when running Fedora 40 on a Debian bookworm host on ppc64le. That issue was confirmed to be related to `fchmodat2(2)`, which is a new syscall that's not supported on the host, and therefore gets the seccomp's default EPERM; fchmodat2(AT_FDCWD, "docker", 0775, AT_SYMLINK_NOFOLLOW) = -1 EPERM (Operation not permitted) tar: docker: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors Ultimately we need to update the libseccomp profile to use ENOSYS (see moby ticket 42871) to allow it to degrade gracefully; fchmodat2(AT_FDCWD, "docker", 0775, AT_SYMLINK_NOFOLLOW) = -1 ENOSYS (Function not implemented) Signed-off-by: Sebastiaan van Stijn <[email protected]>
|
cc @AshwinHIBM |
vvoland
approved these changes
Apr 12, 2024
|
Let me bring this one in, but let us know if it worked, @AshwinHIBM |
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.
commit 07b5d90 disabled seccomp for the deb-builds because
chmodfailed tar was failing with an EPERM (Ubuntu 24.04 armhf on 20.04 host).It looks like the same problem happens when running Fedora 40 on a Debian bookworm host on ppc64le.
That issue was confirmed to be related to
fchmodat2(2), which is a new syscall that's not supported on the host, and therefore gets the seccomp's default EPERM;Ultimately we need to update the libseccomp profile to use ENOSYS (see moby ticket 42871) to allow it to degrade gracefully;
- A picture of a cute animal (not mandatory but encouraged)