Skip to content
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

cap_net_bind_service and vscode debugger #138064

Closed
ghost opened this issue Nov 29, 2021 · 1 comment
Closed

cap_net_bind_service and vscode debugger #138064

ghost opened this issue Nov 29, 2021 · 1 comment
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@ghost
Copy link

ghost commented Nov 29, 2021

  • VS Code Version: (vscodium)
  • Version: 1.56.0
    Commit: cfa2e21
    Date: 2021-05-09T15:54:41.116Z
    Electron: 12.0.4
    Node.js: 14.16.0
    V8: 8.9.255.24-electron.0
    OS: Linux x64 5.11.0-38-generic snap
  • OS Version: ubuntu 20.04

when using this command to let me use port 80 without root
sudo setcap 'cap_net_bind_service=+ep' `which node`
will cause debugger and logs stop working

and when reset cap_net_bind_service
sudo setcap 'cap_net_bind_service=-ep' `which node`
everything work fine ..

not sure if this count as "bug" or not.. but showing warnings about "cap_net_bind_service" settings will help

@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Nov 29, 2021
@weinand weinand removed their assignment Nov 29, 2021
@connor4312
Copy link
Member

See nodejs/node#37588

Duplicates microsoft/vscode-js-debug#852

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 29, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jan 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants