making cvdr connections

[meanderingsquirreleatsnuts]

from local, connecting to emulators on remote machine - I can't see to establish a connection with cvdr - for that matter, this doesn't work running on the remote host either. I can see the emulator in browser on local machine after installing coturn on remote. I have been able to connect via adb by finding and using the ip address of the docker container - even tunneling via ssh to local pc.

But connecting via cvdr is still thwarting me. Would appreciate some help

$ cvdr list
Host: aebfa2503e3fb8fbd8bc6e337cd9492b02a986a8360476033b9ad86bb7d53034
WebUI: http://172.16.220.14:8080/v1/zones/local/hosts/aebfa2503e3fb8fbd8bc6e337cd9492b02a986a8360476033b9ad86bb7d53034/
Group: cvd
Instance: 1
Status: Running
ADB: not connected
Displays: [720 x 1280 ( 320 )]
Logs: http://172.16.220.14:8080/v1/zones/local/hosts/aebfa2503e3fb8fbd8bc6e337cd9492b02a986a8360476033b9ad86bb7d53034/cvds/cvd/1/logs/
$ cvdr connect --host=aebfa2503e3fb8fbd8bc6e337cd9492b02a986a8360476033b9ad86bb7d53034 --group=cvd
Waiting connection from ADB server timed out: accept tcp 127.0.0.1:33981: i/o timeout
1 error occurred:
* failed to connect to aebfa2503e3fb8fbd8bc6e337cd9492b02a986a8360476033b9ad86bb7d53034/cvd/1: no response from agent

[meanderingsquirreleatsnuts]

hmmm, might have solved - thought I'd add solution for others - in cvdr cvdr.toml, since I'm using webRTC
ConnectAgent = "webrtc"

[0405ysj]

This is my guess yet though, perhaps adb server daemon is not running on your computer so cvdr fails to find it. If adb devices is executed in advance on your computer, it would be probably well connected.

I have a plan to ensure adb server daemon is running in advance of executing cvdr create or cvdr connect, but I didn't have a time to land the fix.

[meanderingsquirreleatsnuts]

seems to be working, but will try again tomorrow. Is there a forum / gaggle of humans discussing this orchestration somewhere? This tool comes across as a having a small following and is perhaps not a mainstream tool?

[0405ysj]

Currently, the best approach is sending a mail to cloud-android-ext@google.com. Our mainstream tool is at https://github.com/google/android-cuttlefish, and this repository is for supporting orchestration of remote machine. (e.g. running CF ARM targets remotely)