Expose declared VOLUME / default container data path in CLI

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.”

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.