I’m going to be migrating my setup from HAOS native on a raspberry Pi 4 to a docker container on a NUC.
I currently run the MQTT addon as my broker inside HA.
In the backup/restore process between devices will this move over?, do I need to reconfigure it/add it inside HA once again? or am I better off running it as it’s own container on Docker inside the NUC, if the last one is there any easy way to lift/shift all config and devices?
No. Container installs do not support addons.
I run HA in docker and my MQTT setup requires a separate docker container. It has worked well but as said the docker version of HA does not support add-ons so anything you needed an addon for you will now require another way.
Why?
Why not use HAOS native X-86 on the NUC and save yourself all the aggravation of using Docker at all? Then backup backs up everything- you don’t have to back up individual Docker images.
I moved from a docker container to HAOS on a RPi just for the addons. But you can probably use an LXC container instead of docker. That way you can install full HAOS as a container. LXC containers are like a middle ground between docker and a full blown VM that requires dedicated resources…
The NUC is reasonably powerful and dedicating it all to just HA is most likely a waste of it’s power.
I thought using Docker would be a simple enough solution and I wouldn’t paint myself into a corner giving up the whole machine to HAOS.
Add on wise I only really use, DuckDNS, MQTT and Google backup, all of which as far as I can tell can be run on in their own anyway.
Ad blockers and VPN I run on my router as I run Asuswrt-merlin.
Yes I like the simplification of just HAOS but may want more in the future, still not sure.
When you have Frigate running eight cameras, you will want a dedicated server. I just don’t want the aggravation of yet another layer of complexity (I.E. something else to go wrong) between my home and Home Assistant.
If you want to use your NUC for other things too then install proxmox, plus HAOS on top. You can VMs or LXCs for other stuff.
Yeah over the weekend I potentially came to this conclusion as well.
Proxmox allows me to split the box up and run different VMs on one box but HAOS as a full install so addons etc.
There is a howto in the community guides.
Yep that’s the one.
I have just recently moved from HA on a Pi to a NUC.
The NUC runs Proxmox with HAOS in a VM.
Following the above mentioned guide I had no issues to get HA back up an running.
I am now wondering, if I should move some of my addons out of the HA instance to run as separate LXC container. Such that these services continue to run, even if HA is being updated, or restarted.
Is there any guide on how to move the MQTT Broker from HA Add-On to an LXC.
Can the settings be migrated, would the home assistant mqtt entities be affected by this?
I’m an IT guy so I have a little more experience than the normal end user.
My install is on an intel thin client with Linux and I docker on top. Ha core, mosquito, mariadb, node red, everything with its own container.
My thin client has 4gb of ram so I must use it sparingly.
The pros are an optimal use of the resources (ram and disk the primary ones) and the ability of managing avery single service by itself, not having to rely on the maintainer to be able to install a specific version of some software.
I make consistent backup with application and bare metal tools to my home nas.
The cons are more complexity in general and the need to manage the compatibility matrix for all the services and for docker itself.
I usually update the os every week and the containers every 2/3 months .
Reverting a container update is usually a matter of changing a container name in a script.
If I had a more resourceful host I may go with virtualisation, with the main objective of having a snapshot based backup.
