-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to pull image : Error processing tar file(exit status 1): lsetxattr /vendor: invalid argument
#1076
Comments
how was the image created? The file @rhatdan should we ignore |
ignore the security.selinux xattr if it is present in the tarball header, since invalid labels cannot be set by unprivileged users and the `lsetxattr` syscall fails with EINVAL. Closes: containers#1076 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
opened a PR: #1077 |
ignore the security.selinux xattr if it is present in the tarball header, since invalid labels cannot be set by unprivileged users and the `lsetxattr` syscall fails with EINVAL. Closes: containers#1076 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
I'm not 100% sure how these images are getting created. However It seems that the filesystem is built by some build system used to build android. |
Yes we should ignore selinux labels in an image. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Trying to pull image results in error.
Steps to reproduce the issue:
podman pull docker.io/redroid/redroid:12.0.0-latest
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional details:
Seems to work ok when running the same command as sudo.
Skopeo copy to containers-storage returns the same results:
Skopeo copy to dir or oci returns:
The text was updated successfully, but these errors were encountered: