-
Notifications
You must be signed in to change notification settings - Fork 97
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
Unpack on NFS and Extended File Attributes #248
Comments
We should ignore
I took a look at that fix, and it has a couple of issues (mainly how extensible it is) -- but don't worry, I have my own proposed fix I started working on when I saw your other issue. I'll post that one, and ping you when it's ready to test. But thanks for writing a sample PR anyway! 😸 |
Thank you very much! Indeed it was just a quick fix allowing me to test the umoci integration meanwhile and also to check that I was not reporting something dumb 😄 |
Sorry for the delay. The current update is that at the moment I have it implemented, but I'm having trouble coming up with a way of testing it -- because all of the current always-ignore xattrs are not really writable as a user. I will publish a PR in a bit which should have it tested, as soon as I figure out how to make certain xattrs only ignored when running a test binary (it turns out that |
Hi all,
Issue
I tried to use umoci to extract images on an NFS file-system and encountered various errors linked to extended file attributes. Umoci fails to unpack in both rootless and default cases.
Reproducer
You need to be on an NFS mount.
Discussion
This is linked to the fact that NFS does not support extended file attributes. When removing 'system.nfs4_acl' in Lclearxattrs you get EIO and overall when setting any xattr in Lsetxattr you get ENOTSUP.
Proposed Fix
I humbly tempted an initial fix which seems to solve the issue on my system in this branch:
https://github.com/besnardjb/umoci/tree/nfs
However, as it alters the resulting image (i.e. losing xattr data) it might deserve a warning as some data of the image was lost even if not representable in the target fs?
Thanks,
Jean-Baptiste.
The text was updated successfully, but these errors were encountered: