…in lack of a better word. It should be fairly easy to make an official installation script. A lot of people are using ttecks (rip!) installation script and run into various problems.
Would be cool with a official installation script.
Create an LXC template with docker in it, run HA in docker, problem soved.
Most people would like to run HAOS.
9 Likes
like @saltf1sk mentioned, you can run HAOS. I’ve been running HAOS in a proxmox VM for a few years now.
Plus you can create snapshots before updating/upgrading so you can revert back if needed (I haven’t used the backup feature of HAOS because of this reason).
AAMOF, I reverted a snapshot Tuesday night because ZWaveJS was having issues after an update. A simple shut down, revert, and power up and I’m back in action.
Backups are important, too. Snapshots are not backups. 
Same deal with LXC, even better, because snapshots are just ZFS volumes, you restore separate files rather than the whole VM image.
But for the love of god, if you are already running proxmox why you need HAOS?
Depends on how big noob you are. I kinda am. I’m doing that 
I’ve installed Z2M as LXC much later, which was a totally new concept to me, comparing to the “good old” VM idea.
Some of us prefer to run services outside of HAOS
Why use haos if you will be running services outside haos?
Haos is meant to simply the whole adding services process but is limiting. If you can roll your own why bother with it?
Because updating Add-Ons is just a click in HAOS, and we can expect the Updates to work without much manual work. Updating software manually can be a pain, especially if the LXC container is based on an older OS-version. F. ex. for somebody else I installed Z2M within an LXC several years ago, using the then “newest” Debian image. Now I can’t update without spending a lot of time creating a new container where all the required dependencies are available. In HAOS it’s just a click every now and then.
1 Like
Literally every single useful app is distributed in containers now, the underlying OS does not matter to a certain degree (unless it’s like 10 yo). No need to mess with system libs.
There are also nice guis like potrainer and others, but I just prefer good’ol docker -c myserver compose up -d.
@saltf1sk I use HA on Proxmox for years and actually it is very well supported since I use the HAOS VM and THIS is an official install option.
There is even a Helper Script I use to install the HAOS VM in this link Proxmox VE Helper-Scripts.
2 Likes
It’s the usual problem - somebody needs to develop and support that. Few people are willing to invest the time involved in long term support, not helped by all the frustration that comes with people that yell at you because it “doesn’t work”.
1 Like
That’s true. But I chose to use LXCs directly, as it’s the built-in method Proxmox provides for containerization. To me, nesting a (Docker) container within a (LXC) container, though possible, kind of defeats the purpose. And with LXC it’s just not as easy as restarting a Docker container using the :tatest tag. Hence it’s more work than an add-on in HAOS.
Couldn’t that be stated for all installation methods though?
Yes. However somebody is already supporting the current options - whether a core developer or the community (in the case of Supervised).
Because it is simple, it is well known, and it is almost the same as running it on a pie.
I only use Proxmox so I can run another server on the same HW, and still only have one box on the shelf.
And I want to spend most of my time with my wife and kids, a little time on automating the house. And not on learning advanced use of LXC, ZFS and containers.
2 Likes