Trouble with Unraid Docker of CPAI

[stev067]

My setup:
Running Blue Iris on a Windows VM on an Unraid machine
Running Codeproject.AI as a docker on the same Unraid machine
Coral m.2 TPU

I'm trying to set up my CPAI docker to run the Coral module, and I feel like this docker is broken in more ways than not. Does anyone else use this successfully? Even when I can somehow get the Coral module running, and other "preinstalled-modules" disabled, if I change any settings, I break it. If I restart the docker, zero settings are retained.
Any help would be greatly appreciated.

 

[hapstabu]

My setup:
Running Blue Iris on a Windows VM on an Unraid machine
Running Codeproject.AI as a docker on the same Unraid machine
Coral m.2 TPU

I'm trying to set up my CPAI docker to run the Coral module, and I feel like this docker is broken in more ways than not. Does anyone else use this successfully? Even when I can somehow get the Coral module running, and other "preinstalled-modules" disabled, if I change any settings, I break it. If I restart the docker, zero settings are retained.
Any help would be greatly appreciated.

Several things...
Check out the Running CPAI on Docker information on the Code Project web site.

Running CodeProject.AI Server in Docker - CodeProject.AI Server v2.7.0

A Guide to using and developing with CodeProject.AI Server

www.codeproject.com

Advanced Docker launch (settings saved outside of the container)


You will need to create 2 folders in the Linux filesystem, and reference them in the run command or the Docker Compose file in order to save the changes that you make, like deleting modules. Otherwise, the Docker image will start with all the default settings every time.

I am running CPAI on the Windows Blue Iris machine with a Coral M.2 accelerator. I have also seen with later Coral modules that any change I try to make to the Coral module crashes it. I've given up, and now use the YOLOv5.NET module.

And finally, I started with the Coral USB accelerator, which was terrible with CPAI on Windows.

I had thought there was a hardware problem, but that device has been working flawlessly with Frigate NVR on Linux for close to a year now. In Frigate, the Coral USB is the ONLY detector, so I know it is working. So my assumption is that the issue is with the software, not the hardware.


Sent from my iPlay_50 using Tapatalk

 

[stev067]

I appreciate you taking a look. I think I have straightened things out. The Unraid docker config already had me setting up mappings to the 2 folders you mentioned, so that was not the problem. I had some help from the CPAI forums also, where a member pointed out that this version (2.6.5) has a bug where the "modulesettings.json" file never gets created. So any changes you make, such as whether a module should auto-start, which model size to use, etc, would never persist through a reboot of the container. I ended up setting up a 2nd container, using an earlier version (2.6.2) and stealing this settings file from that.
My 2nd issue was that I was trying to use custom models in BI, with default object detection disabled. And it sounds like with Coral on CPAI with BI, you can only use default object detection and no custom models. So I had that backwards.
After all that, I'm using a large model, getting 200ms inference times, and thankfully the night moths are no longer being ID'd as Person. And the CPAI settings persist through a reboot of the container now.

 

[stev067]

Just wanted to add that this bug is fixed in 2.8. The modulesettings.json file is correctly created and updates when you change module settings.