Aha, thanks for clearing that up. Like stephack, it was until this thread that i never took the time to really dive into this info. 
edit: yup, correct. Had a look at the terminal add-on in HA and “ha os info” gives “version: null”. No HassOS indeed, just HA present in docker.
Before running HA on Linux, i had it running on a raspberry pi 4, but it became way too sluggisch and slow to be practical. When i migrated to Linux on a dedicated server, it was like a big breath of fresh air. Wonderful! And, looking at the poll results, i guess that everyone here has had the same experience.
Personally I wouldn’t be too worried about this thread. This thread has already made enough noise and the devs have heard the complaints.
2 Likes
Good to hear. Thank you.
Oh wow, just read the news about this deprection… There should have really been more time to talk about this, also I’m not sure if my deployment is a target of these deprecations?
In the blog entry they talk about “generic Linux installation method” - I’m running debian and a virtual python environment - should I be afraid?
The communication about this was really not good, but hey, we learn from things and next time it will be better 
No it doesn’t affect you. that is an easy question. Pay attention.
docker pull homeassistant/home-assistant
docker stop home-assistant
docker rm home-assistant
docker run ...(as per the install documentation)
Put it in a script.
Going to add my vote here as well. Home Assistant Supervised on Docker is well worth it. Ive run full Hass.io and stand alone scripts. The Home Assistant Supervised setup on Docker was the best middle ground for me for sure.
I am not sure what this even means. What is a “Stand along script”?
I know but it is what the script does which bothers me. Call me old fashion but I find it absurd and inefficient to delete an entire container and recreate it when the upgrade only requires a few files. Sorry I profoundly dislike the container concept. As I said, to me it is a complex solution to a simple problem. It only moves the problem environment dependency from one level to the other: managing the OS dependencies, which is controlled within the container to now managing the complexity of the container manager which is the cause of this deprecation discussion. It is a nice with a GUI, don’t get me wrong but really not optimal or efficient.We end up with a bunch of repeated environments all very similar to one another occupying space on the disk and having to delete them all and reload them at every upgrade which adds wear and tear to the hardware. There are cases I am sure when this is necessary when for example the environment needed is very different from the host but most of the time, it is avoidable. Many I can see are using this for its convenience but I think there are much better ways to achieve the same thing… scripting upgrades and calling them within the UI for example, similar to how the server control menu reload commands are already running.
Then use a venv. Any other solution (hassos or supervised) relies on docker and has the same “problem” you describe.
3 Likes
Like many here I am saddened by this news and hope that the install method continues to be supported.
I run a Debian server for my general nas/Hass/media needs. I appreciate the ability to run these services on a single device.
I could run Core and the equivalent Docker containers to replace the functionality of the home assistant add-ons. But a really undersold feature is ingress. I create my own addons out of generic Docker images just so I can use ingress. I’d hate to lose this feature, in particular, it’s how I access my media server remotely when I’m traveling.
I’ll wait for further news before I make any install changes, but disappointed either way.
1 Like
It was supposed to be “Stand alone scripts”.
Not only that if you go the “recommended” VM path then you not only still have Docker containers to worry about you also add the VM layer to the machine
So instead of "Host OS->docker app->containers" you now have "Host OS->VM app->VM OS->docker->docker containers".
Along with the inherent added complexity of it all.
I just don’t see how running things in a VM helps make things easier or m ore efficient.
1 Like
I completely agree. It’s just an extra layer of complexity.
1 Like
I have proxmox (which is my host-os)->hassos->docker->(supervisor, core, addons)
I have Debian->Docker->Home Assistant(Supervised)
So you have 2 Host O/S’s -
Proxmox (Debian) Hosting the VM running HassOS and you need to manually keep Proxmox updated as well.
I was about to do a supervised install on a new (second hand) computer to migrate my docker/core install to - but the bios wouldn’t boot linux.
By the time I got the bios sorted, the deprecation had been and gone (or held) so I thought I’d try proxmox with hassos. It is OK so far, but not that easy for beginners I think.
2 Likes
I agree particularly when you consider how mindless people can be blindly following guides with no idea what they are doing. There are a few landmines as well - things like checking a VM has a unique MAC address etc. I think the Supervised install was a doddle compared to proxmox. I had a nightmare with my Security program (eset) preventing accessing the console for Proxmox for instance… then the constant security warnings in the browser - and it is not simple making your own CA to stop getting those all the time. Easy when you work it out…
1 Like
Yup, That’s what I did for a few years up until I realized recently that I could get rid of the venv and run directly within the OS. It’s even simpler and cleaner. It just requires to be a bit more careful when upgrading other packages but it has not been a problem in spite of all the other servers I am running within the same VM.
I started with HA on an older computer in 2018 with CentOS 7, using the HA Supervised on generic Linux. It was very easy to setup. The script told me what packages were missing, so I installed them. This was an opportunity to learn about Docker, which wasn’t too hard either.
Two months ago, I replaced all of the computers with a Dell server. It’s running 4 Fedora 32 VM’s and a Windows 2019 Server. The VM’s HAVE NOT added to the complexity. Once Fedora 32 was installed, it behaved exactly like the computer I retired.
I’ve work with Linux for over 20 years, so I am knowledgeable about getting services up and running. The HA Supervised on generic Linux script is a godsend. Please continue to support it going forward. I’m not interested in using a prebuilt, stripped down HA VM.