Tecnativa / Tecnativa/docker-socket-proxy
Add example non-default env variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
It would be useful to me to see an example of one way the proxy could be configured with env variables.
My understanding is that to explicitly grant the proxy access to SECRETS, I would add the line -e SECRETS=1 to the Docker run command, or - SECRETS=1 to the environment block of my docker-compose.yml.
The system is pretty simple and intuitive, but I think basic security practices like this should be as approachable and accessible as possible.
An example docker-compose.yml file would also be useful, perhaps with commented modification env variables.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the Docker run command and the requested docker-compose.yml example. Add an example showing one non-default environment variable in both forms, with commented environment-variable options; done means users can understand how to configure the proxy without guessing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100