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

How is the container version crippled?

An anecdotal data point, but I've been running the home-assistant container image on k8s without any issue, and I have a lot of integrations.



Same here. Running on a pi 3 with nodered, both in docker containers. Works perfectly and reliably with hundreds of entities, numerous automations, etc. Just make sure you have an official pi ac adapter and boot off an SSD drive not SD card otherwise you will have problems.


You can't run HACS, supervisor mode, Kelvin-sun matching plugin ...


I'm running HACS in the container release right now, it's worked for a long time. So long as you have your HA configuration folder as a volume etc it will preserve across restarts/upgrades.

I'd go as far as to argue the (officially supported!) container release is the best way to get a production quality install of HA - containers are a great way to package and release complex web apps like HA. Mines automatically updates itself every time new container image released, has done so with no intervention from me for over a year. With the container lifecycle/config, you don't really need Supervisor mode either.

To say it is crippled is nonsense, it is literally one of the two officially recommended install paths:

> https://www.home-assistant.io/installation/

Official support for Docker release in HACS:

> https://hacs.xyz/docs/setup/download#home-assistant-containe...


Totally agree. I use the docker containers and persistent volumes and works great. No loss of function,.


HACS works in a container, or is there specific functionality of it that doesn't work? I've been using it inside a Docker HA container on a Pi without issue.




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

Search: