Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify expected PAX headers for xattrs (LIBARCHIVE.xattr. vs. SCHILY.xattr.) #725

Open
wking opened this issue Aug 26, 2017 · 1 comment
Open

Clarify expected PAX headers for xattrs (LIBARCHIVE.xattr. vs. SCHILY.xattr.) #725

wking opened this issue Aug 26, 2017 · 1 comment

Comments

@wking
Copy link
Contributor

wking commented Aug 26, 2017 •
edited
Loading

The layer spec requires layer to, “where supported”, include xattrs. But there seem to be two extended header prefixes in use for xattrs: LIBARCHIVE.xattr. and SCHILY.xattr. (libarchive/libarchive#691). GNU tar prefers SCHILY.xattr, and Go reads SCHILY.xattr.* into Header.Xattrs (although that will be deprecated in Go 1.10, golang/go#14472). It's probably worth clarifying in the spec which prefix SHOULD be used in OCI layers, and whether unpackers MUST support one or both prefixes when they support xattrs.
@wking
Copy link
Contributor Author

wking commented Aug 26, 2017

@jstarks mentioned these prefixes in moby/moby#20125, but he was looking for a place to store Windows metadata. This issue is just about portably storing the Linux xattr (and other OSes that use those same prefixes, if any).

@neersighted neersighted mentioned this issue May 30, 2023
Closed
@Kern-- Kern-- mentioned this issue Aug 30, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wking