Unable to launch Chrome when working with a remote container

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]

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

[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.