SSH key verification with ManagedFile

[snerzkristall]

I am currently trying to flash a binary from a remote host. I use a custom driver (openocd driver with minor changes) for this which syncs a managedfile object to the machine running the exporter. Can i speficy ssh keys somewhere, because this is where my test breaks...?
Interacting via labgrid-client console is no problem it's just the ssh connection for syncing files.

Current setup
Windows 10 PC
|
Docker container (labgrid client) --> needs ssh private key for syncing
|
(local network)
|
Raspberry Pi 4b (running exporter and coordinator) --> has ssh public key
|
STM32 Boards (flash target)

Error log:

 transition state='start', args={'status': 'off'}
    off state='start'
    off state='stop', exception=ExecutionError(msg="failed to connect to <RASPI HOSTNAME> with args ['ssh', '-x', '-o', 'LogLevel=ERROR', '-o', 'PasswordAuthentication=no', '-n', '-MN', '-o', 'ConnectTimeout=30', '-o', 'ControlPersist=300', '-o', 'ControlMaster=yes', '-o', 'ControlPath=/tmp/labgrid-connection-drvj5yj0/control-<RASPI HOSTNAME>', '-o', 'StrictHostKeyChecking=yes',<RASPI HOSTNAME>], returncode=255 [],[b'No ECDSA host key is known for <RASPI HOSTNAME> and you have requested strict checking.\\r\\n', b'Host key verification failed.\\r\\n'] ", stdout=None, stderr=None), duration=0.121

[jluebbe]

For connecting to the exportes, labgrid just uses your user's ssh configuration. So if manual ssh works there (in your container), it shouldn't be different for labgird.

[Bastian-Krause]

Extending your PATH in /etc/profile will not affect SSH. Have a look at your /etc/ssh/sshd_config on your Raspberry Pi. There should be something like # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin in there. That's the PATH that is used.

What system is installed on the Pi? For Debian, there is a sispmctl package.

[snerzkristall]

Solution:
ssh is using /usr/bin/local on the server-machine, if your executable is not there, the error above is thrown.

Create symbolic link ln -s (not safe or reliable) or install on correct path to fix.

[snerzkristall]

I am using RaspbianOS (bullseye), the debian package (version 3.1) doesn't recognize my device...

[jluebbe]

sispmctl 4.1 was released in 2018, so updating the package in debian would be good, but won't help you in the short term. So perhaps just build and install it from source on your exporter.

[snerzkristall]

Ok thanks for the info.
I compiled 4.8 from source and it works without problems now.

(arnitestgrid-py3.10) root@20ea07000afb:~/arnitestgrid# labgrid-client -p heating power get
power for place heating is on

Thank you both a lot for the super quick and friendly responses :)