Connecting Vector to Dockerized Escape Pod - Githubissues

cyb3rdog / escapepod-docker

Unofficial Docker image wrapping the Escape Pod for Anki/DDL Vector Robot.

MIT License

18 stars 8 forks source link

Connecting Vector to Dockerized Escape Pod #2

Open m-vandeneede opened 3 years ago

m-vandeneede commented 3 years ago

Hi, I'm running this docker image on a local server and everything seems to be working just fine GUI-wise. I've read in issue #1 that you need to use a proper RPi EP installation for the onboarding process, I've done this and vector seems to be able to communicate with it just fine. However, as soon as I turn the RPi off so that just the dockerized escapepod instance remains, vector no longer connects to anything. My guess is that vector keeps trying to connect to the IP of my RPi escapepod, but I can't really test it.

What are the next steps here? How do I get vector to talk with my dockerized escapepod instance instead of the RPi?

cyb3rdog commented 2 years ago

Hey,

depends, if your Vector is unlocked OSKR/DVT bot, or just regular production bot...

In case you have access to Vector's filesystem, you can always configure the endpoints in the following file: /anki/data/assets/cozmo_resources/config/server_config.json the default configuration look's like this:
```
{
    "jdocs": "escapepod.local:8084",
    "tms": "escapepod.local:8084",
    "chipper": "escapepod.local:8084",
    "check": "escapepod.local:8080/ok",
    "logfiles": "s3://anki-device-logs-prod/victor",
    "appkey": "oDoa0quieSeir6goowai7f"
}
```
for production robots, you're unfortunatelly unable to change this, so your only chance is to tickle your networking to make these enpoints discoverable on your network...