Matthew Heon 0f6b0e8c9c Ensure volumes can be removed when they fail to unmount ... Also, ensure that we don't try to mount them without root - it appears that it can somehow not error and report that mount was successful when it clearly did not succeed, which can induce this case. We reuse the `--force` flag to indicate that a volume should be removed even after unmount errors. It seems fairly natural to expect that --force will remove a volume that is otherwise presenting problems. Finally, ignore EINVAL on unmount - if the mount point no longer exists our job is done. Fixes: #4247 Fixes: #4248 Signed-off-by: Matthew Heon <matthew.heon@pm.me>		2019-10-14 10:32:15 -04:00
..
config.go	Correctly report errors on unmounting SHM	2019-09-05 17:12:27 -04:00
containerstate.go	libpod removal from main (phase 2)	2019-06-27 07:56:24 -05:00
errors.go	Ensure volumes can be removed when they fail to unmount	2019-10-14 10:32:15 -04:00
exec_codes.go	Fix exit code failure	2019-09-17 12:01:02 -04:00
version.go	libpod removal from main (phase 2)	2019-06-27 07:56:24 -05:00