I don’t think you’re understanding something; pretty much everything listed as a Home Assistant addon is already available as a Docker Container, since that’s essentially what an HA addon is. Where they differ from the upstream container is in having code that allows them to integrate tightly with the Supervisor component in HAOS.
Wasn’t aware of that repo. Nice.
1 Like
https://www.linuxserver.io/ provides standardized docker configs too.
Yeah except those will unlikely get properly organized, Thsts the entire point of my messages, is for you to make something that’s semi-official, to gather all of those random tweaker, posts, repos, etc in one place that’s recognized to be the main place for this kind of stuff
I don’t think you’ve read my entire message, I’ve mentioned I have NO Virtualization support and Docker is the only way for me on that machine
Without the proper virtualization you can’t have an efficient VM, if any, it will waste a lot of resources and won’t perform well at all even if I do manage to run it there
I’m literally running on a reporposed ARM device, and I clearly stated it was my only option.
Also no, you won’t need “many skills” if there was a proper community repo for this specific purpose, it would make it trivial for anyone except the first person to figure it out
And who said anything about “sample docker Compose”? And don’t you realize you do not need to change anything in your OS. That’s literally the entire point docker exists… Docker does everything inside containers, it doesn’t mess with host OS
Edit: this was meant for Edwin_D, this forum is a bit difficult to work with from a phone
1 Like
Even when I come and literally give you a solution on a silver plate, you keep dismissing a valid approach, no idea how could there be so much ignorance about something so simple and common. I’ll pray that someday there’s a fork of this that actually listens to people who have valid concerns instead of dismissing them like it’s not your problem… I don’t understand why you don’t want docker users to ever have a better life with this, probably because that would decrease your hardware sales, huh?
So besides a link from the ha docs, what are you wanting that isn’t already provided by awesome-selfhosted or linuxserver.io?
I scrolled through the whole thread now to make sure: none of the responses came from the HA dev team. All the feedback is from the community.
1 Like
You know what? I don’t think there is an HA Docs reference listing Custom Integrations either. Just a Community driven Custom Integration that tracks other Custom Integrations. Hmmm…
Maybe because it’s all Community Driven Custom Stuff, not part of the actual HA package.
(All the add-ons, even the ones listed as ‘official’ are not part of core, they are their own things and are not maintained as a part of Nome Assistant…)
2 Likes
Again, people that run Home Assistant via Docker already have access to MORE containers than there are Addons for Home Assistant OS. Most of them are aware that they won’t integrate neatly into Home Assistant and be managed by it, but they don’t care about it.
I decided on the docker installation to avoid even the add ons.
As mentioned several time, all add ons are available as separate container. And I preferer to have a container from the real source instead of waiting that someone is updating a add on (for example vaultwarden or adguard)
1 Like
I took my decision to go with the HA Container fairly lightly. I read the warning, and accepted the consequence (or so I thought), and I had things up and running with discovery, and leveraging the accessible integrations all within an hour.
Coming from SmartThings, my next instinct was to explore the integrations to see if something was there that I had not used in the past, and then I turned to addons, even when I feel comfortable getting all of this running on my own I wanted to see what my options were.
I searched the formal documentation and hit a snag with a screenshot and link back to my environment which dead ended.
Again, I knew what I was getting into with the container path and needing to roll my own additional services, but I thought surely there is no reason to “hide” this, I should be able see the addons and their source to learn more even without being able to install them, and it led me to this thread.
1 Like
–
In the end, I searched the GitHub org repo for matches “addons”
This led me to seeing that the supervisor was using both in code and tests a reference to addons.json which appears to be created by the code underlying https://analytics.home-assistant.io/, a click or two later and I am on the page listing installs/popularity https://analytics.home-assistant.io/add-ons/ but this is still incomplete to find my way back to the source of the add-ons
So I pulled up the code reference, specifically https://analytics.home-assistant.io/addons.json, although this was interesting to see all of the different versions, and install numbers, I still thought “we can do better”. where/how is this file being generated, and this led me to the script snippet
declare addons_path="${PWD}/site/src/_data/addons.json"
a few steps later, now I have something as I stumble across:
Bottom Line, I had to follow this journey all to get a text based reference/listing to the concepts.
It just seems like this could have been easier, by leaving the store functionality “visible” (including custom repositories) even if the installation capability is “disabled”
1 Like
all in all a disheartening read. i felt today its time to fire up my homeassistent. i have a machine that runs 24/7 and that can run containers. so i simply fire up a docker container, right? No. only a core-Container. No addons. From what I know I’m sure I’m going to need some Addons …
so now I have to find another machine that will run 24/7, that will run essentially docker containers and if i don’t want that, I’m all by myself, because I am clever enough to spin up containers? I do things like this for work. At home I want to explore home automation, not containers. So i am not starting HomeAssistant today. bugger. i don’t wanna run this on a raspvberry pi with SD card, because that’s neither fast nor reliable. My Server with lots of RAM and a Xeon processory would have been.
I’m running a lot of other containers alongside Home Assistant. To manage all of them i use dockge. I don’t need several systems for that, it’s only a Raspberry Pi CM4 doing the work.
Not sure what makes you think you need two machines?
This whole thread is extremely unfortunate since the official stance of the matter team is the following:
We only provider official support for Matter when running on HAOS, running it yourself on container is at your own risk.
Reason for this is that we have patched the Home Assistant OS for Thread to work correctly.
So according to the HA community, the docker container is supported because anyone “can just run the addons as additional containers”. But according to the matter team, arguably the most important part of any future HA build, they refuse to support the docker container as a runtime option in all github issues and in their discord.
1 Like
Again, the Linux mindset that says that “I took the time to work it out from first principles, you should too”.
“Whole heartedly agree. Hence why there are warnings ensuring new users know that they will have to be Linux experts to use the container install method.”
That’s fine. What we don’t understand is why the HA developers apparently oppose ANY effort to document using other containers in a pure-docker installation.