Environment variables missing when connecting through SSH

[chrmarti]

@chrmarti That was a very good idea. I do see a lot of differences between the printenv from the initialize command and from the SSH shell in VSCode before launching the container. Most notably, the HTTP_PROXY/HTTPS_PROXY variables are missing.

Now these variables get set in /etc/profile.d/<some_script>.sh which should normally get sourced automatically for every new shell, but don't seem to get sourced in this case. Is my understanding wrong and this is the correct behaviour, or should it in fact source these files first?

If I set these vars in the command explicitly, the login works:

"initializeCommand": "http_proxy='http://127.0.0.1:3128' https_proxy='http://127.0.0.1:3128' HTTPS_PROXY='http://127.0.0.1:3128/' HTTP_PROXY='http://127.0.0.1:3128/' ... az acr login -n <OurRegistryName>",

Originally posted by @cbandera in #2994 (comment)

[cbandera]

@chrmarti Was this fixed? I can still reproduce the issue with the latest version

[cbandera]

This is fixed for me now with the latest release. Thanks again!

[rzhao271]

Marking as verified based on #5976 (comment)