You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Throughout Syft's execution, it writes and reads temporary data on disk. When Syft receives the signal SIGINT, it should gracefully exit, which includes removing any temp data that it had written, but Syft doesn't do this.
The text was updated successfully, but these errors were encountered:
PR #448 will address this problem at a bare minimum by using stereoscope.Cleanup once an interrupt is received --which cleans up the majority of the volume for temp files.
Ideally the workers should have a coordinated shutdown by passing context to indicate a cancellation intent and allowing the happy path to drive temp dir/file cleanup (and happy path cleanup should not use global state for tracking temp files).
I'm leaving these closed PRs here for reference, they may or may not be part of a solution to solve this later:
As of right now I'm not seeing evidence of syft leaving temp files on disk when SIGINT is received (something that is partially handled in anchore/clio and the other part in syft itself. We are passing context through many levels, but not all levels, to help coordinate shutdown.
Throughout Syft's execution, it writes and reads temporary data on disk. When Syft receives the signal SIGINT, it should gracefully exit, which includes removing any temp data that it had written, but Syft doesn't do this.
The text was updated successfully, but these errors were encountered: