Updated based on feedback

This commit is contained in:
Nitin Gupta 2024-06-21 15:28:24 +02:00 committed by GitHub
parent a469a0ab6d
commit dd5aff516a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -58,15 +58,34 @@ If MQTT isn't working in docker try using the IP of the device hosting the MQTT
This is because, by default, Frigate does not run in host mode so localhost points to the Frigate container and not the host device's network.
### Where can I find the log files generated by Frigate?
### How can I view the Frigate log files without using the Web UI?
Frigate doesn't store log files directly. Instead, it uses Docker to manage logs. To view these logs, follow these steps:
Frigate uses Docker to manage logs. So to view these logs from the CLI, follow these steps:
* Open a terminal or command prompt on the host running your Frigate container.
* Type the following command and press Enter:
```
docker logs -f frigate
```
This command tells Docker to show you the logs from the Frigate container.
Note: If you've given your Frigate container a different name, replace "frigate" in the command with your container's actual name. The "-f" option means the logs will continue to update in real-time as new entries are added. To stop viewing the logs, press `Ctrl+C`.
Note: If you've given your Frigate container a different name, replace "frigate" in the command with your container's actual name. The "-f" option means the logs will continue to update in real-time as new entries are added. To stop viewing the logs, press `Ctrl+C`. If you'd like to learn more about using Docker logs, including additional options and features, you can explore Docker's [official documentation](https://docs.docker.com/engine/reference/commandline/logs/).
If you'd like to learn more about using Docker logs, including additional options and features, you can explore Docker's [official documentation](https://docs.docker.com/engine/reference/commandline/logs/).
Alternatively, when you create the Frigate Docker container, you can bind a directory on the host to the mountpoint `/dev/shm/logs` to not only be able to persist the logs to disk, but also to be able to query them directly from the host using your fav log parsing/query util.
```
docker run -d \
--name frigate \
--restart=unless-stopped \
--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 \
--device /dev/bus/usb:/dev/bus/usb \
--device /dev/dri/renderD128 \
--shm-size=64m \
-v /path/to/your/storage:/media/frigate \
-v /path/to/your/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-v /path/to/local/log/dir:/dev/shm/logs \
-e FRIGATE_RTSP_PASSWORD='password' \
-p 5000:5000 \
-p 8554:8554 \
-p 8555:8555/tcp \
-p 8555:8555/udp \
ghcr.io/blakeblackshear/frigate:stable
```