Brian Goff d0165c4085 Fix panic when plugin responds with null volume ... In cases where the a plugin responds with both a null or empty volume and a null or empty Err, the daemon would panic. This is because we assumed the idiom if `err` is nil, then `v` must not be but in reality the plugin may return whatever it wants and we want to make sure it doesn't harm the daemon. Signed-off-by: Brian Goff <cpuguy83@gmail.com> (cherry picked from commit 96c79a1934)		2016-03-07 14:49:37 -05:00
..
drivers	Fix panic when plugin responds with null volume	2016-03-07 14:49:37 -05:00
local	Move responsibility of ls/inspect to volume driver	2016-01-05 16:28:38 -05:00
store	Fix issue with multiple volume refs with same name	2016-02-19 15:06:09 -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-26 12:58:59 -08: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