Kasper Skytte Andersen

Had this issue too. Was due to my `ansible.cfg` was placed in a subfolder of the git repo alongside the playbook. So it didn't read the config at all and...

@sweisgerber-dev thanks. Just went through possibly everything in the ssh man pages and seems there is just no way to "turn off" the interactiveness, at least for the host key...

In addition: I can connect just fine from behind NAT when the target is the machine running the proxy server docker container. Everything else no

@tanhakabir it's bash. I saw another issue https://github.com/microsoft/vscode-remote-release/issues/5111 where sh was to blame and changing to bash solved it. Not in my case, it's already bash. But notice the proxy...

Adding `"remote.SSH.useLocalServer": false` to my VSCode settings seems to have solved the issue, see https://github.com/gravitational/teleport/issues/4176. But ideally it would be nice if the extension supported `tsh` too, or would that...

That would cause trouble. `tsh` is the standalone binary replacing `ssh`

I may be guessing here, but could it be due to the proxy command is invoking in a subshell (`-s`)?

Update: I tried replacing the `ssh` binary with `tsh ssh` by setting ``` "remote.SSH.enableRemoteCommand": true "remote.SSH.path": "/usr/local/bin/tsh ssh" ``` But it errors and defaults to `ssh` ``` ... [13:01:15.206] Install...

> Is this a valid path to ssh? `/usr/local/bin/tsh ssh` Maybe you you need to escape the space? @tanhakabir Just tried escaping the space. Makes no difference, the setting is...

> @KasperSkytte That’s what I suspected too. Curious if when you reboot the VM (thus stopping the remote VS Code server) do you then have to set `”remote.SSH.useLocalServer": “false”` once...