Hmm okay not sure how to do that...

I have added '-v /var/crash:/var/crash' to the Extra parameters in the Unraid container settings, is that correct

docker-run.pdf
Viseron-log.pdf

Not sure if these help, but I've attached the docker run settings and a log file...

Yes that is correct.
However, that is how you would troubleshoot this on a Linux server, not sure how to do this on Unraid so you will have to look around a bit to find how to read the crash logs on Unraid

Thanks, I cannot find any way to get crash logs out of the container...

I don't see a directory /var/crash in the Viseron container when it is running without object detection, should there be one?

I see that the device 1a6e:089a has been detected is that correct or does it need to be 18d1:9302 Google Inc?

I have never used Unraid so unfortunately im not sure how the crash dumps are processed :(

/var/crash only gets populated when a sysdump occurs (at least on Ubuntu) so it should not appear unless there is an error.

The Coral can have either 1a6e:089a or 18d1:9302 so that should be okay

This is exactly the error I wrote about above.
I use this hack to solve it:

My Dockerfile looks like this:

FROM roflcoopter/amd64-cuda-viseron:dev
RUN apt-get -y update && apt-get install -y build-essential cmake python3-dev
RUN pip install --force-reinstall dlib

docker-compose.yml changes to use this Dockerfile:

  viseron:
#    image: roflcoopter/amd64-cuda-viseron:dev
    build: .

It rebuilds Dlib inplace.
You may need to use non cuda image.

How do you run viseron now? docker-compose up? docker run command? Some web ui?

RUN apt-get -y update && apt-get install -y build-essential cmake python3-dev
It runs in viseron container, so it's independed from unraid package manager.

I’ve had a look on Unraid and apt-get, cmake pip are all an unknown command.

This commands not needed on unraid itself. Build runs inside viseron container.

You can use docker command in CLI to build and run container.
place Dockerfile somwere, then run commands:

cd /path/to/your/Dockerfile
run docker build . --tag viseron-hacked
run docker run --rm \
  -v {recordings path}:/recordings \
  -v {config path}:/config \
  -v /etc/localtime:/etc/localtime:ro \
  -p 8888:8888 \
  --name viseron \
  viseron-hacked

Also, you can use docker exec to run commands in allready running viseron container. Note: remove object detection from configuration and restart container, container must be in running state.

Get viseron container name/id:
docker ps | grep viseron

Run build in container:

docker exec -it name-or-id-of-viseron-container apt-get -y update
docker exec -it name-or-id-of-viseron-container apt-get install -y build-essential cmake python3-dev
docker exec -it name-or-id-of-viseron-container pip install --force-reinstall dlib
docker restart name-or-id-of-viseron-container

Ahh yes that is a bit old, i think its crashing since your CPU does not support AVX2 for instance
As @bsyomov said its possible to build the containers yourself, it takes some time bit its not very hard.

You can follow these steps to build everything: https://viseron.netlify.app/docs/developers/docker