You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently trying to remote debug some code running in a docker container. I've rebuilt the container to install debugpy as well as launching the container with debugpy and exposing both web (8080) and debug (5678) ports to the host. When trying to start the debug, I just get a pop-up window that just opens up the dialog prompting be to open launch.json. I would expect it to try and attach to the process via port 5678 to debug. No apparent errors are logged, even when log detail is set to TRACE.
I am using a Workspace in VS Code that has 4 different sub projects that are located in different places on the drive. The launch.json is located within one of the sub-projects and not globally at the workspace. I've tried this same config in both places, same result. I've also tried created a config without a workspace with unchanged behavior.
Magically... nothing changes and it just starts working.... then a reboot... and it stops working again. It's unclear what's going on. I suspect the debugger is having problems connecting to the debugger ports on the remote server and is just silently failing with no apparent error.
I'm currently trying to remote debug some code running in a docker container. I've rebuilt the container to install
debugpy
as well as launching the container with debugpy and exposing both web (8080) and debug (5678) ports to the host. When trying to start the debug, I just get a pop-up window that just opens up the dialog prompting be to openlaunch.json
. I would expect it to try and attach to the process via port 5678 to debug. No apparent errors are logged, even when log detail is set to TRACE.This issue seems very similar to #564
Here's the details:
VS Code Version info:
Here's my hardware and os:

I am using a Workspace in VS Code that has 4 different sub projects that are located in different places on the drive. The
launch.json
is located within one of the sub-projects and not globally at the workspace. I've tried this same config in both places, same result. I've also tried created a config without a workspace with unchanged behavior.Here's the
launch.json
config:Logs set to
Trace
. Here is the output of the logs once I click the button to initiate debugging...Other things I've done is grant VS Code full disk access, which shouldn't be the issue, however changing this configuration does nothing.
To prove ports are exposed, here's
docker ps
:And here's the command that is used inside the container to start the process for debugging process:
The text was updated successfully, but these errors were encountered: