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
Describe the bug
When running insider in docker, the report gets generated in /opt/insider. This is a problem because the report is hard to access once the container has stopped. The image is basically mixing binaries and data. The report should written to a separate directory, for instance /var/insider so one may bind that to another volume, or sent to stdout.
Describe the bug
When running insider in docker, the report gets generated in
/opt/insider
. This is a problem because the report is hard to access once the container has stopped. The image is basically mixing binaries and data. The report should written to a separate directory, for instance/var/insider
so one may bind that to another volume, or sent to stdout.To Reproduce
Steps to reproduce the behavior:
docker run --name container -v /path:/target insidersec/insider -tech csharp -target /target
docker comit container image
docker run -ti --entrypoint=sh image
ls -l /opt/insider
Expected behavior
report placed somewhere else or output to stdout
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: