-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to launch Chrome when working with a remote container #908
Comments
Does it work if you manually specify the chrome path using the |
I have tried by adding Log File |
@connor4312 Sorry to bug you, just wondering if there is anything else for me to try? |
I have re-tested this with VS Code Version 1.53.2 and JavaScript Debugger 1.53.0. Its still a problem for me. |
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. |
I'am having the same issue in Ubuntu 20.04 |
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:
My
|
The fix will be available on Insiders tomorrow, and in stable early next month. |
Verified on Ubuntu with
|
It looks like this is fixed! Thanks! |
I'm running into the same issue on Ubuntu 20.04.2 using:
|
Where is your chrome executable located? |
|
I did something similar to @alexr00. Here is my launch configuration:
This works for me on Ubuntu 20.04 |
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:
I have tried this as part of a
.code-workspace
as well aslaunch.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.
The text was updated successfully, but these errors were encountered: