FR: Read /etc/docker/config.json in addition to ~/.docker/config.json
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
As a sysadmin, I would like to set some options globally for all users.
So it would be good, if the logic reading ~/.docker/config.json would also read /etc/docker/config.json and merge the results.
When it comes to precedences, I think, the user's config should override the system config.
My major use case are proxies (see #93). Asking every user to configure them by hand is not optimal.
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.
Research direction
Locate the Docker CLI logic that reads ~/.docker/config.json and trace how its options are represented and merged. Add support for /etc/docker/config.json, with the user's configuration taking precedence over the system configuration. Done means global options such as proxies work for all users while user-specific values override them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100