Reject building new images named "scratch"
Open
Nobody has claimed this yet.
kind/feature
status/0-triage
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
Docker should not allow images to be named scratch, as that may lead to accidents.
Docker (and Kubernetes) should warn when interacting with images that spoof the stock scratch image.
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 names no files or tests. Start by locating Docker CLI entry points for building images and interacting with them, then determine how names matching scratch are handled. Done means new images named scratch are rejected and interactions with spoofed stock images produce warnings, with tests covering both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100