[BUG] Won't connect to DeepStack

SOLVED Solution provided by @szmidtpiotr works! 😃 https://github.com/jakowenko/double-take/issues/167#issuecomment-975376875

Describe the bug I have installed DeepStack as a seperate Docker container. Forwarded port 5000 to 4999 (on the host). This used to be port 80, but I thought some conflict could’ve been the issue, which it wasn’t. I am using a key. Double Take won’t connect to my DeepStack. Frigate works fine.

Version of Double Take v1.6.0-893328f

Expected behavior Double Take should connect to my DeepStack detector If there are any errors, they should be shown in the logs.

Screenshots

Hardware

• OS: Home Assistant Operating System
• Browser: Firefox

Additional context

# Double Take
mqtt:
  host: 192.168.10.105
  user: <USER>
  password: <PASS>

frigate:
  url: http://192.168.10.105:5000

detectors:
  deepstack:
    url: http://192.168.10.105:4999
    key: <KEY>

docker run -d --restart=unless-stopped --name="deepstack" -e VISION-DETECTION=True -e VISION-FACE=True -e API-KEY="<MY KEY>" -v localstorage:/datastore -p 80:5000 deepquestai/deepstack

Tested both with and without key.

[willpowell8]

I have been trying to get Deepstack on a Jetson Tx2 4GB which is close to the Jetson nano as far as performance. @LordNex it was crashing when connecting. I found it was because of memory pressure so increased swap size on connected SSD and it stopped it crashing.

[Calimerorulez]

@Heisenberg2980 But that is for a VM specifically, I can’t recall yet how to do it for a container. I don’t think that’s possible, because containers always see the host CPU as it is.