Feature Request: `docker pull/push --calculate`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Currently there is no way to run a 'simulated' docker pull, and given the difference between layer hashes (used locally) and compressed layer hashes (used in the registries) it's not trivial to tell what the data cost will be to do a docker pull.
Please introduce a --calculate switch to the docker pull command to allow Docker to calculate the cost of a docker pull without actually doing one.
Similarly, a docker push --calculate would tell us how much data would be pushed to the registry without actually doing so, would be very useful for development when the user is bandwidth constrained.
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 with the Docker CLI entry points for the docker pull and docker push commands. Determine how each command identifies layer data and registry transfers, then define a calculation-only path that reports the data cost without performing the operation; done means both commands support --calculate with useful estimates.
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
- Mostly clear
- Newbie friendliness
- 35/100