Stop docker containers on linux

[0kate]

Description of the changes

1. Additional support to stop docker containers by specifying port number.

• add Killable trait for abstraction layer to implement stopping native processes and docker containers.
• Maybe we should relocate this trait to more upper hierarchy for implement stopping logics abstractly to all platforms.

2. Add some libraries

• anyhow・・・ for easier generic error handling
• bollard・・・for docker client in rust
• tokio・・・for asynchronous runtime (because the bollard is only supported tokio runtime currently)

Sorry for some huge changes. 🙏

Related issue(s)
If this PR is related to an existing issue, please link to it using the Fixes #issue_number or Closes #issue_number syntax.

Type of change
Please select one or multiple of the following options:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Code cleanup (refactoring or improving code quality)
• Documentation update (adding or updating documentation, updating README)

Checklist:

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Additional information
Add any other information or screenshots about the pull request here.

[jacobtread]

I don't think that this commit really needs to introduce the anyhow crate from the looks of your changes all the errors already have some sort of mapping to std::io::Error and those that can't can just use the ErrorKind::Other from your usages it might be worth just mapping your errors into io errors instead of adding an extra crate

[jkfran]

Hi @0kate, thank you so much for the contribution! Would it be possible to eliminate all the unwrap()? I know some of them were already present, but we should aim to eliminate them from killport.

About anyhow, I agree with the previous comment. In our case, we're only dealing with std::io::Error and a few other error types that can be easily converted to std::io::Error. It might be simpler and more consistent to stick with std::io::Error.

[0kate]

@jacobtread @jkfran
Thank you for your confirming!
I understood about anyhow and only dealing std::io::Error. That's certainly right.

It's okay about eliminating unwrap() too!
I will add changes above 👍

[0kate]

@jkfran
Hello. I have eliminated unwrap and using error dealing with "anyhow" crate.
Please confirm that changes. 🙏

[banool]

Hey I'd love to see this landed, any other changes needed?