ERROR when running the Application Inspector in WSL 2
See original GitHub issueDescribe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Download the OWASP Benchmark by
git clone https://github.com/OWASP-Benchmark/BenchmarkJava
. - Change the directory to the benchmark:
cd BenchmarkJava
. - Run ApplicationInspector with
appinspector analyze -s ./
. - See the error.
Expected behavior
Get the result file from the benchmark.
Screenshots
Operating Environment (please complete the following information):
- Application Inspector Version: ApplicationInspector.CLI 1.5.20+3790d0a4cb
- OS: WSL 2 on Windows 10 [version 10.0.19044.1826].
- .NET version: 6.0.302
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
WSL2 (Preview) cannot run .exe files: exec format error: ...
it was possible to run Windows binaries from within WSL2 by simply having them in PATH and typing binary.exe with systemd enabled and...
Read more >Troubleshooting Windows Subsystem for Linux
Provides detailed information about common errors and issues people run into while running Linux on the Windows Subsystem for Linux.
Read more >ECONNREFUSED error with WSL 2 with Chrome ...
It is a bug of vscode. This issue can be fixed by replacing extensions 'JavaScript Debugger' with 'JavaScript Debugger (Nightly)'.
Read more >How to Install WSL 2 on Windows 10 (Updated)
Install a Linux distro. I walk through each step in turn below. I recommend using the PowerShell app, which you need to run...
Read more >Using WSL 2 in Enterprises
First, you have to clone the repository. The repository contains the C++ reference implementation for a Windows Subsystem for Linux (WSL) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There are a few options you can try as a workaround in the meantime:
I tried on the Linux system and found that there is no error on it. I think maybe this issue is caused by the WSL 2. So try not to use WSL to run SAST tool···