connecting to custom image

[ghost]

I am having issue connecting over SSH to a custom image I have made. It seems it is trying to use vagrant's keys to connect. I dont see an option to provide a custom key.

transient run -name debian10_x64.orcircd -image debian10_x64,file=/home/brettg/VMs/debian10_x64.qcow2 -ssh-console -ssh-user orcircd -- -nographic -enable-kvm -m 1G

RuntimeError: Failed to connect with command '['ssh', '-o', 'StrictHostKeyChecking=no', '-o', 'UserKnownHostsFile=/dev/null', '-o', 'batchMode=yes', '-o', 'LogLevel=ERROR', '-o', 'ConnectTimeout=3', '-p', '42615', '-i', '/home/brettg/.local/share/transient/vagrant.key', '-i', '/home/brettg/.local/share/transient/transient.key', '[email protected]']' after 90 seconds

[ALSchwalm]

Hmm, this is a good issue. Currently transient attempts to connect with the vagrant keying information (for comparability with images on vagrant cloud) and the transient ssh key. My thought was that if you were making a custom image, you would probably just use that key (the private portion available here: https://github.com/ALSchwalm/transient/blob/master/transient/static/transient.priv), but we should definitely document that if we don't and we should probably allow users to specify arbitrary ssh flags, so they can add any keying info or other settings.

[ghost]

I think we should likewise support ssh-key args in the configuration example. My python is a little dusty, but i'll see if I can come up with a solution

[Timmmm]

I'm seeing the same issue but with the image from the Readme. Here's the command it runs:

transient run centos/7:2004.01 --copy-in-before test_input:/home/vagrant/test_input --ssh-command /home/vagrant/test_input/test.sh -- -m 1G

Is it really a key issue? Why does it look like a timeout rather than some "permission denied" error? Also the exact same command works on my Mac.

Nice project btw.