If you want to keep putting band-aids on things, good luck to you. This will keep happening, you are running unsupported, it’s not going to go away.
You could just move to a supported OS in as little as an hour and not have this issue, but I guess wasting countless hours temporarily fixing things is enjoyable for you.
there is nothing wrong with running supervised on a generic host. at all. i understand why they dont want to support all these distros, but i do not agree. i will continue running the way i want and helping others with the same setup. i am not going to change my entire setup for one application.
Thanks tho
I hope you like being version frozen due to being locked out of updates.
It’s coming.
Was there any userbase stats on how many people were running Ubuntu cf Debian in a supervised role ? Just wondering what impact this is really having. It’s a done deal I realise.
Don’t know why I originally chose Ubuntu - but I’m in the same position now. Too many other things running on my 18.04 LTS install to want the hassle and HA is currently (all band aided up fttb) - still running. I’ve also relegated HA, the picky kid to a Blue for future stability. It’s very own playground and a dual setup currently. I also intend to look at Proxmox
welll, the comments here give a hint.
Why don’t just run in a venv? You can still use your old configuration. That’s what I do on my server where lot’s of other things are running. Never seen any benefit of virtualization
Because a lot of people like that addons etc you can only get with supervised. I personally was happy to leave venv and Python updates well behind me.
That is an old repository…
Debian is actually the father of Ubuntu so you should not change anything and Debian just work very well with supervised version. Thats all.
Ah, I see.
Maybe a silly question, but is not the point of docker to really don’t care about the host os? Maybe this is harder when containers need to be privileged. I otherwise run docker quite some both on private servers and at work. I have never had or heard of any host incompatibilities other than with HA.
Another question. I could Google this of course, but would it be possible to run HassOS or Debian in an LXC (which is way lighter than running a VM)? I mean the full feathered supervised installation with the docker-service. I guess my question is if there is an LXC image of HassOS and if it is possible to run a docker inside an LXC.
On another note. My HA supervisor also always losses privileges after every upgrade. I have to rerun the utility script. I’m running latest version of Debian which is supported. Getting this anyways but so far running the utility script is an easy fix.
The homeassistant docker container doesn’t care what system you run it on, as you say docker containers are system agnostic.
The supervisor container can also run on any system, BUT, the whole point of the supervisor container is to interact with the host system and manage networking and system resources. It therefore needs the host system to be configured in a certain way to allow that interaction. So whilst it can physically run on a system that isn’t so configured, it can’t actually do its job properly and reports it as such with terms such as ‘unhealthy’ and ‘unsupported’ depending on the misconfiguration of the host.
I think this makes sense. As you say the host systems may differ a bit (or a lot). One thing here that I wonder though is why the main problem here seems to be that the container losses privileges. This feels like something that should at least work the same as it intuitively feels like core docker functionality.
Even the ‘debian being supported’ has caveats.
I run a debian vm on proxmox with a supervised install and have never had any permissions (or any other) issues, so I can’t really help much further on that front.