#Running Frigate on separate container
1 messages · Page 1 of 1 (latest)
you can just choose not to expose that port in your container configuration
I can't do that as it's running on an ipvlan on its own IP.
I like to segregate all my containers on their own IP but maybe this is one I shouldn't?
just a random example from the docs, and you can see that port 5000 is commented out: https://docs.frigate.video/frigate/installation/#docker
why can't you control the network configuration for that container?
https://docs.docker.com/engine/network/drivers/ipvlan/
ipvlan gives the container essentially it's own networking, so everything is exposed.