VS2017 Remote Debug Attach not working with WSL

[jakubsuchybio]

• Your Windows build number: (Type ver at a Windows Command Prompt)
  Microsoft Windows [Version 10.0.16299.192]

• What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
  When I want to attach to WSL dotnet exec instance of my app, it gives me error (see the gif) and img:
  
  

• What's wrong / what should be happening instead:
  I would expect it to attach to my linux process

• Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here)
  Dunno what to strace. dotnet run? that vssomething.sh script? or nothing?

[jakubsuchybio]

Damn nevermind... I looked into output where was command
/home/biosek/.vs-debugger/GetVsDbg.sh -v vs2017u5 -l "/home/biosek/.vs-debugger/vs2017u5

I ran it inside WSL and got:

Using arguments
    Version                    : 'vs2017u5'
    Location                   : '/home/biosek/.vs-debugger/vs2017u5'
    SkipDownloads              : 'false'
    LaunchVsDbgAfter           : 'false'
    RemoveExistingOnUpgrade    : 'false'
Info: Using vsdbg version '15.1.11011.1'
Info: Previous installation at /home/biosek/.vs-debugger/vs2017u5 not found
Info: Using Runtime ID 'linux-x64'
Downloading https://vsdebugger.azureedge.net/vsdbg-15-1-11011-1/vsdbg-linux-x64.zip
unzip command not found. Install unzip for this script to work.

So the freaking unzip was missing...

[pieandcakes]

@jakubsuchybio that error should also be in your output window. I'm looking into making it a bit more visible there so you don't have to go run it. The original pop-up error you get should redirect you to the output window also.

[jakubsuchybio]

Yeah, the messagebox navigates me to the output window, but there is only that command:
/home/biosek/.vs-debugger/GetVsDbg.sh -v vs2017u5 -l "/home/biosek/.vs-debugger/vs2017u5
would be nice if there was output of that command as well, so I don't need to run it manually as you say.
Sorry if my explanation wasn't clear enough :)