Brian Goff dd7d1c8a02 On container rm, don't remove named mountpoints ... This makes it so when calling `docker run --rm`, or `docker rm -v`, only volumes specified without a name, e.g. `docker run -v /foo` instead of `docker run -v awesome:/foo` are removed. Note that all volumes are named, some are named by the user, some get a generated name. This is specifically about how the volume was specified on `run`, assuming that if the user specified it with a name they expect it to persist after the container is cleaned up. Signed-off-by: Brian Goff <cpuguy83@gmail.com>		2016-01-25 15:51:28 -05:00
..
drivers	Use fine-grained locks for plugin loading.	2016-01-20 13:57:52 -05:00
local	Move responsibility of ls/inspect to volume driver	2016-01-05 16:28:38 -05:00
store	On create, copy image data for named volumes.	2016-01-07 21:57:08 -05:00
testutils	Move responsibility of ls/inspect to volume driver	2016-01-05 16:28:38 -05:00
volume.go	On container rm, don't remove named mountpoints	2016-01-25 15:51:28 -05:00
volume_propagation_linux.go	Add capability to specify mount propagation per volume	2015-12-14 10:39:53 -05:00
volume_propagation_linux_test.go	Add some unit and integration tests	2015-12-14 10:39:53 -05:00
volume_propagation_unsupported.go	Add capability to specify mount propagation per volume	2015-12-14 10:39:53 -05:00
volume_test.go	Move volume.SplitN() to the one place it is used in runconfig.	2016-01-04 12:06:30 -05:00
volume_unix.go	Fix downstream client API build errors on Solaris	2015-12-30 18:25:42 -05:00
volume_windows.go	Merge pull request #17034 from rhvgoyal/volume-propagation	2015-12-15 12:14:41 -05:00