Alexander Larsson c199ed228b devmapper: Move init layer to top rather than bottom ... The init layer needs to be topmost to make sure certain files are always there (for instance, the ubuntu:12.10 image wrongly has /dev/shm being a symlink to /run/shm, and we need to override that). However, previously the devmapper code implemented the init layer by putting it in the base devmapper device, which meant layers above it could override these files (so that ubuntu:12.10 broke). So, instead we put the base layer in *each* images devmapper device. This is "safe" because we still have the pristine layer data in the layer directory. Also, it means we diff the container against the image with the init layer applied, so it won't show up in diffs/commits.		2013-09-26 15:09:32 +00:00
..
docker-device-tool	devmapper: Add simple tool to test the DeviceSet commands	2013-09-26 15:08:54 +00:00
deviceset_devmapper.go	devmapper: Move init layer to top rather than bottom	2013-09-26 15:09:32 +00:00
devmapper.go	Add libdevmapper wrapper	2013-09-26 15:08:54 +00:00