Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Almost all my issues with Python versions went away when starting to use HA in docker container. Everything is very smooth.

One way is also to use HAOS but it is kinda limited.

Current stack for me is HA+traefik+Z2M+Frigate+Mosquitto. All running in containers, on top of Debian. Works perfectly.



How is it limited?

I have been thinking of migrating my setup from a docks container to HAOS on metal.

I have like 1 dozen Intel j5105 boxes, might as well use them.


Limited; as in you might have to find a way to configure some things in a different way than you are used to.

HAOS in a principle is a lightweight immutable distro for running containers; the HA itself is the same container that you would be running if you went the Docker path.

In my case, I have my IoT toys in a separate VLAN; HAOS needed to have access to both, main LAN (for the frontend) and IoT LAN (to talk to the devices). Configuring that meant installing container with SSH, making sure I can connect to the host via that (the featured "Terminal & SSH" addon won't allow that, you need the other, "Advanced SSH & Web Terminal"), and then using nmcli to configure the network.


Thanks for the reply.

I like the concept of paring down and organizing my myraid docker containers into native HAOS "add-ons".

That plus having a better update cycle and less hardware pass through headaches is appealing to me.

I've also been encountering a bug in my docker build pipeline that freezes my ability to remove a container until I restart it. Pretty frustrating.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: