Vscode-js-debug: Unable to launch Chrome when working with a remote container

[nsgundy]

Describe the bug
When trying to launch Chrome using pwa-chrome while attached to a remote container, the extension is unable to launch Chrome and I get to see this:

To Reproduce
Steps to reproduce the behavior:

1. Launch a workspace in a remote container
2. Launch the following default launch config:

    {
        "name": "Launch Chrome",
        "request": "launch",
        "type": "pwa-chrome",
        "url": "http://localhost:3000",
        "webRoot": "${workspaceFolder}"
    }

I have tried this as part of a .code-workspace as well as launch.json, neither work.

Log File
vscode-debugadapter-2ff4ba31.json.gz

VS Code Version: 1.52.1
JavaScript Debugger (Nightly) Version: v2021.1.817
JavaScript Debugger Companion Extension Version: v1.0.8
Remote -Containers Version: v0.154.2

Additional context
OS: Ubuntu 20.10
When opening the same workspace locally, launching Chrome works just fine. I have attempted to do this both with and without the nightly version.

The example given is quite bare on purpose. Normally I would have it execute a pre-launch task that spins up a webpack dev-server. The environment is supposed to be able to run on Linux, Windows and Mac and requires a specific version of nodejs, hence the use of a container.

[connor4312]

Does it work if you manually specify the chrome path using the runtimeExecutable property?

[nsgundy]

Does it work if you manually specify the chrome path using the runtimeExecutable property?

I have tried by adding "runtimeExecutable": "/usr/bin/google-chrome" to the launch config. The only difference is that the Unable to attach to browser message appears right away (before it would take a couple of seconds).

Log File
vscode-debugadapter-619129f0.json.gz

[nsgundy]

@connor4312 Sorry to bug you, just wondering if there is anything else for me to try?

[nsgundy]

I have re-tested this with VS Code Version 1.53.2 and JavaScript Debugger 1.53.0. Its still a problem for me.

[nsgundy]

Hey, just tested this on Windows today and there the same thing works as expected(same Docker container, same versions of VS Code and extensions as above). So Ubuntu (or Linux) only it seems.

[tomatac]

I'am having the same issue in Ubuntu 20.04

[kalebpace]

I've been having the same issue on Archlinux 5.10.16.

Granted this doesn't solve the issue with js-debug itself, but hopefully this will help anyone re-enable launch-to-debug until this is fixed.

My current work around:

• Disable js-debug with: debug.javascript.usePreview: false
• Reinstall the old _Debugger for Chrome_ (msjsdiag.debugger-for-chrome) extension
• In launch.json set "type": "chrome" to enable launching with the legacy extension above

My launch.json:

{
    "name": "Launch Chromium Debug (Legacy)",
    "request": "launch",
    "type": "chrome",
    "url": "http://localhost:8080/",
    "webRoot": "${workspaceFolder}",
    "runtimeExecutable": "/usr/bin/chromium"
}

[connor4312]

The fix will be available on Insiders tomorrow, and in stable early next month.

[alexr00]

Verified on Ubuntu with

    {
        "name": "Launch Chrome",
        "request": "launch",
        "type": "pwa-chrome",
        "url": "http://localhost:3000",
        "webRoot": "${workspaceFolder}"
    }

[tomatac]

It looks like this is fixed! Thanks!
One note. Having an incorrect setting to:
"webRoot": "${workspaceFolder}/app/src"
generates the same error.
It would be nice to tell that the path does not exist.

[tomatac]

It looks like this error is back for me. How can I troubleshoot this issue?