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
..
btrfs.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
btrfs_test.go	Pass all graphdriver create() parameters in a struct	2016-11-09 15:59:58 -05:00
dummy_unsupported.go	Replace "amd64" build tags with "cgo" as appropriate, and remove where unnecessary	2014-08-06 17:20:21 -06:00
version.go	daemon/graphdriver/btrfs fix lint errors/warnings	2015-07-23 22:48:45 +00:00
version_none.go	Fix typos found across repository	2015-12-13 18:04:12 +02:00
version_test.go	fix t.Errorf to t.Error in serveral _test.go	2016-11-14 17:54:43 +08:00