54dcbab25e
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> |
||
---|---|---|
.. | ||
flags.go | ||
flags_freebsd.go | ||
flags_linux.go | ||
flags_unsupported.go | ||
mount.go | ||
mount_unix_test.go | ||
mounter_freebsd.go | ||
mounter_linux.go | ||
mounter_linux_test.go | ||
mounter_solaris.go | ||
mounter_unsupported.go | ||
mountinfo.go | ||
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 |