{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Melony? 的问题《How do you list volumes in docker containers?》','https://www.manongdao.com/q-37057.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
When using docker images from registries, I often need to see the volumes created by the image's containers.
Note: I'm using docker version 1.3.2 on Red Hat 7.
Example
The postgres official image from the Docker Registry has a volume configured for containers at /var/lib/postgresql/data.
What's the most succinct command to show the volume at /var/lib/postgresql/data in a postgres container?
With docker 1.10, you now have new commands for data-volume containers.
(for regular containers, see the next section, for docker 1.8+):
docker volume lsdocker volume inspectWith docker 1.8.1 (August 2015), a
docker inspect -f '{{ .Volumes }}' containeridwould be empty!You now need to check
Mounts, which is a list of mounted paths like:If you want the path of the first mount (for instance), that would be (using index 0):
As Mike Mitterer comments below:
Or, as commented by Mitja, use the
jqcommand.Show names and mount point destinations of volumes used by a container:
This is compatible with Docker 1.13.
Use
docker psto get the container id.Then
docker inspect -f '{{ .Mounts }}' containeridExample:
terminal 1
terminal 2
The output
is, apparently, due to the use of the Go language to implement the docker command tools.
The
docker inspectcommand without the-f formatis quite verbose. Since it is JSON you could pipe it to python or nodejs and extract whatever you needed.docker history <image name>will show the layers baked into an image. Unfortunately,docker historyseems hobbled by its formatting and lack of options to choose what is displayed.You can choose terse and verbose formats, via the --no-trunc flag.
Here's a verbose example.
if you want to list all the containers name with the relevant volumes that attached to each container you can try this:
example output:
/opt_rundeck_1 - container name
[..] - volumes attached to the conatiner
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, theVolumesandVolumesRWfields give you information about ALL of the volumes mounted inside a container, including volumes mounted in both the Dockerfile with theVOLUMEdirective, and on the command line with thedocker run -vcommand. However, you can isolate which volumes were mounted in the container using thedocker run -vcommand by checking for theHostConfig.Bindsfield in thedocker inspectJSON output. To clarify, thisHostConfig.Bindsfield tells you which volumes were mounted specifically in yourdocker runcommand with the-voption. So if you cross-reference this field with theVolumesfield, you will be able to determine which volumes were baked into the container usingVOLUMEdirectives in the Dockerfile.A grep could accomplish this like:
And...
And in my example, you can see I've mounted
/var/docker/docker-registry/configinto the container as/registryusing the-voption in mydocker runcommand, and I've mounted the/dataand/configvolumes using theVOLUMEdirective 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 theHostConfigJSON output of yourdocker inspectcommand.