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
..
chtimes.go	…
chtimes_test.go	…
chtimes_unix.go	…
chtimes_unix_test.go	…
chtimes_windows.go	…
chtimes_windows_test.go	…
errors.go	…
events_windows.go	…
exitcode.go	…
filesys.go	…
filesys_windows.go	…
lstat_unix.go	…
lstat_unix_test.go	…
lstat_windows.go	…
meminfo.go	…
meminfo_linux.go	…
meminfo_solaris.go	…
meminfo_unix_test.go	…
meminfo_unsupported.go	…
meminfo_windows.go	…
mknod.go	…
mknod_windows.go	…
path_unix.go	…
path_windows.go	…
path_windows_test.go	…
process_unix.go	…
rm.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
rm_test.go	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
stat_darwin.go	…
stat_freebsd.go	…
stat_linux.go	…
stat_openbsd.go	…
stat_solaris.go	…
stat_unix.go	…
stat_unix_test.go	…
stat_windows.go	…
syscall_unix.go	…
syscall_windows.go	…
syscall_windows_test.go	…
umask.go	…
umask_windows.go	…
utimes_freebsd.go	…
utimes_linux.go	…
utimes_unix_test.go	…
utimes_unsupported.go	…
xattrs_linux.go	…
xattrs_unsupported.go	…