Open Roemer opened 6 months ago
I now tried with setting the environment variable NODE_TLS_REJECT_UNAUTHORIZED
to 0
in Windows and that actually made it work. This is a workaround but I don't see any reason why it should not work when NODE_EXTRA_CA_CERTS
is set to a .pem file with all corporate certificates.
We have the an issue that just creating the dev-container configuration files locally (or when connected to the remote WSL2) does not work, It always immediately aborts with the error:
I do have the
NODE_EXTRA_CA_CERTS
set to our certificates on Windows but that seems not to help. The last version of the Dev Containers extension that this still works is 0.255.4 but everything newer (up to the pre-release 0.329.0) fails with the error mentioned above. I went thru all open issues related to similar issues but most of them are regarding issues with installing extensions on the remote / container which we don't have if we just add theNODE_EXTRA_CA_CERTS
and the certificates into the container as well. The only really matching issue is https://github.com/microsoft/vscode-remote-release/issues/8230 which is closed but it still does not work for us.Steps to Reproduce: