Brian Goff 00ec6102d9 Probe all drivers if volume driver not specified ... This fixes an issue where `docker run -v foo:/bar --volume-driver <remote driver>` -> daemon restart -> `docker run -v foo:/bar` would make a `local` volume after the restart instead of using the existing volume from the remote driver. Signed-off-by: Brian Goff <cpuguy83@gmail.com>		2016-02-10 20:43:15 -05:00
..
drivers	Fix volume driver API compatibility mode (a little)	2016-02-08 23:12:29 -05:00
local	Move responsibility of ls/inspect to volume driver	2016-01-05 16:28:38 -05:00
store	Probe all drivers if volume driver not specified	2016-02-10 20:43:15 -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	Probe all drivers if volume driver not specified	2016-02-10 20:43:15 -05:00
volume_unix.go	Probe all drivers if volume driver not specified	2016-02-10 20:43:15 -05:00
volume_windows.go	Merge pull request #17034 from rhvgoyal/volume-propagation	2015-12-15 12:14:41 -05:00