Skip to content
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.

image analysis scratch space removal partially fails if image files have non-readable modes #579

Closed
nurmi opened this issue Aug 18, 2020 · 0 comments · Fixed by #580
Closed
Assignees
Labels
area:analysis Image analysis issues (squashing, artifact detection, etc) bug
Milestone

Comments

@nurmi
Copy link
Member

nurmi commented Aug 18, 2020

In rare cases, a condition has been observed where files inside an image's layer tarballs have a file mode that results in non-readable files when extracted (i.e. mode 0x0000). Some anchore analyzers extract targetted files for analysis, and when this occurs the extracted files cannot be removed from the analysis scratch space after image analysis is completed.

This condition doesn't prevent images from being analyzed, but it does create left over data in analysis scratch space that could grow slowly over time.

Proposed solution is to explicitly detect this condition and ensure that such files have a readable mode when temporarily extracted, so that they can be removed cleanly upon analysis completion.

@nurmi nurmi added bug area:analysis Image analysis issues (squashing, artifact detection, etc) labels Aug 18, 2020
@nurmi nurmi added this to the v0.8.1 milestone Aug 18, 2020
@nurmi nurmi self-assigned this Aug 18, 2020
nurmi added a commit that referenced this issue Aug 18, 2020
…e file modes unset, preventing cleanup of analysis scratch space. Fixes #579.

Signed-off-by: Daniel Nurmi <nurmi@anchore.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:analysis Image analysis issues (squashing, artifact detection, etc) bug
Projects
None yet
1 participant