Your comment got me thinking... Is this a big deal, or even a small deal?
I think it's a deal of some proportion. If someone is trying out Linux for the first time and stumbles across how Flatpaks work and starts exploring Flathub, maybe their initial impression will be good enough to consider switching. If something appears to be polished, then maybe it is.
It was a typo in my compose file. Oops!
Wow. What are the chances?
Nice! I'm just getting a blank screen at http://myip:20211 after installing it with docker compose. I'll try again later and see if I can figure it out.
Looks like OP might need SFF-8482 type connectors?
Interesting. I'd be interested in hearing other people's experience with this. Is this BBR stuff enabled by default on any distros?
I have 2 Amcrest cameras. One PoE that's super solid, and an inexpensive WiFi camera. I ended up buying another wifi access point just for the camera, and ever since it has been very solid. More a symptom of my house having tons of IoT devices than a problem with the camera, really.
I don't know anything about Blink, but for self hosted camera stuff, Frigate is wonderful.
Does it work after a reboot? I vaguely remember having this problem on my old motherboard. Adding a PCIe LAN adapter and switching everything over solved it for me. Now I have a new mobo and it doesn't have any network problems.
For my setup/workflow, individual containers don't get static IPs, but the machine that they run on gets a static IP. Docker is running on some sort of machine (either bare metal or a VM) which gets a static IP in my router's settings.
I think the default firewall rules allow all VLANs to talk to each other, so you have to add a rule to prevent that.
This traffic will go through the CPU (I think), so benchmarks are heavily dependent on hardware.
If traffic on two different VLANs needs to talk with high throughput, you might ask yourself why they're on different VLANs.
I have 2 cameras on their own VLAN and they're only allowed to talk to my NVR. The amount of traffic is pretty low and the CPU use is negligible, so I haven't bothered to put the NVR on that VLAN.
I think the docs recommend (and this is how I have it set up) leaving the go2rtc stream as you have it currently, and changing the stream path for the camera config to
rtsp://127.0.0.1:8554/nursery