doesn't work under custom devcontainer

[icegood]

Environment

• OS and Version: docker
  Linux ice-home 6.14.0-15-generic Find all references (Experimental Version) #15-Ubuntu SMP PREEMPT_DYNAMIC Sun Apr 6 15:05:05 UTC 2025 x86_64
  x86_64 x86_64 GNU/Linux
  under root

• VS Code Version:
  -Version: 1.100.2
  Commit: 848b80aeb52026648a8ff9f7c45a9b0a80641e2e
  Date: 2025-05-14T21:47:40.416Z
  Electron: 34.5.1
  ElectronBuildId: 11369351
  Chromium: 132.0.6834.210
  Node.js: 20.19.0
  V8: 13.2.152.41-electron.0
  OS: Linux x64 6.14.0-15-generic

• C/C++ Extension Version: 1.26.1

• If using SSH remote, specify OS of remote machine:
  rooted container

Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

1. prepare own cotainer. Run it as root
2. install extension under devcontainer
3. try use (say, goto definition of function)

Expected behavior:
works

Configuration and Logs

2025-05-25 08:17:40.416 [info] Extension host with pid 852 started
2025-05-25 08:17:40.418 [info] Lock '/root/.vscode-server/data/User/workspaceStorage/8030c29de55fbb539249111912790f17/vscode.lock': Lock acquired.
2025-05-25 08:17:40.535 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-05-25 08:17:40.536 [info] ExtensionService#_doActivateExtension KylinIdeTeam.cppdebug, startup: false, activationEvent: 'onLanguage:c'
2025-05-25 08:17:40.536 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: false, activationEvent: 'onLanguage:c'
2025-05-25 08:17:40.769 [info] ExtensionService#_doActivateExtension vscode.configuration-editing, startup: false, activationEvent: 'onLanguage:jsonc'
2025-05-25 08:17:40.770 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2025-05-25 08:17:40.770 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2025-05-25 08:17:40.944 [error] Activating extension ms-vscode.cpptools failed due to an error:
2025-05-25 08:17:40.944 [error] Error: command 'extension.pickNativeProcess' already exists
	at Wb.registerCommand (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:119:40218)
	at Object.registerCommand (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:170:30271)
	at Object.initialize (/root/.vscode-server/extensions/ms-vscode.cpptools-1.26.1-linux-x64/dist/src/main.js:12155:38)
	at activate (/root/.vscode-server/extensions/ms-vscode.cpptools-1.26.1-linux-x64/dist/src/main.js:116856:29)
	at ly.kb (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:123:15268)
	at ly.jb (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:123:14975)
	at file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:123:13133
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async Nb.n (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:119:13382)
	at async Nb.m (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:119:13345)
	at async Nb.l (file:///vscode/vscode-server/bin/linux-x64/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/out/vs/workbench/api/node/extensionHostProcess.js:119:12801)
2025-05-25 08:17:40.944 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2025-05-25 08:17:40.974 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2025-05-25 08:17:40.974 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-05-25 08:17:41.377 [info] Eager extensions activated
2025-05-25 08:17:41.377 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-05-25 08:17:41.377 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2025-05-25 08:17:41.612 [warning] [Decorations] CAPPING events from decorations provider vscode.git 4682
2025-05-25 08:17:42.224 [warning] [Decorations] CAPPING events from decorations provider vscode.git 4682
2025-05-25 08:32:50.016 [warning] [Decorations] CAPPING events from decorations provider vscode.git 4683
2025-05-25 08:32:55.114 [warning] [Decorations] CAPPING events from decorations provider vscode.git 4683

====
no option to select 'cpptools' logs

Other Extensions

doesn't matter. could disable all of them

Additional context

No response

[sean-mcmanus]

@icegood Your logging indicates our C/C++ extension fails to activate due to Error: command 'extension.pickNativeProcess' already exists -- do you know what could be causing that? Is that command being registered by another extension? Is someone calling our extension's activate() more than once? If so, I have a PR at #13643 that could fix that case. Are you able to repro the issue when debugging our extension's TypeScript? If so, you could try out the change in that PR to see if your issue is fixed or not. The code that is doing the register is at https://github.com/microsoft/vscode-cpptools/blob/main/Extension/src/Debugger/extension.ts#L38 .

[Colengms]

This appears to be a conflict with the extension KylinIdeTeam.cppdebug, which also registers extension.pickNativeProcess.

[sean-mcmanus]

We (or an external contributor) could potentially add a setting that switches the command we use to cpptools.pickNativeProcess for use when another extension has the conflicting name.