167

I'm trying to go deeper in my understanding of Docker's volume, and I'm having an hard time to figure out the differences / use-case of:

  • The docker volume create command
  • The docker run -v /path:/host_path
  • The VOLUME entry in the Dockerfile file

I particularly don't understand what happens if you combine the VOLUME entry with the -v flag.

Koray Tugay
  • 22,894
  • 45
  • 188
  • 319
radium226
  • 1,993
  • 2
  • 12
  • 10

4 Answers4

110

A volume is a persistent data stored in /var/lib/docker/volumes/...

  • You can either declare it in a Dockerfile, which means each time a container is started from the image, the volume is created (empty), even if you don't have any -v option.

  • You can declare it on runtime docker run -v [host-dir:]container-dir.
    combining the two (VOLUME + docker run -v) means that you can mount the content of a host folder into your volume persisted by the container in /var/lib/docker/volumes/...

  • docker volume create creates a volume without having to define a Dockerfile and build an image and run a container. It is used to quickly allow other containers to mount said volume.

If you had persisted some content in a volume, but since then deleted the container (which by default does not deleted its associated volume, unless you are using docker rm -v), you can re-attach said volume to a new container (declaring the same volume).

See "Docker - How to access a volume not attached to a container?".
With docker volume create, this is easy to reattached a named volume to a container.

docker volume create --name aname
docker run -v aname:/apath --name acontainer
...
# modify data in /apath
...
docker rm acontainer

# let's mount aname volume again
docker run -v aname:/apath --name acontainer
ls /apath
# you find your data back!
gravetii
  • 9,273
  • 9
  • 56
  • 75
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • 7
    Let's say you use a `Dockerfile` with `VOLUME` and the `-v /path:/host_path/` flag. The content of the `VOLUME` will be overrided by the the content of `/host_path/`? – radium226 Jan 15 '16 at 13:06
  • Thanks to you @VonC, I think I get it :) And if you do a `docker volume create --name my_volume` followed by a `docker run --volume-from my_volume`, how do you know where the mountpoint will be? – radium226 Jan 15 '16 at 13:09
  • @radium226 no mount point (meaning nothing mounted from the host, beside the native empty /var/lib/docker/volume). The path of the volume is in the my_volume metadata: http://stackoverflow.com/a/31997267/6309 – VonC Jan 15 '16 at 13:15
  • I understand that there is no mountpoint on the host side. But within the running container lauched with `docker run ...`, how can I write into a file stored on the `my_volume` volume? I do not know the... path? of the volume inside my running container because I defined nothing? I hope I'm clear enough, because I'm definitely not sure of my vocable :-/ – radium226 Jan 15 '16 at 13:28
  • 1
    @radium226 the `docker volume create --name aname` creates a *named* volume: You assign a *container* path on runtime: `docker run -v aname:/apath`: that container now has a volume attached to it, mounted to its /apath folder. I have rewritten the answer to make that clear. – VonC Jan 15 '16 at 14:38
  • If you want to use standalone volumes `docker volume create ...` but still want them to persist on the host, you can use a plugin such as: https://github.com/cwspear/local-persist (disclaimer: that's my repo) – CWSpear Feb 10 '16 at 02:15
  • You do not need the `VOLUME` in Dockerfile for `docker run -v`. – Koray Tugay Oct 05 '19 at 12:19
26

VOLUME instruction becomes interesting when you combine it with volumes-from runtime parameter.

Given the following Dockerfile:

FROM busybox
VOLUME /myvolume

Build an image with:

docker build -t my-busybox .

And spin up a container with:

docker run --rm -it --name my-busybox-1 my-busybox

The first thing to notice is you will have a folder in this image named myvolume. But it is not particularly interesting since when we exit the container the volume will be removed as well.

Create an empty file in this folder, so run the following in the container:

cd myvolume
touch hello.txt

Now spin up a new container, but share the same volume with my-busybox-1:

docker run --rm -it --volumes-from my-busybox-1 --name my-busybox-2 my-busybox

You will see that my-busybox-2 contains the file hello.txt in myvolume folder.

Once you exit both containers, the volume will be removed as well.

Koray Tugay
  • 22,894
  • 45
  • 188
  • 319
  • 8
    The volumes will be deleted because they are **anonymous volumes** AND you started the containers with the `--rm` option. I think it might works mentioning it. If you didn't start a container with `--rm`, you can still remove container and its *anonymous volumes* with `docker rm -v my-container`. – AymDev Jan 12 '20 at 11:38
6

@radium226

  1. Specifying VOLUME in Dockerfile makes sure the folder is to be treated as a volume(i.e., outside container) at runtime, as opposed to be a regular directory inside the container. Note the performance and accessibility implications.
  2. If having forgot to specify "-v" in "docker run" command line, the above is still true. It's just the volume name becomes anonymous. But there are still ways to access or recover data from such anonymous volumes.
M2014
  • 1,094
  • 1
  • 9
  • 16
1

Using MYSQL from docker hub:

Running the below command as an example:

$ docker run --name some-mysql -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag

The -v /my/own/datadir:/var/lib/mysql part of the command mounts the /my/own/datadir directory from the underlying host system as /var/lib/mysql inside the container, where MySQL by default will write its data files.

Therefore, a directory that persists when the container is killed is mounted is available that also provided higher performance for some operations like databases actions.

Afshin Ghazi
  • 2,784
  • 4
  • 23
  • 37
  • In addition to your example, this shows how flexible volumes are. Author of an image simply tells what should live outside the container by using `VOLUME`, and a user can: do nothing and let Docker create an anonymous volume, or tell Docker to mount it to physical location on a disk, or mount it to some pre-defined Docker volume. That's awesome, because author of the image doesn't know where users want to keep their data. Besides, when you forget to mount the volume, do some work, and kill the container, there's no "oops, data lost", because it can be retrieved from the anonymous volume. – itachi Mar 23 '23 at 19:58