@github-actions[bot] commented on GitHub (Mar 23, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@gnlgrim commented on GitHub (Feb 17, 2024):
@NickM-27 I am on 0.13. It refused to start with the config you posted. I had to add it like this
/dockershare/frigate/config/config.yml:/config/co…
@NickM-27 commented on GitHub (Feb 17, 2024):
it would be best to figure out why, if I had to guess it is because of the database existing in both places. There is a reason that the docs…
@briodan commented on GitHub (Feb 21, 2024):
it would be best to figure out why, if I had to guess it is because of the database existing in both places. There is a reason that the docs…
@NickM-27 commented on GitHub (Feb 21, 2024):
The initial problem that they tried to fix in 0.13 was that the database used to live under the media folder, with the introduction on network…
@blakeblackshear commented on GitHub (Feb 21, 2024):
You also still have full flexibility to put the config file and the db wherever you want. All that changed was the default location. You can…
@briodan commented on GitHub (Feb 8, 2024):
issue looks to be related to the config folders. my config folder is on a network share and i used to bind the full folder instead of just the config…
@NickM-27 commented on GitHub (Feb 8, 2024):
the ability to store the database on a network share but that looks to not be the case at least for me.
The change was done so that users would not…
@briodan commented on GitHub (Feb 8, 2024):
the ability to store the database on a network share but that looks to not be the case at least for me.
The change was done so that users…
@Zetto12 commented on GitHub (Feb 8, 2024):
I had this problem as well. I eliminated
and it now starts. I have lost…
@NickM-27 commented on GitHub (Feb 8, 2024):
@Zetto12 at the very least you should include your logs so others can see
@gnlgrim commented on GitHub (Feb 17, 2024):
@briodan /dockershare/frigate/config/config.yml:/config/config.yml
This saved my life. I do not know why this is not documented in the notes.…
@NickM-27 commented on GitHub (Feb 17, 2024):
that is incorrect and will cause issues in 0.13, the entire config directory needs to be mapped. In your case it would need to be
`/dockershare/fri…
@traxx34 commented on GitHub (Feb 3, 2024):
I had this problem as well. I eliminated
and it now starts. I have lost the birdseye view…
@repomanz commented on GitHub (Feb 2, 2024):
changing to 416 fixed the issue. Working object detection again. Thanks for pointing out my error in the config.
@repomanz commented on GitHub (Feb 2, 2024):
logging into console of the frigate container:
:
I also had this problem. I ended up deploying a new container with new storage directories. Started it with the dummy config from https://docs.frigate.v…