[Support]: docker compose ("dockge" managed) starts and restarts - how do I fault find please? #15883

ElectronicBattle · 2025-01-07T23:06:08Z

ElectronicBattle
Jan 7, 2025

Describe the problem you are having

Hello

On my TrueNAS box and integrated with it and jailmaker, I use dockge to successfully run a few images

but I am unable to get the Frigate container to run and remain "healthy".

The logs visible in dockge say "starting|healthy|running|restarting" ad infinitum. As a result, Frigate's webUI is present for perhaps one second in every ten.

Whilst I don't know where my USB Coral TPU gets mounted within TrueNAS (and hence it might not even be visible to dockge), I do successfully run Frigate 0.13 on TrueNAS and it does use the TPU, but I run it using an official truenAS Frigate app whose innards are not exposed to me (or at least I don't know how to look deep inside the configuration of the app).

Even if I hash out the line - /dev/bus/usb:/dev/bus/usb the container still gets stuck in the loop.

Can anyone help me please?

Version

0.13 and 0.14 and 0.15

What browser(s) are you using?

Chromium Version 131.0.6778.204 (Official Build) for Linux Mint (64-bit)

Frigate config file

I can't get at it because the webUI never loads and I don't know where it is stored in docker compose/dockge. I do see the docker compose line which says - /opt/frigate/config:/config but I don't know where that directory lives, nor how to find it. I can't get into the bash shell associated with the container:

https://github.com/user-attachments/assets/502999da-800c-4b30-8ff4-35995d3ef296

Relevant Frigate log output

frigate013  | 2025-01-07 22:01:11.660311182  [INFO] Preparing Frigate...
frigate013  | s6-rc: info: service legacy-services: starting
frigate013  | 2025-01-07 22:01:11.665182707  [INFO] Starting NGINX...
frigate013  | s6-rc: info: service legacy-services successfully started
frigate013  | 2025-01-07 22:01:11.700592404  [INFO] Preparing new go2rtc config...
frigate013  | 2025-01-07 22:01:11.723023423  [INFO] Starting Frigate...
frigate013  | 2025-01-07 22:01:12.773036683  [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually
frigate013  | 2025-01-07 22:01:12.834130534  [INFO] Starting go2rtc...
frigate013  | 2025-01-07 22:01:12.952109319  22:01:12.952 INF go2rtc version 1.8.4 linux/amd64
frigate013  | 2025-01-07 22:01:12.952868381  22:01:12.952 INF [api] listen addr=:1984
frigate013  | 2025-01-07 22:01:12.952933803  22:01:12.952 INF [rtsp] listen addr=:8554
frigate013  | 2025-01-07 22:01:12.953702161  22:01:12.953 INF [webrtc] listen addr=:8555
frigate013  | 2025-01-07 22:01:15.152297167  [2025-01-07 22:01:15] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
frigate013  | 2025-01-07 22:01:15.223352022  *************************************************************
frigate013  | 2025-01-07 22:01:15.223357741  *************************************************************
frigate013  | 2025-01-07 22:01:15.223381927  ***    Your config file is not valid!                     ***
frigate013  | 2025-01-07 22:01:15.223383800  ***    Please check the docs at                           ***
frigate013  | 2025-01-07 22:01:15.223385113  ***    https://docs.frigate.video/configuration/index     ***
frigate013  | 2025-01-07 22:01:15.223387654  *************************************************************
frigate013  | 2025-01-07 22:01:15.223389310  *************************************************************
frigate013  | 2025-01-07 22:01:15.223419165  ***    Config Validation Errors                           ***
frigate013  | 2025-01-07 22:01:15.223421668  *************************************************************
frigate013  | 2025-01-07 22:01:15.223604164  12 validation errors for FrigateConfig
frigate013  | 2025-01-07 22:01:15.223611078  cameras -> upper_patio -> zones -> upperpatio
frigate013  | 2025-01-07 22:01:15.223613770    invalid literal for int() with base 10: '0.003' (type=value_error)
frigate013  | 2025-01-07 22:01:15.223615427  cameras -> upper_patio -> review
frigate013  | 2025-01-07 22:01:15.223617298    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223619005  cameras -> drive -> zones -> drive_gravel
frigate013  | 2025-01-07 22:01:15.223620987    invalid literal for int() with base 10: '0.256' (type=value_error)
frigate013  | 2025-01-07 22:01:15.223622813  cameras -> drive -> review
frigate013  | 2025-01-07 22:01:15.223624666    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223626405  cameras -> lower_patio -> zones -> lower_patio_slabs
frigate013  | 2025-01-07 22:01:15.223629064    invalid literal for int() with base 10: '0.345' (type=value_error)
frigate013  | 2025-01-07 22:01:15.223630946  cameras -> lower_patio -> review
frigate013  | 2025-01-07 22:01:15.223670916    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223673251  cameras -> blue_gate -> review
frigate013  | 2025-01-07 22:01:15.223675262    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223695947  cameras -> lower_steps -> zones -> shed-path
frigate013  | 2025-01-07 22:01:15.223723169    invalid literal for int() with base 10: '0.722' (type=value_error)
frigate013  | 2025-01-07 22:01:15.223725397  cameras -> lower_steps -> review
frigate013  | 2025-01-07 22:01:15.223727412    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223729667  camera_groups
frigate013  | 2025-01-07 22:01:15.223731749    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223733527  review
frigate013  | 2025-01-07 22:01:15.223735421    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.223737686  version
frigate013  | 2025-01-07 22:01:15.223739942    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224630062  Traceback (most recent call last):
frigate013  | 2025-01-07 22:01:15.224633838    File "/opt/frigate/frigate/app.py", line 645, in start
frigate013  | 2025-01-07 22:01:15.224635844      self.init_config()
frigate013  | 2025-01-07 22:01:15.224637822    File "/opt/frigate/frigate/app.py", line 112, in init_config
frigate013  | 2025-01-07 22:01:15.224639665      user_config = FrigateConfig.parse_file(config_file)
frigate013  | 2025-01-07 22:01:15.224641640    File "/opt/frigate/frigate/config.py", line 1346, in parse_file
frigate013  | 2025-01-07 22:01:15.224643510      return cls.parse_obj(config)
frigate013  | 2025-01-07 22:01:15.224654442    File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
frigate013  | 2025-01-07 22:01:15.224656813    File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
frigate013  | 2025-01-07 22:01:15.224658899  pydantic.error_wrappers.ValidationError: 12 validation errors for FrigateConfig
frigate013  | 2025-01-07 22:01:15.224660585  cameras -> upper_patio -> zones -> upperpatio
frigate013  | 2025-01-07 22:01:15.224662276    invalid literal for int() with base 10: '0.003' (type=value_error)
frigate013  | 2025-01-07 22:01:15.224663784  cameras -> upper_patio -> review
frigate013  | 2025-01-07 22:01:15.224665433    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224667014  cameras -> drive -> zones -> drive_gravel
frigate013  | 2025-01-07 22:01:15.224668862    invalid literal for int() with base 10: '0.256' (type=value_error)
frigate013  | 2025-01-07 22:01:15.224670427  cameras -> drive -> review
frigate013  | 2025-01-07 22:01:15.224672118    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224673816  cameras -> lower_patio -> zones -> lower_patio_slabs
frigate013  | 2025-01-07 22:01:15.224675697    invalid literal for int() with base 10: '0.345' (type=value_error)
frigate013  | 2025-01-07 22:01:15.224677664  cameras -> lower_patio -> review
frigate013  | 2025-01-07 22:01:15.224679389    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224681113  cameras -> blue_gate -> review
frigate013  | 2025-01-07 22:01:15.224683232    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224684860  cameras -> lower_steps -> zones -> shed-path
frigate013  | 2025-01-07 22:01:15.224722392    invalid literal for int() with base 10: '0.722' (type=value_error)
frigate013  | 2025-01-07 22:01:15.224725223  cameras -> lower_steps -> review
frigate013  | 2025-01-07 22:01:15.224727176    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224728620  camera_groups
frigate013  | 2025-01-07 22:01:15.224731785    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224733416  review
frigate013  | 2025-01-07 22:01:15.224735139    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224736705  version
frigate013  | 2025-01-07 22:01:15.224738529    extra fields not permitted (type=value_error.extra)
frigate013  | 2025-01-07 22:01:15.224771449  
frigate013  | 2025-01-07 22:01:15.224773762  *************************************************************
frigate013  | 2025-01-07 22:01:15.224775676  ***    End Config Validation Errors                       ***
frigate013  | 2025-01-07 22:01:15.224801069  *************************************************************
frigate013  | 2025-01-07 22:01:16.424418052  [INFO] Service Frigate exited with code 1 (by signal 0)
frigate013  | s6-rc: info: service legacy-services: stopping
frigate013  | s6-rc: info: service legacy-services successfully stopped
frigate013  | s6-rc: info: service nginx: stopping
frigate013  | s6-rc: info: service go2rtc-healthcheck: stopping
frigate013  | 2025-01-07 22:01:16.457595022  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
frigate013  | s6-rc: info: service go2rtc-healthcheck successfully stopped
frigate013  | 2025-01-07 22:01:16.551983253  [INFO] Service NGINX exited with code 0 (by signal 0)
frigate013  | s6-rc: info: service nginx successfully stopped
frigate013  | s6-rc: info: service nginx-log: stopping
frigate013  | s6-rc: info: service frigate: stopping
frigate013  | s6-rc: info: service frigate successfully stopped
frigate013  | s6-rc: info: service go2rtc: stopping
frigate013  | s6-rc: info: service frigate-log: stopping
frigate013  | s6-rc: info: service nginx-log successfully stopped
frigate013  | 2025-01-07 22:01:16.559578263  exit with signal: terminated
frigate013  | s6-rc: info: service frigate-log successfully stopped
frigate013  | 2025-01-07 22:01:16.572726740  [INFO] The go2rtc service exited with code 0 (by signal 0)
frigate013  | s6-rc: info: service go2rtc successfully stopped
frigate013  | s6-rc: info: service go2rtc-log: stopping
frigate013  | s6-rc: info: service go2rtc-log successfully stopped
frigate013  | s6-rc: info: service log-prepare: stopping
frigate013  | s6-rc: info: service s6rc-fdholder: stopping
frigate013  | s6-rc: info: service log-prepare successfully stopped
frigate013  | s6-rc: info: service legacy-cont-init: stopping
frigate013  | s6-rc: info: service s6rc-fdholder successfully stopped
frigate013  | s6-rc: info: service legacy-cont-init successfully stopped
frigate013  | s6-rc: info: service fix-attrs: stopping
frigate013  | s6-rc: info: service fix-attrs successfully stopped
frigate013  | s6-rc: info: service s6rc-oneshot-runner: stopping
frigate013  | s6-rc: info: service s6rc-oneshot-runner successfully stopped
frigate013 exited with code 0

Relevant go2rtc log output

unknown

FFprobe output from your camera

unknown

Frigate stats

unknown

Install method

Docker Compose

docker-compose file or Docker CLI command

version: "3.9"
services:
  frigate:
    container_name: frigate013
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.13.2
    shm_size: 64mb # update for your cameras based on calculation above
    devices:
      # HOST : CONTAINER
      - /dev/bus/usb:/dev/bus/usb
      - /dev/dri/renderD128:/dev/dri/renderD128
    volumes:
      # HOST : CONTAINER
      - /etc/localtime:/etc/localtime:ro
      - /opt/frigate/config:/config
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - 8971:8971
      - 8554:8554 # RTSP feeds
      - 8555:8555/tcp # WebRTC over tcp
      - 8555:8555/udp # WebRTC over udp
    environment:
      PLUS_API_KEY: ###################

Object Detector

Coral

Network connection

Mixed

Camera make and model

Floureon hikvision clone

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

Answered by NickM-27

Jan 7, 2025

the logs you are showing here show an issue trying to use a 0.14 config with 0.13 which is not valid.

View full answer

NickM-27 · 2025-01-07T23:09:51Z

NickM-27
Jan 7, 2025
Collaborator Sponsor

the logs you are showing here show an issue trying to use a 0.14 config with 0.13 which is not valid.

6 replies

NickM-27 Jan 8, 2025
Collaborator Sponsor

I don't know how truenas handles these things

ElectronicBattle Jan 8, 2025
Author

No matter. I can start exploring now that I have something (wrong config) to go on. I'll report back when I have got somewhere (or # rm -rf* in desparation!).

Thanks again.

ElectronicBattle Jan 11, 2025
Author

Short version:
I think I am getting somewhere. I think I need to find out how to get inside the docker container such that I can paste in the text from a valid config.yml - do you agree?

(I'll certainly try to figure out by myself how to do it in Docker etc. if you tell me you think it's worth a go).

Detail:
I now have a docker compose config in dockge which allows me to mount a healthy container but I can't get at the Frigate config.yml file, and hence the webUI is blank because the default config is being read rather than one peculiar to my setup.

Here is the "healthy" docker compose file

#version: "3.9"
services:
  frigate:
    container_name: frigate015
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.15.0-beta4
    shm_size: 256mb # update for your cameras based on calculation above
    devices:
      - /dev/usb:/dev/usb
      - /dev/dri/renderD128:/dev/dri/renderD128
    volumes:
      #host : container
      - /etc/localtime:/etc/localtime:ro
      - /config:/config
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - 5000:5000
      - 8554:8554 # RTSP feeds
      - 8555:8555/tcp # WebRTC over tcp
      - 8555:8555/udp # WebRTC over udp
    environment:
      #      mem_limit: 4096m # seemed to make load a bit worse
      #      cpus: "4" # seemed to make load a bit worse
      LIBVA_DRIVER_NAME: i965
      PLUS_API_KEY:##############################
networks: {}

Here are the dockge logs which result (pruned to include what I hope are the salient bits), noting that I can't get at the Frigate logs via the webUI and I don't know other ways to see them:

] watchdog.name_of_your_camera   ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
frigate015  | 2025-01-11 11:22:05.538049191  [2025-01-11 11:22:05] ffmpeg.name_of_your_camera.detect ERROR   : [tcp @ 0x561fc2607280] Connection to tcp://10.0.10.10:554?timeout=5000000 failed: No route to host
] frigate.video                  ERROR   : name_of_your_camera: Unable to read frames from ffmpeg process.
frigate015  | 2025-01-11 11:19:45.354072838  [2025-01-11 11:19:45] frigate.video                  ERROR   : name_of_your_camera: ffmpeg process is not running. exiting capture thread...
frigate015  | 2025-01-11 11:19:45.551403399  2025/01/11 11:19:45 [error] 176#176: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.115, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "192.168.1.193:5000"
frigate015  | 2025-01-11 11:26:05.955367330  [2025-01-11 11:26:05] frigate.video                  ERROR   : name_of_your_camera: Unable to read frames from ffmpeg process.
frigate015  | 2025-01-11 11:26:05.955509156  [2025-01-11 11:26:05] frigate.video                  ERROR   : name_of_your_camera: ffmpeg process is not running. exiting capture thread...

I can see that Frigate is trying to read from tcp://10.0.10.10 which I think is the default placeholder config.yml.

If I check the webUI and look at any of the icons, for example
http://192.168.1.193:5000/
http://192.168.1.193:5000/logs
http://192.168.1.193:5000/system#general
the page is blank apart from the vertical left hand toolbar thus:

NickM-27 Jan 11, 2025
Collaborator Sponsor

it needs to be done via mounts, creating a file only inside of the container is not a viable solution as many features won't work and you'd have to do it every time

ElectronicBattle Jan 11, 2025
Author

OK, I know the sort of thing I need to look into in that case:

- /config:/config
needs to be something like
- /mnt/raid/frigate/config:/config

Thanks Nick. I'll see what I can do.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: docker compose ("dockge" managed) starts and restarts - how do I fault find please? #15883

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Support]: docker compose ("dockge" managed) starts and restarts - how do I fault find please? #15883

ElectronicBattle Jan 7, 2025

Describe the problem you are having

Version

What browser(s) are you using?

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Frigate stats

Install method

docker-compose file or Docker CLI command

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment · 6 replies

NickM-27 Jan 7, 2025 Collaborator Sponsor

NickM-27 Jan 8, 2025 Collaborator Sponsor

ElectronicBattle Jan 8, 2025 Author

ElectronicBattle Jan 11, 2025 Author

NickM-27 Jan 11, 2025 Collaborator Sponsor

ElectronicBattle Jan 11, 2025 Author

ElectronicBattle
Jan 7, 2025

Replies: 1 comment 6 replies

NickM-27
Jan 7, 2025
Collaborator Sponsor

NickM-27 Jan 8, 2025
Collaborator Sponsor

ElectronicBattle Jan 8, 2025
Author

ElectronicBattle Jan 11, 2025
Author

NickM-27 Jan 11, 2025
Collaborator Sponsor

ElectronicBattle Jan 11, 2025
Author