nooooooooo! there are 3 different ways that VOLUMEs get created or linked up. firstly, when the instruction is encountered, a new filesystem is created and used for the remainder of the build. If you just run the image, that created volume is used. (1a you can do ``docker run -v /data image`` which will make a new volume for that container) Secondly, you can use a data-container that does 1a, and then link it to your run using --volumes-from. Thirdly, and least sustainably, is the -v /local:/container mounting.