More reliable unmount w/ SIGINT, particularly on kvm2 #3985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With kvm2, when using mount and hitting Ctrl-C, the unmount fails with:
read tcp 127.0.0.1:40862->127.0.0.1:37853: read: connection reset by peer
If you try again, it fails with:
connection is shut down
This is because the native Docker ssh implementation dies when SIGINT is encountered. This switches the implementation to use our CommandRunner over ssh, as well as adding a second attempt using "umount -f".
Additionally, I noticed that "findmnt -T /tmp/777" would show the tmpfs mount, so there is now a
grep
command added in.