Secrets for containerEnv

[g-kartik]

Currently the --secrets-file sets the secret environment variables as remoteEnv which are only accessible by the vscode server process. A support for setting secrets as containerEnv shall ensure that all the running processes inside the devcontainer can access them.

At present, if I want to pass secrets at runtime I would have to pass them in containerEnv in devcontainer.json file, which is insecure as they are committed to the git repository. As a workaround, I make a docker compose file and pass the env_file there and use it for spinning up the devcontainer.

[samruddhikhandale]

I wonder if it's very similar to the ask in https://github.com/orgs/devcontainers/discussions/119.

From https://github.com/orgs/devcontainers/discussions/119#discussioncomment-8761462

Not sure if a static env file would cover your case, but there is a feature request for supporting .env files: microsoft/vscode-remote-release#3007.

[g-kartik]

Yes it is similar to microsoft/vscode-remote-release#3007