Explicitly expose content store gRPC service
Open
Nobody has claimed this yet.
area/daemon
- Dominant language
- Go
- Stars
- 72.1k
- Forks
- 19.2k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 164
Description
- Related to https://github.com/moby/moby/issues/44369
Currently it's "accidentally" exposed through Buildkit code.
We should make sure that it's exposed intentionally through moby.
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 reading related issue #44369 and the discussion on pull request #50744, then trace how the content store gRPC service is currently exposed through BuildKit. Done means the service is exposed intentionally through Moby rather than accidentally through BuildKit; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100