Inconsistent directory permissions for ~/.docker directory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Opening as a tracking issue, following the discussion on https://github.com/moby/buildkit/pull/1660#discussion_r487596550, which highlighted that depending on which path in the code is taken, permissions on the ~/.docker may be either 0700 or 0755;
The second example was added later, so should probably be updated to match the former, although less restrictive permissions would likely not be a problem in most cases as this directory (in the default case) will be inside the user's home directory, which should already be inaccessible for other users.
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
Start by comparing the directory creation paths in cli/config/configfile/file.go and cli/context/store/metadatastore.go at the linked locations. Confirm the differing permissions and make both paths consistent, then run the relevant Docker CLI tests to verify directory creation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100