Parameters are available in an inconsistent way (e.g. human, no-trunc)
Open
Nobody has claimed this yet.
area/ux
kind/enhancement
kind/feature
status/0-triage
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
Trying to automate information manipulation using docker cli is complicate as parameters such as human=false or no-trunc are not available consistently.
To give some examples:
- image history
- image inspect
- image ls
- system df
- human=false is available on 1 but not 2, 3 and 4, forcing to parse a formatted value
- no-trunc is required to have complete ID's in 1 and 3 while not needed in 2 and 4
In addition UniqueSize reported by 4 is often 0 as shown in the excerpt below (the first value after "image" is supposed to be the UniqueSize).
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
Compare the parameter and output behavior of image history, image inspect, image ls, and system df, focusing on human, no-trunc, and UniqueSize. Start by tracing the Docker CLI entry points for these commands and their existing tests, then define completion as consistent parameter availability and correct UniqueSize reporting across the listed commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100