Yes, it looks like your device is 0003:2C97:1015.0011. But it is not available inside the container sysfs. You can try to pass through entire host sysfs to the container, but it’s not a safe option.
Also to note, that when I try to grep “usb” in git repo
this is a shared library, according to your strace it’s loaded by the cardano-hw-cli process.
Everything went fine.
I could run all the needed operations.
By doing the udev rules on HOST,
Then doing the pass through for hidraw 0 and 1 from HOST to GUEST.
Thanks
Hi @tomp
Yes I did see while digging the topic,
But I got stuck/hesitating by a sentence in the intro.
Could you help me understand “Implementation depends on systemd-udev to be run on the host” ?
Can you extend/reformulate ?
Also what would be the difference with the unix-char type I used ?
Presumably that means it relies on udev events generated by systemd-udev to detect when a device is connected. It should still generate the same kind of device inside the container though.
If you use unix-block or unix-char devices you can specify required=false and then the device is dynamically added/removed when the source path appears/disappears.