From e7d9b59313d38b163ace22ce5ae16c05263a132b Mon Sep 17 00:00:00 2001 From: Juliafin Date: Thu, 13 Apr 2023 20:48:29 -0400 Subject: [PATCH] Update docs/docs/configuration/live.md Co-authored-by: Nicolas Mowen --- docs/docs/configuration/live.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/live.md b/docs/docs/configuration/live.md index bd86b2242..0bac9b520 100644 --- a/docs/docs/configuration/live.md +++ b/docs/docs/configuration/live.md @@ -99,7 +99,7 @@ If you are having difficulties getting WebRTC to work and you are running Frigat - `network: host`, in this mode you don't need to forward any ports. The services inside of the Frigate container will have full access to the network interfaces of your host machine as if they were running natively and not in a container. Any port conflicts will need to be resolved. This network mode is recommended by go2rtc, but we recommend you only use it if necessary. - `network: bridge` creates a virtual network interface for the container, and the container will have full access to it. You also don't need to forward any ports, however, the IP for accessing Frigate locally will differ from the IP of the host machine. Your router will see Frigate as if it was a new device connected in the network. -You may also expose port 8555 for the container: +If not running in host mode, port 8555 will need to be mapped for the container: docker-compose.yml ```