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
..
flags.go
flags_freebsd.go	Use lazy unmount for local volume driver unmount	2017-04-27 08:43:43 -04:00
flags_linux.go	Use lazy unmount for local volume driver unmount	2017-04-27 08:43:43 -04:00
flags_unsupported.go	Use lazy unmount for local volume driver unmount	2017-04-27 08:43:43 -04:00
mount.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
mount_unix_test.go
mounter_freebsd.go
mounter_linux.go
mounter_linux_test.go
mounter_solaris.go
mounter_unsupported.go
mountinfo.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
mountinfo_freebsd.go
mountinfo_linux.go
mountinfo_linux_test.go
mountinfo_solaris.go
mountinfo_unsupported.go
mountinfo_windows.go
sharedsubtree_linux.go
sharedsubtree_linux_test.go
sharedsubtree_solaris.go