-
Notifications
You must be signed in to change notification settings - Fork 245
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
Setting shared xattr fails on images with named pipes #2174
Comments
I think this probably should be ignored. @giuseppe WDYT? |
Thanks for considering this. Found one more image with a similar error: Image:
Identifies as character device file.
|
Third example that fails. Image: Error: |
I know that you are not allowed to set User XATTRS on symbolic links. |
Right. I think setting xattrs should be skipped for those special file types. I think they end up in container images by accident and having their permissions slightly off due to missing |
I didn't see errors from symbolic links. Maybe those files are already skipped by Podman? |
symlinks are already ignored.
I am not sure. Ignoring the issue is easy, but it could cause a different behavior in the container. It is safer to extend |
when ignore_chown_errors is set, ignore also failures from setting the override mode xattr. Closes: containers#2174 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
opened a PR: #2175 |
Issue Description
This is a bit of an edge case. When extracting an image that has a named pip inside, setting the xattr
user.containers.override_stat
forforce_mask=shared
fails. Usingsetfattr
directly also fails.I'm assuming this is a limitation of extended attributes, but wonder if Podman should ignore such errors instead of failing to pull the image.
Steps to reproduce the issue
Steps to reproduce the issue. (All run as root user)
Pulling the image with
podman pull
Using
setfattr
directly fails on the same file:File seems to be a named pipe:
Describe the results you received
Pulling the image fails with
force_mask=shared
setting.Describe the results you expected
Pulling the image should succeed, even if the xattr of this one file isn't set.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: