-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to define SSH connection options #1301
Comments
Also need this. For now, I'm using with-ssh-docker-socket (disclaimer: i built that). It lets you specify the SSH command using go-templates, e.g.: $ with-ssh-docker-socket \
-ssh-app='ssh -nNT -L "{{.LocalPort}}:{{.RemoteSocketAddr}}" "{{.RemoteHost}}"' \
-a user@remote-host \
docker ps # (or any other command, e.g. docker-compose) Also there's an I would prefer to use |
Just adding another use case here. I've been looking at trying to split up my terraform modules into two main parts: Just a small additional use case :) |
We have no plans at the moment to extend the scope of this feature. So, I'm closing this issue for now but we can possibly reconsider in the future. |
Docker supports `~/.ssh/config` but not custom SSH config files (docker/cli#1301). Podman does not support `~/.ssh/config` but might partially do so soon (containers/podman#23831).
Description
The new ssh connection introduced in #1014 does not allow to define many SSH options that are sometimes needed.
It indeed supports
~/.ssh/config
, but what about portability?Possible solutions that come to my mind:
ssh -F /tmp/other_config
) that can be filled by a script previously.docker -H ssh://example.com -o ForwardAgent=yes -o 'ProxyCommand=/usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p ' container ls
)Current workaround would be for a script to override current
$PATH
and prepend a differentssh
binary that proxies to the original one. But that's hacky!The text was updated successfully, but these errors were encountered: