You can get information about which volumes were specifically baked into the container by inspecting the container and looking in the JSON output and comparing a couple of the fields. When you run docker inspect myContainer
, the Volumes
and VolumesRW
fields give you information about ALL of the volumes mounted inside a container, including volumes mounted in both the Dockerfile with the VOLUME
directive, and on the command line with the docker run -v
command. However, you can isolate which volumes were mounted in the container using the docker run -v
command by checking for the HostConfig.Binds
field in the docker inspect
JSON output. To clarify, this HostConfig.Binds
field tells you which volumes were mounted specifically in your docker run
command with the -v
option. So if you cross-reference this field with the Volumes
field, you will be able to determine which volumes were baked into the container using VOLUME
directives in the Dockerfile.
A grep could accomplish this like:
$ docker inspect myContainer | grep -C2 Binds
...
"HostConfig": {
"Binds": [
"/var/docker/docker-registry/config:/registry"
],
And...
$ docker inspect myContainer | grep -C3 -e "Volumes\":"
...
"Volumes": {
"/data": "/var/lib/docker...",
"/config": "/var/lib/docker...",
"/registry": "/var/docker/docker-registry/config"
And in my example, you can see I've mounted /var/docker/docker-registry/config
into the container as /registry
using the -v
option in my docker run
command, and I've mounted the /data
and /config
volumes using the VOLUME
directive in my Dockerfile. The container does not need to be running to get this information, but it needs to have been run at least one time in order to populate the HostConfig
JSON output of your docker inspect
command.