Frigate Failed to Start | Home Assistant | Page 1

charred shell Dec 27, 2024, 7:06 PM

#

I just used portainer maybe in the wrong way to download latest frigate image. I used the recreate container and pull image option now frigate is down. The latest version of portainer is slightly different I used to just go in and repull image and I think I went a little too far. Anyone know how I might be able to recover my previous container and settings?

📎 frigate_logs.txt

night veldt Dec 27, 2024, 7:07 PM

#

Share the stack/compose from portainer.

sly monolith Dec 27, 2024, 7:29 PM

#

That is an odd failure

charred shell Dec 27, 2024, 7:37 PM

#

It did give errros like it did fully pull everything

#

it gave an error + a success so not sure where it failed.

#

I can't find the docker-compose.yml and not sure how to pull it from portainer.

#

I searched the file system for docker-compose.yml and nothing found.

#

I searched discord as well for some of those errors above and never been reported.

night veldt Dec 27, 2024, 7:42 PM

#

Did you create the container via the stack feature or purely through the GUI?
Kind of sucks to troubleshoot the latter as you have to share pictures of all the options.

sly monolith Dec 27, 2024, 7:43 PM

#

The place to go for a docker-compose file is the Frigate docs

#

It will show what you need to configure even if you don't use it as is

charred shell Dec 27, 2024, 7:44 PM

#

night veldt Did you create the container via the stack feature or purely through the GUI? Ki...

I originally created this without portainer and I decided to use portainer as it made managing things easier about 6 months after since then just been using portainer so I don't have to learn as much about docker.

charred shell Dec 27, 2024, 7:48 PM

#

sly monolith The place to go for a docker-compose file is the Frigate docs

https://docs.frigate.video/frigate/installation - searched here and i also did locate and file name on the drive itself and couldn't find it.

Installation | Frigate

Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon. Note that a Home Assistant Addon is not the same thing as the integration. The integration is required to integrate Frigate into Home Assistant.

#

Now my decision to just use portainer is kind of biting me 😦 - should have just learned docker a little more.

#

@sly monolith I made a mistake on saying that the compose wasn't using my directories I setup I read it wrong I see now that /frigate-config directory is mapped in /config so that all appears correct. It something else when it goes to pull the image when it errors that is what caused the problem. However I would like to find where the heck the docker-compose.yml is on my drive and not through my portainer instance.

#

im going to guess if it pull latest nginx or something in the compose then it missing that image or something.

#

something it tried to pull errored out but in the portainer interface it just said error in the upper right hand corner then success.

sly monolith Dec 27, 2024, 7:53 PM

#

As long as you have your config dir, you can just use docker-compose with a fresh docker-compose.yaml and point to it

night veldt Dec 27, 2024, 7:54 PM

#

When you use portainer the compose file, of any, is inside the file system of it. Usually a docker volume.
I ask again. Did you use rhe stack feature of portainer or just the GUI with its dozens of options to set options?

charred shell Dec 27, 2024, 7:54 PM

#

i just used the stack feature

#

clicked on stack, name of stack frigate and then ran recreate and selected the option to pull latest image.

night veldt Dec 27, 2024, 7:55 PM

#

Perfect. Can you share the stack content? By default portainer uses a data volume to store things. It should be in /var/lib/docker. Not really meant to be managed by you though.

charred shell Dec 27, 2024, 8:23 PM

#

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    #image: ghcr.io/blakeblackshear/frigate:0.12.0-beta8
    shm_size: "256mb" # update for your cameras based on calculation
    devices:
      - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
      #- /dev/apex_0:/dev/apex_0 # passes a PCIe Coral
      - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      #- /home/nvradmin/frigate-config/config.yml:/config/config.yml # modify to match your setup
      - /home/nvradmin/frigate-config/:/config/ # modify to match your setup
      - /mnt/storage/frigate:/media/frigate # modify to match your setup
      - /home/nvradmin/frigate-db/:/db/ # modify to match your setup
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1500000000
    environment:
      FRIGATE_RTSP_PASSWORD: "changeme4567" #modify to whatever if using rtsp
    ports:
      - "5000:5000"
      - "1935:1935" # RTMP feeds – comment out if not needed , it may conflict with other containers
      - "554:554" #RTSP
      - "8554:8554" #Birdseye for frigate
      - "8555:8555/tcp" #WebRTC over tcp
      - "8555:8555/udp" #WebRTC over udp

night veldt Dec 27, 2024, 8:28 PM

#

Looks okay to me. Try this. Stop and delete your frigate container in portainer, save that content into a compose.yaml file, run docker compose up in the file's directory and see if it has the same issue. Probably best to save the file first.

#

I also found this:

sly monolith Dec 27, 2024, 8:30 PM

#

Good catch. Friends don't let friends use portainer

charred shell Dec 27, 2024, 8:35 PM

#

This is the exact problem it seems whatever he did here resolved my problem. His screenshots show exact problem I see in portainer.

charred shell Dec 27, 2024, 9:00 PM

#

how do you edit the path variable in portainer

#

I can see it I stopped the container and still didn't let me edit.

charred shell Dec 27, 2024, 9:41 PM

#

well just ran it with docker compose and all is good. It shows up in portainer as healthy now.

#

I searched for way to edit env variable and eventually gave up.

#Frigate Failed to Start