fix: non completed containers with invalid stacktrace

[chen-keinan]

Description

non completed containers with invalid stacktrace

Related issues

• Close Stacktrace when scanning k8s containers and no info about the problem #2101

Checklist

• I've read the guidelines for contributing to this repository.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).

[ymettier]

This PR will fix #2101 .

But isn't there a regression here ? If Trivy fails (like described in #2101 ) will there be any way to detect it ?

The stacktrace was a way to detect the problem and it is now removed.

[chen-keinan]

@ymettier thanks for the input, I'll revert the change, after investigating the issue its look like root case related to latest changes with trivy logger, its under investigation.

• Related fix(cli): always output fatal errors to stderr trivy#6827