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
..
check.go	Use naive diff for overlay2 when opaque copy up bug present	2016-11-09 13:42:10 -08:00
mount.go	Avoid fork on mount for overlay2 in common case	2016-08-22 11:43:10 -07:00
overlay.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
overlay_test.go	Skip overlay2 diff tests when using naivediff	2016-11-10 13:52:22 -08:00
overlay_unsupported.go	Add separate overlay2 driver	2016-06-08 00:16:01 -07:00
randomid.go	Add separate overlay2 driver	2016-06-08 00:16:01 -07:00