I’ve been running Unraid and HA in a container for a year. I’m no Linux or HA expert. I just saw some comments above about high amounts of writes on SSDs and missing bluetooth dongles and I would like to share my experience.
@MagicMountainMan Unraid uses btrfs for its cache pool. I was running two NVMe in RAID1 and I too saw high amount of writes. At first I thought it was CoW enabled for docker.img, but no - system and domains shares have it off. However, it is enabled for appdata where HA db is located. I think the issue is btrfs pool specific. I have converted/balanced the pool to single mode. I do see less IO, but still higher because of CoW on appdata. I hope kernel 5.5 in Unraid 6.9 will fix that.
@dedi I’ve tried to pass bluetooth dongles to my docker container. Unfortunately, Unraid kernel have explicitly removed all bluetooth drivers/firmware. Even though the device is visible it cannot be started. I have read somewhere that the host OS should support the device in order to be available in the container. I have no idea if this is true also for qemu and VMs. It looks like it is a problem for you.
I have ordered five ESP32s to convert them to ESPHome bluetooth-MQTT hubs. and forget about native bluetooth support
I’m still thinking, if I need a VM with HassIO for the great plugin integration or should I stick to a simple container.
I hope my ramble helps some of you.