[Proposal] docker pull return code
Open
Nobody has claimed this yet.
area/distribution
kind/enhancement
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
This is a follow up to https://github.com/moby/moby/issues/27658
//cc @neilhwatson @KristofErr @DenerKup @gregmartyn
It seems like docker pull returning different exit codes would be helpful for automating failures.
For example, to distinguish between image name doesn't exist and registry is wrong.
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 the linked issue 27658 and the Docker CLI's existing docker pull behavior. Determine the desired distinction between a missing image name and an incorrect registry, then identify the relevant command and tests before proposing exit-code coverage and verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100