Debugging in a Docker container (UI Mode): Unable to find Chrome version stable

Describe the bug

Chrome debugger refuses to launch inside of mcr.microsoft.com/dotnet/core/sdk:3.1 container (ui mode) after latest update. Produces error:

Setting runtimeExecutable to dev as idicated produces the same error, except saying it couldn’t find version dev

This doesn’t seem to be a totally new issue, but it only started happening after the latest update (see https://github.com/microsoft/vscode-js-debug/issues/212). I’d be okay with a workaround for now, but since this is running in a container, I’m not sure what I should set the runtimeExecutable setting to…

To Reproduce Steps to reproduce the behavior:

1. use VSCode to build a .net core 3.1 dev container (specific container probably isn’t relavent)
2. create a launch config:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch Chrome",
            "url": "http://localhost:5000/Leaderboards/Recents",
            "webRoot": "${workspaceFolder}/wwwroot",
			"runtimeArgs": [
				"--auto-open-devtools-for-tabs"
			],
            "sourceMapPathOverrides": {
                "webpack:///*": "${workspaceFolder}/../ClientApp/*"
            }
        }
   ]
}

1. try to launch the config

Log File vscode-debugadapter-0.json.gz

VS Code Version: Version: 1.47.0 (user setup) Commit: d5e9aa0227e057a60c82568bf31c04730dc15dcd Date: 2020-07-09T08:02:06.629Z Electron: 7.3.2 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18362

[thomasrea0113]

The fix for this is to set your launch type to pwa-chrome instead of chrome. With just chrome, the config gets resolved using the old extension which is missing some bits. Let me know if that works for you.

This’ll be fixed when the redirection is removed, for now I’ll also add an extra default check when the config gets to the new debugger.

Awesome, this worked. You guys are the reason I love VS Code! keep up the good work.

[connor4312]

The fix for this is to set your launch type to pwa-chrome instead of chrome. With just chrome, the config gets resolved using the old extension which is missing some bits. Let me know if that works for you.

This’ll be fixed when the redirection is removed, for now I’ll also add an extra default check when the config gets to the new debugger.