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
Choose the node --inspect-brk process and you'll see:
With the following command it works (I assume here that you're running under UID 1000):
$ docker run --rm -itv "$PWD/a.js:/a.js" -p 9229:9229 alpine:3.19 \
sh -euxc 'apk add nodejs shadow && useradd a \
&& su a -c "node --inspect-brk=0.0.0.0 a.js"'
Is it really needed to have access to the process? Chromium DevTools for one doesn't need that. Then the following is rather out of scope, but what about remote debugging?..
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.0. Please try upgrading to the latest version and checking whether this issue remains.
connor4312
added
debug
Debug viewlet, configurations, breakpoints, adapter issues
bug
Issue identified by VS Code Team member as probable bug
labels
Mar 4, 2024
connor4312
added a commit
to microsoft/vscode-js-debug
that referenced
this issue
Apr 5, 2024
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
a.js
:debugger
node --inspect-brk
process and you'll see:With the following command it works (I assume here that you're running under UID 1000):
Is it really needed to have access to the process? Chromium DevTools for one doesn't need that. Then the following is rather out of scope, but what about remote debugging?..
The text was updated successfully, but these errors were encountered: