Hacker News new | ask | show | jobs
by asveikau 864 days ago
I also use the docker deployment method.

I started out with the VM image, which was a good low commitment "gateway drug" to try it out and get to know it... But a big downside I witnessed is their "haos" distro handles disk failures very poorly. I hit that twice, and recovery was not fun. It basically put up an infinite spinner on the web interface, until I messed with the disk image somewhere else. Haos does not even have fsck.

Now my docker setup runs out of ZFS and I'm happy. There is no update UI or addons but if you're comfortable with a little mild sysadmin style stuff it's fine.

2 comments

I’m also running home assistant in a docker container. The only thing I miss is support for some plugins that need to install extra by components like mqtt. It appears that can be done transparently in the Haos image and is manual in the docker flavour.
You can install HACS into the docker image FYI and it'll persist, which gets you a pretty huge chunk of the HAOS experience.

*EDIT: I meant HACS, HACS is what I meant.

Hmm, I just read about how to do it. I am already running Debian which is one of the requirements. Maybe will look into it later, but for now it seems like more work for not very much gain.

Thanks for the tip.

I have HACS[0] installed in my Docker image, I use it for exactly one integration and the initial setup seemed a little dodgy but it's been pain-free for a couple of years now.

[0]: https://hacs.xyz/

Yeah, I'm using that too..

Interestingly when I migrated from a VM to docker, I copied /config over and didn't need to reinstall HACS. It was still there and working.

Oh, the original comment, before editing, was talking about installing supervisor into docker. Which is much more complex than HACS.
I thought they meant HACS and then mis-typed, but then saw the edit later. Figured I'd link to it anyways since it's a good option for integrations :)