paramiko ssh transport leads to strange discrepancies to docker cli
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
E.g. when using compose the dependency to paramiko generates avoidable problems (by using the ssh binary in the path). compose and the normal docker-cli work totally different. Furthermore verbose output is generated on stdout.
Paramiko does not obey the .ssh/config as #2251 already pointed out. Far more fatal it does e.g. not support jump hosts or any custom auth schemes.
IMHO it would be the far better choice also removing not so easy to handle second-level dependencies like py-nacl (does not really build via pip in cygwin) to just use the command line ssh in the path as docker-cli does. Paramiko should be e.g. only used when using e.g a --native-ssh switch as i think it is given in docker-machine.
Is there actually any downside in using the systems ssh client?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the SSH behavior described for compose and the normal docker CLI, including .ssh/config, jump hosts, custom authentication, and verbose output. Review the proposed system SSH client approach and the possible --native-ssh alternative; done requires a decided transport design and confirmation that the listed discrepancies and dependency concerns are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- cli, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100