Having trouble with file permissions #2302
Unanswered
djdubd
asked this question in
Ask A Question
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When I attempt to access recordings, I get this message:
I receive this error message seemingly anytime the container is restarted. After a restart no previous recordings are available. The first time it happened, I just cleared out the recordings folder and started over, but today a restart was needed of the docker host, and when Frigate came back up, no media is able to be played back from before the reboot, but I noticed that new recordings were working like expected.
Sounds like maybe an file access issue. Here are some log entries that seem to support that:
When I console into the frigate container sure enough, I can't see the folders from before the restart, which explains why those log messages happened.
Alright, so my setup is an NFS share mounted on the Docker host, then passed into the container. The old recordings are accessible from the docker host, and the permissions look like this:
The folder that holds the file referenced in the log entries looks like this and the file exists:
So the file permissions do not seem to have not changed. Another thing I noticed was that frigate logged that it "created" the recordings and clips folders:
I can see the new recording files from the console on the frigate container, and I can play them back on the web interface, however they are not available from the docker host, in the source folder where they should be.
Did Frigate create the folders/files inside the container because it couldn't find the source volume when it started?
Are there docker host/daemon logs I can look at to help understand what happened on the host when it started the Frigate container and tried to mount the volume in the container?
Beta Was this translation helpful? Give feedback.
All reactions