Alexander Larsson 00401a30b7 devmapper: Use a "rootfs" subdirectory in the devmapper volume ... We place the actual image/containers in the "rootfs" directory, which allows us to have other data in the toplevel directory in the mount. For starters, this means the "lost+found" directory from mkfs will not always be in your container/image. Secondly, we can create a file "id" in the toplevel dir which is not visible from the container. This is useful because it allows us to map back from the device fs to the container if something goes wrong with the devicemapper metadata.		2013-11-19 09:29:42 +01:00
..
docker-device-tool	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
deviceset.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
devmapper.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
devmapper_log.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
devmapper_test.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
devmapper_wrapper.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
driver.go	devmapper: Use a "rootfs" subdirectory in the devmapper volume	2013-11-19 09:29:42 +01:00
driver_test.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00
mount.go	Move all drivers to the same subdir graphdriver	2013-11-15 15:48:24 -08:00