I was seeing if I could run Indi on WSL2 running Ubuntu 22.04.1 LTS. I was able to install it and then run Kstars on the Windows 10 machine but it doesn't connect to localhost.
I tried to install and start indi and it appears to run but then it times out
kurt@THREADRIPPER:~$ sudo apt-get install indi-asi
[sudo] password for kurt:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
indi-asi is already the newest version (2.2+t202301311047~ubuntu22.04.1).
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
2023-02-22T04:59:06: startup: indiserver indi-asi@192.168.12.15:7624
2023-02-22T05:01:20: Driver indi-asi@192.168.12.15:7624:
connect(192.168.12.15,7624): Connection timed out
2023-02-22T05:01:20: good bye
Then I can run with an OnStep board, an ASI Camera. But there are issues with ownership and security of the devices. (eg for the onstep, the tty device is usually owned by root:root), could only connect to asi cameras if running as root ....
So needed to start indi-web (yes it works) as root. Would not really advise this.
Haven't tested if fully with devices, but with the emulators it works fine.
Would not use it (yet) in a production environment.
I feel like I am almost there.
I followed the directions you so kindly supplied and I have the ASI224 attached:
kurt@THREADRIPPER:~/indi$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 03c3:224a ZWO ASI224MC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
kurt@THREADRIPPER:~/indi$
How do I start indi? I cd'ed to indi and ran:
kurt@THREADRIPPER:~/indi$ sudo indiserver indi-asi
2023-02-22T21:57:17: startup: indiserver indi-asi
2023-02-22T21:57:17: Driver indi-asi: 2023-02-22T21:57:17: Driver indi-asi: execlp : No such file or directory
2023-02-22T21:57:17: Driver indi-asi: process 346 exited with status 1
2023-02-22T21:57:17: Driver indi-asi: read: Connection reset by peer