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
..
aufs	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
btrfs	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
devmapper	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
graphtest	Moves graphdriver plugn docs out of experimental	2016-12-22 15:30:25 -05:00
overlay	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
overlay2	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
overlayutils	'docker daemon' deprecation message doesn't use the new versioning scheme	2017-03-03 17:26:49 +08:00
quota
register
vfs	Do not remove containers from memory on error	2017-05-05 17:02:04 -04:00
windows	Windows: Do not attempt to clean empty windowsfilter folder	2017-04-17 13:10:15 -07:00
zfs	Switch to using opencontainers/selinux for selinux bindings	2017-04-24 21:29:47 +02:00
counter.go	Merge pull request #31083 from xulike666/fight-for-readability	2017-03-03 15:13:01 +01:00
driver.go	Let graphdrivers declare diff stream fidelity	2017-03-31 08:32:00 -07:00
driver_freebsd.go
driver_linux.go
driver_solaris.go
driver_unsupported.go
driver_windows.go
fsdiff.go
plugin.go	Let graphdrivers declare diff stream fidelity	2017-03-31 08:32:00 -07:00
proxy.go	Let graphdrivers declare diff stream fidelity	2017-03-31 08:32:00 -07:00