Working with remote boards
I found this page to be helpful: https://www.tecmint.com/access-linux-server-using-a-jump-host/
You should try to make each leg of the jump (from local machine to jump server, and from jump server to remote machine) password-less.
I found that if my local machine's public key was in the remote machine's authorized keys file, then I could log in without a password, even if the jump server's public key was not in the remote machine's authorized keys file.
For example, in your local ttc.conf, you can put:
Please note that 'ttc status <remote-board>' does not work with ttc version 1.4.4. This is due to internal usage of %(ip_addr)s in the function network_status(), which will not be correct for the remote-board.
In order to set up password-less operation, or use of a jump server or ProxyCommand, you have to add appropriate items (config and keys) to: /var/lib/jenkins/.ssh
Please note that this may make your docker container a security risk, as it may expose your private keys to tests. Please use caution when adding private keys or other sensitive security information to the docker container.