Brian Goff 54dcbab25e Do not remove containers from memory on error ... Before this, if `forceRemove` is set the container data will be removed no matter what, including if there are issues with removing container on-disk state (rw layer, container root). In practice this causes a lot of issues with leaked data sitting on disk that users are not able to clean up themselves. This is particularly a problem while the `EBUSY` errors on remove are so prevalent. So for now let's not keep this behavior. Signed-off-by: Brian Goff <cpuguy83@gmail.com>		2017-05-05 17:02:04 -04:00
..
aufs.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
aufs_test.go	use t.Fatal() to output the err message where the values used for formatting	2017-02-23 10:16:22 +08:00
dirs.go	Adds ability to squash image after build	2016-11-01 13:41:59 -04:00
mount.go	Be more lenient on auplink errors.	2016-04-06 18:24:19 -07:00
mount_linux.go	daemon/graphdriver/aufs fix lint errors/warnings	2015-07-28 06:17:05 +00:00
mount_unsupported.go	daemon/graphdriver/aufs fix lint errors/warnings	2015-07-28 06:17:05 +00:00