Expose declared VOLUME / default container data path in CLI
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start by locating the Docker CLI output or inspection path that reports image metadata, then compare it with the Dockerfile VOLUME declaration and the docker inspect JSON output mentioned here. Done means images declaring VOLUME expose the default container data path clearly in the CLI, while images without VOLUME produce no additional output.
Written by the indexing model from the issue text.
Description
Description
Overall, my recent experience with Docker has been really positive.
Compared to manually copying projects, managing plugins, and configuring environments, Docker feels refreshingly simple—spin up with one command, clean up with another.
It’s certainly much more comfortable than traditional deployment, though there are still a few rough edges that feel unnecessarily awkward.
The Dockerfile already declares VOLUME, and the official docs mention the default data directory.
Yet, figuring out which directory the container actually expectsstill requires parsing docker inspectJSON output or digging through documentation—this isn’t very elegant.
Most mature software (nginx, mysql, redis, even systemd) follows a simple rule:
‘Here’s the default. Use it, or override it if you want.’
Docker does the opposite: it hints that a default exists, but refuses to show it clearly.
What I’m asking for is very simple:
Image has a VOLUME→ tell me
No VOLUME→ quietly skip
This is probably about three lines of Go code in the CLI. 😏
If a default exists, the CLI should expose it as a first‑class citizen—not force users to play detective.”
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
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.
More from docker/cli
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
kind/feature status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Similar issues
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100