@obogle1986 commented on GitHub (Feb 8, 2024):
Just do a find -name command. It should be on the root of /opt if not in your frigate directory
@NickM-27 commented on GitHub (Jan 31, 2024):
make sure that docker is fully downed and upped not just restarted
@obogle1986 commented on GitHub (Jan 31, 2024):
Ah. That did the trick. Thank you.
@Tiotbrev commented on GitHub (Feb 8, 2024):
good evening, can you explain the methodology more precisely please, thank you
@obogle1986 commented on GitHub (Feb 8, 2024):
@Tiotbrev within my docker-compose file, I had :ro (read-only) at the end of my config reference as per the documentation I was following. You can…
@Tiotbrev commented on GitHub (Feb 8, 2024):
@obogle1986 Thank you very much, but my installation is a little old and I'm completely lost I need to modify the configuration file? can you…
@obogle1986 commented on GitHub (Feb 8, 2024):
@Tiotbrev not the frigate config file but the docker-compose.yaml file. I have mine here: https://github.com/blakeblackshear/frigate/issues/9539#issu…
@Tiotbrev commented on GitHub (Feb 8, 2024):
Thanks, I'll look but I can't even find the file anymore. complicated weekend ahead ;-)
@NickM-27 commented on GitHub (Jan 31, 2024):
this behavior has not changed in 0.13. There is a job in frigate that runs periodically to clean up duplicate events like that, just need to be patient
@NickM-27 commented on GitHub (Jan 31, 2024):
it is not stuck, it is generating the TRT model
you have to…
@obogle1986 commented on GitHub (Jan 31, 2024):
Is this the config folder being referred to?
@supermarkert commented on GitHub (Jan 31, 2024):
Got it; Thanks! Relatively new to Frigate, and now playing with 0.13, so I was monitoring it like a hawk during testing... 0.13 gives me much…
@BurningTheSky commented on GitHub (Jan 31, 2024):
Ah ok, why is it generating those for the coral? I thought it used TRT for the nvidia gpus?
@NickM-27 commented on GitHub (Jan 31, 2024):
Yep, feel free to create a new issue if something else comes up
@NickM-27 commented on GitHub (Jan 31, 2024):
yes
@NickM-27 commented on GitHub (Jan 31, 2024):
probably because you are running the tensorrt variant of the docker image and the env variables are set by default
@obogle1986 commented on GitHub (Jan 31, 2024):
The above screenshot shows that it isn't read-only though. What should the permission be? Should I just set it to 777?
@NickM-27 commented on GitHub (Jan 31, 2024):
it is read only and the logs show this as well [Errno 30] Read-only file system: '/config/model_cache'
you need to update your docker compose…
@BurningTheSky commented on GitHub (Jan 31, 2024):
That's it! Removed all that and good to go. Thanks
@obogle1986 commented on GitHub (Jan 31, 2024):
I followed the steps and removed :ro and I am still getting the same thing. I went as far as to change the permissions to the config director to…