dockerfile: whitelist configuration for `# syntax =` frontend
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 50
Description
Supporting whitelist configuration for # syntax = frontend would be useful for preventing malicious frontends from being specified due to e.g. typo.
The whitelist could be specified either via static buildkitd.toml or dynamic CRUD object.
whitelist types
- image reference prefix
- image digest
- notary signer key
...
dynamic CRUD object
For a while bbolt could be used, but in long-term, we might want to use distributed store like etcd for supporting multi-master distributed mode.
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
The issue points to static buildkitd.toml configuration and a dynamic CRUD object; start by locating how Dockerfile # syntax frontends are handled. Compare the proposed whitelist forms—image prefixes, image digests, and Notary signer keys—and the bbolt or distributed-store options before defining scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100