Closed hallyn closed 10 months ago
I'm using my tree so builds can happen. Obviously we'll want to get that fix back into github.com/project-stacker/umoci
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
47f8230
) 13.02% compared to head (3f1ad55
) 57.16%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
We end up with errors like:
/home/shallyn/stackertest2/roots/test2/overlay/etc/systemd/system/multi-user.target.wants: dropped overlay attrs: user.overlay.origin error: no data available get xattr: user.overlay.origin github.com/opencontainers/umoci/oci/layer.(*tarGenerator).AddFile /stacker-tree/.build/gopath/pkg/mod/github.com/project-stacker/umoci@v0.0.0-20231025233220-c7bb24d57e98/oci/layer/tar_generate.go:225 github.com/opencontainers/umoci/oci/layer.GenerateInsertLayer.func1.2
Unless there is an actual data i/o error, ignore it. In particular, if the fs either says eopnotsupp, enodata, or eperm, just assume the xattr did not actually exist. We have to do this because there are cases where listxattr will return xattr keys which getxattr will filter out, and we're expected to ignore those.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.