Alexander Larsson 4bdb8c03fc graphdriver: Fail initialization if supported but got error ... If a graphdriver fails initialization due to ErrNotSupported we ignore that and keep trying the next. But if some driver has a different error (for instance if you specified an unknown option for it) we fail the daemon startup, printing the error, rather than falling back to an unexected driver (typically vfs) which may not match what you have run earlier. Docker-DCO-1.1-Signed-off-by: Alexander Larsson <alexl@redhat.com> (github: alexlarsson)		2014-05-09 14:48:39 +02:00
..
aufs.go	graphdriver: Fail initialization if supported but got error	2014-05-09 14:48:39 +02:00
aufs_test.go	graphdriver: Fail initialization if supported but got error	2014-05-09 14:48:39 +02:00
dirs.go	Rename runtime/* to daemon/*	2014-04-17 14:43:01 -07:00
migrate.go	Initial work on selinux patch	2014-04-29 03:40:05 -07:00
mount.go	Rename runtime/* to daemon/*	2014-04-17 14:43:01 -07:00
mount_linux.go	Rename runtime/* to daemon/*	2014-04-17 14:43:01 -07:00
mount_unsupported.go	Rename runtime/* to daemon/*	2014-04-17 14:43:01 -07:00