My pet issue of showing it all inside docker…
I have a working supervisor. How do I point it to my existing HA in docker?
and since they aren’t linked then how does HA know to look for a supervisor container to know when to add the hassio functionality or not.
I know that if I delete the hassio container and not disable the supervisor container it will immediately create a new hassio container even tho the other HA container is in the same docker instance and functioning. So the supervisor can’t just be looking for HA in general but a specific “version” (for lack of a better term now).
If nothing else this is at least helping my understanding and it might just help some new person that is helplessly lost.
I’ll admit not knowing that the hassio & non-hassio images were the same so I concede that point.
If the people “in the know” can’t (or won’t…) explain this to someone who has been using HA for over 2 years now then how is a new person going to be expected to understand any of the differences and nuance that is involved?
It’s right on their home page.
Home assistant, all the addons, and the supervisor are all “App[s]” in the sense of the above image.
Perhaps enclosing them all in a “cloud” for docker (as I did) isn’t the most standardized representation, however the image before I modified it implied that only the supervisor communicated with docker, not that HA, the addons, and the supervisor were all running inside docker.
Again, this is just my opinion. We all seems to see and conceptualize things differently. I’m trying to keep in mind what the average “noob” user will understand best; but I’m not him so I can’t really say for sure what’s best.
How about “Hassio on Debian, Ubuntu, etc.” and “Hassio on HassOS” (or just HassOS since “Hassio on HassOS” is in itself redundant)?
“Hassio in Docker” is redundant and not any clearer than just saying Hassio since (as you said) the Hassio install method utilizes Docker regardless of the host OS that it’s installed on (again, Debian, Ubuntu, HassOS, etc.)
Saying “Hassio in Docker” implies there is a method of running Hassio that doesn’t involve Docker, but there isn’t.
This whole thing kind of reminds me of saying ATM Machine instead of just ATM or PIN Number instead of just PIN lol
6 Likes
Wonderful way of phrasing it.
3 Likes
But the front page, and all documentation regarding installation just refers to it as Hassio.
When NewBie123 installs hassio, and has any issues, they come to the forums and just say “I installed hassio and I have issue X”.
Depending on the issue, we might need to know HOW hassio was installed. Sometimes they go on to say “I just installed hassio like the website told me”.
Only the website explains every method of installation even if it doesn’t explain the differences in detail.
So now we’re back to “How did you install it?”.
It’s a vicious cycle. So much repitition around here…
4 Likes
Yes, so it’s just back to improving the documentation on the primary documentation pages to better represent the differences between Home-Assistant, HassIO, and HassOS.
This is something I think we all agree on.
This can all be a PR submitted before 2020.
That’s a fair point, but I suppose the next question could be “are you running Raspbian/Debian/Ubuntu + Hassio or did you just flash the image on an SD card/SSD?” The answer to that question should get you what you need.
I’d also imagine anyone running Raspbian/Debian/Ubuntu + Hassio probably knows that’s an important detail to mention (but… that is merely an assumption after all).
1 Like
Just like it’s also an assumption that everyone is running their install on a RPi, which is where we get back to that vicious cycle of questions that we see SO MANY new threads about 
2 Likes
I actually don’t mind that idea however it’s incomplete no?
Hassio on/in Docker on Debian… Whereas HassOS it’s clear. The actual hardware isn’t important - HassOS is the same regardless of how it’s installed. It’s only hassio that raises questions for more info.
Also very true lol
Yes indeed. Sometimes you might have to distinguish between hassos on rpi, hassos on nuc, hassos on tinkerboard, hassos on rpi4 etc as there are many hassos image builds Installation - Home Assistant
Can someone PLEASE close this thread, it is past it’s use by date. Every poster here knows how hassio, hassos, venv, etc work. This is just becoming a circle jerk.
1 Like
Feel free to ignore it Nick… but this semantic circle jerk has been going on for years so a great discussion about it is useful.
Moved a bunch of stuff here: Hassio containers? / How do version numbers work? where it can be continued…or not. Not would be fine.
And closing this.
2 Likes