Is there anyone running Home Assistant in a container?
I noticed that as soon as (actually, about a minute later) I start the HA container on RDS2216 (without even any setup, no mounts, no env variables etc – just add the container and start it right away), the Fasttack becomes inactive in both /ip/settings print and /ipv6/settings print. It gets back to normal when I stop the container. Guess HA does something weird with the network interface. I got about 20 other containers, none of which have this issue.
It behaves the same in 7.19 and 7.20 branches, didn’t try anything older.
Wonder if it is just me or not.
I can post my config, and I will if required / if Fasttrack works for others, but for now I’ll skip it as it is quite long.
I know this is an relative old post.
But I wanted to share what I have learned about this.
If my information is correct, the veth interface that is used by the container cannot be hardware offloaded. It is CPU bound. When you add a CPU bound interfaces to your normal LAN bridge that whole bridge can’t use hardware offloading anymore. That is why fasttrack is being disabled the moment you start the container.
When you stop the container the veth inteface becomes inactive and hardware offloading is possible again.
You mention other containers don’t show this behaviour. My best guess is that the veth interface you use with HA is on your LAN bridge and the other veth intefaces were not.
Maybe someone on this forum can confirm this theory.