I’d say it’s not that trivial and makes you the maintainer of your add-ons. Of course it gives you more flexibility, but you do have to manage them/update yourself.
Yeah, that’s what you put in a compose file, and you shouldn’t care about anything else, port mappings can be read from the Dockerfile if it’s not documented, and if the container was built correctly you shouldn’t care about config files.
I never met a container with 0 documentation. You can read the Doockerfile at least, it’s not magic.
I mean, I can understand why someone want to use HAOS and neber deal with such things, but if someone can set up HA in a container, the second and third container from there is not an unbelivably big step.
The point is that there are hassio addons which do not have any regular docker counterpart, and for the ones that do, there is little to no documentation that gets them actually integrated into the Home Assistant sidebar. They work as their own separate entities and can communicate, sure. Sometimes that is even more desired. What if I want ESPHome as an item in the home assistant sidebar? I have yet to find a guide on how to do that.
How can you get the Home Assistant Google Drive Backup working in docker compose as another example? Extremely useful and only available in HAOS or supervised. Yes there are workarounds and other services, but they are workarounds and other services
Well, moving the goalposts, but exactly, it doesn’t solve the problem at all that I talked about.
Again, it is completely fine if people want separate services, but there is currently seemingly no documented way to tightly integrate services into homeassistent to be able to be used within homeassistant via containers.
Maybe if you’re a deep Linux head, but the rabbit hole of “first do x, which requires y, which requires z, which requires….” Seemed infinitely deep for me, who has only a passing familiarity with Linux.
You don’t like Add-ons?
I’m surprised this still comes up. There’s like one extra step to adding the same functionality.
I’d say it’s not that trivial and makes you the maintainer of your add-ons. Of course it gives you more flexibility, but you do have to manage them/update yourself.
What is the step‽ I am running the container in unraid and want the addon!
Search for the name of the addon on docker hub and write your compose. Addons are just other containers.
Then find exactly what environment variables, config files, port mapping, etc… need to be placed in each container with 0 documentation at all.
Not as simple as writing a compose block.
Yeah, that’s what you put in a compose file, and you shouldn’t care about anything else, port mappings can be read from the Dockerfile if it’s not documented, and if the container was built correctly you shouldn’t care about config files.
I never met a container with 0 documentation. You can read the Doockerfile at least, it’s not magic.
I mean, I can understand why someone want to use HAOS and neber deal with such things, but if someone can set up HA in a container, the second and third container from there is not an unbelivably big step.
https://hub.docker.com/r/hassioaddons/vscode-amd64
https://hub.docker.com/r/hassioaddons/bookstack-amd64
In fact, here are 347 containers with 0 documentation whatsoever:
https://hub.docker.com/u/hassioaddons
The point is that there are hassio addons which do not have any regular docker counterpart, and for the ones that do, there is little to no documentation that gets them actually integrated into the Home Assistant sidebar. They work as their own separate entities and can communicate, sure. Sometimes that is even more desired. What if I want ESPHome as an item in the home assistant sidebar? I have yet to find a guide on how to do that.
How can you get the Home Assistant Google Drive Backup working in docker compose as another example? Extremely useful and only available in HAOS or supervised. Yes there are workarounds and other services, but they are workarounds and other services
I didn’t meant the addon container just a regular container. If you don’t use HAOS, then don’t use their containers, use these instead:
Well, moving the goalposts, but exactly, it doesn’t solve the problem at all that I talked about.
Again, it is completely fine if people want separate services, but there is currently seemingly no documented way to tightly integrate services into homeassistent to be able to be used within homeassistant via containers.
Which add-on?
You must not be talking about HA Core. Because some of those add-on additions are just straight up impossible for Core, as far as my experience.
Which ones? I’m yet to see one and am eager to learn.
https://github.com/sabeechen/hassio-google-drive-backup
And any add-on that you actually want usable from within home assistant. I.e. tight integration like having esphome in the sidebar.
You can just edit the configuration.yaml and it adds sidebar entries.
Node red is the most notable example.
Node Red is perfectly installable
Maybe if you’re a deep Linux head, but the rabbit hole of “first do x, which requires y, which requires z, which requires….” Seemed infinitely deep for me, who has only a passing familiarity with Linux.
Again, I’m talking about Node Red on HA CORE.
Except I can run other stuff that is not provided through addons. But granted; most use cases are covered with addons.