microsoft / microsoft/vscode-remote-release
Start dev containers with secure logs
Open
@chrmarti is already working on this.
Since Feb 28, 2022.
bug
containers
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Currently starting a dev container appears to start a container (optionally with env vars or an env file set), then reads all of the env vars and re-applies them in a final docker exec (so that additional env vars can be injected)?
For common dev workflows that use .env files or similar, this spills secrets into the dev container build log.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.