summaryrefslogtreecommitdiff
path: root/docs/podman-pull.1.md
diff options
context:
space:
mode:
authorMatthew Heon <matthew.heon@pm.me>2019-10-14 10:29:54 -0400
committerMatthew Heon <matthew.heon@pm.me>2019-10-14 10:32:15 -0400
commit0f6b0e8c9ca3bfa944294a0de98869d732988893 (patch)
treeeb93b90e8ae7e0cea863e1f3c7ac18b205f58bd8 /docs/podman-pull.1.md
parenta8993bab7861e2181630a022484d3f55f706a460 (diff)
downloadpodman-0f6b0e8c9ca3bfa944294a0de98869d732988893.tar.gz
podman-0f6b0e8c9ca3bfa944294a0de98869d732988893.tar.bz2
podman-0f6b0e8c9ca3bfa944294a0de98869d732988893.zip
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>
Diffstat (limited to 'docs/podman-pull.1.md')
0 files changed, 0 insertions, 0 deletions