slimtoolkit / slimtoolkit/slim
Files deleted on probing stage aren't included in reports
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
When a file is deleted during probing, it should appear in the slim version of the image. Deleting a file means access, and that automatically should qualify the file as used.
Actual Behavior
When some files are deleted during probing, they aren't included in the creport.json file and the files folder. It happens because the artifact dumping logic fails to copy those files. Preserving files also don't mitigate the issue because that same logic iterates over the preserved files, but tries to check the existence of the original files too (and fails).
Steps to Reproduce the Problem
Here is a (skipped for now) E2E test
Specifications
- Version: 1.37+
- Platform: All
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pkg/app/sensor/app_test.go and the artifact-dumping path described in the report. Run or review the skipped E2E case to trace how deleted and preserved files are handled. Done means files deleted during probing appear in the slim image, creport.json, and files folder, including when preservation is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100