DevContainers: Fails to open folder using DevContainers

[vrv7567]

• VSCode Version: 1.78.0

• Local OS Version: Windows_NT x64 10.0.19042

• Remote OS Version: Ubuntu 22.04.2 LTS

• Remote Extension/Connection Type: Containers v0.292.0

• Logs:

2023-05-09 16:06:41.935 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-containers, startup: false, activationEvent: 'onStartupFinished'
2023-05-09 16:06:42.289 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
2023-05-09 16:08:16.280 [error] ProxyResolver#getCaCertificates error Error: Cannot find module 'vscode-windows-ca-certs'
Require stack:
- c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar\@vscode\proxy-agent\out\index.js
- c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js
- c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js
- 
	at Module._resolveFilename (node:internal/modules/cjs/loader:1010:15)
	at s._resolveFilename (node:electron/js2c/utility_init:2:2740)
	at Module._load (node:internal/modules/cjs/loader:858:27)
	at f._load (node:electron/js2c/asar_bundle:2:13330)
	at b._load (c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:126:29948)
	at h._load (c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:126:26698)
	at I._load (c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:90:24489)
	at Module.require (node:internal/modules/cjs/loader:1082:19)
	at g (c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:4:647)
	at c:\Users\dogma\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar\@vscode\proxy-agent\out\index.js:380:71
	at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-05-09 16:08:16.498 [error] Error: unable to get local issuer certificate
	at TLSSocket.onConnectSecure (node:_tls_wrap:1535:34)
	at TLSSocket.emit (node:events:513:28)
	at TLSSocket._finishInit (node:_tls_wrap:949:8)
	at ssl.onhandshakedone (node:_tls_wrap:730:12) remote-containers.openFolder {"value":"ms-vscode-remote.remote-containers","c":"ms-vscode-remote.remote-containers"}

Steps to Reproduce:

1. Connect to remote linux machine using vscode installed in windows workstation using remoteSSH extension
   Note: The remote linux machine is behind HTTP PROXY(Doesn't affect SSH Connection/No special configs required in config file of .ssh directory)
2. Open a folder in remote linux machine using DevContainers
3. The extension silently fails to open the folder with the above logs

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

[vrv7567]

Related issue: microsoft/vscode#181404

[vrv7567]

Workaround: Manually set the proxy field in vscode under remote settings:

[chrmarti]

Error: Cannot find module 'vscode-windows-ca-certs' is caught and logged and should not impact anything else. Error: unable to get local issuer certificate on the other hand would not go away by setting Http: Proxy I think. Are you setting Http: Proxy to the same proxy that would otherwise be used or is this some other (maybe local) proxy?

[vrv7567]

Are you setting Http: Proxy to the same proxy that would otherwise be used or is this some other (maybe local) proxy?

Yes I'm setting Http: Proxy to the same proxy that is also set as env_var http_proxy
There's no other local/special proxy involved here

[chrmarti]

Not sure why that changes the behavior. Will continue to track in microsoft/vscode#181404 which is considered for a VS Code 1.78.x recovery release.