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
..
copy.go	Don't create devices if in a user namespace	2016-08-12 16:26:58 -04:00
overlay.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
overlay_test.go	Remove failing overlay test	2016-06-13 22:34:57 -07:00
overlay_unsupported.go	Windows: Don't build Linux graph drivers	2015-06-08 15:09:33 -07:00