@scstraus I don’t believe a time frame was given…
Nevertheless, there is progress, the architecture proposals are open, discussed, being finalized, and can be seen here:
3 Likes
Thanks, as long as it happens at all, I’m happy. No rush.
1 Like
Great news,
though I dont understand one thing, in this post you say supervised is supported, but in the community guides under supervised on ubuntu/debian basically the first thing it says is unsupported method.
If you are referring to @kanga_who’s guides, they do not fully comply with the “supported” version of supervised addon, as they install ssh, portainer and samba on the operating system, rather than as addons. Having said that, no one has ever had a problem that @kanga_who or I are aware of.
1 Like
I am still confused. I have installed Home Assistant in Docker (running on Ubuntu Linux). But I do have the Supervisor panel.
So is that Home Assistant container (as I did install it in Docker) or Supervised (as it is installed on top of Linux, and I do see the Supervisor panel)?
The Info panel says it is installation_type: Home Assistant Supervised. So I suppose this is what this is.
Supervised
That method uses Docker.
1 Like
Then you installed a supervised installation into docker, rather than just running home assistant core in docker like this https://www.home-assistant.io/docs/installation/docker/
1 Like
If you have the Supervisor you either have HA Supervised or HA OS. Given you installed on Ubuntu, you have Supervised.
You can actually see the installation method under Developer Tools > Info > System Health.
Many thanks for keeping Home Assistant Supervised. 
1 Like
The only one reason why I’ve using Home Assistant Supervised, because there’s no docker config for HA with supervisor. Having addon store is really needed for me (and the confort of it). However to use a full VM is soo inefficient in my point of view (both in time and resource). If I need to restart the machine or something happens I don’t want to wait until 2 OS boots up and then HA starts, especially when I build around HA it’s a huge key to have up and running in the shortest period of time. At the end it’s really good that it will stay around this installation method, at least until there will be some easier install for HA + supervisor in docker.
FYI, Supervised uses Docker. You don’t install it in Docker.
Yes, I know it using Docker, but I was not able to install them like an Apache + MySQL + PHP bundle (same container or separate) for instance. I’ve run the scrip which seems like does something like I wanted and some additional thing.
Thanks also from me that the Home Assistant Supervised (HA-S) configuration remains supported. But I have to say, I remain confused.
I carefully read all HA update bulletins, but was caught out because updates to Supervisor are not included in those bulletins. Yes, I should probably have known better by monitoring the forums, but there must be plenty of other people who had no idea that HA-S was deprecated, then put back again.
I would love it if the HA devs could include notes relevant to Supervisor in the HA update bulletins. It would be very helpful. I know that the release cadence is different (and automated), but I don’t think this is a reason not to provide updates.
I would also like to know whether my HA-S build is only temporarily supported by stay of execution, or whether it is for the long term.
I am running HA-S on a Debian 10, built on an Intel NUC. I got a shock yesterday when I saw a new message in the Supervisor log saying that I was running in an unsupported environment. After carefully studying ADR-0014, I discovered that I didn’t have docker configured for journald logging. I was able to fix that, and now I don’t get the error message any more.
I don’t have any obsession about staying with an HA-S build, but when I initially built my NUC, this appeared to be the most straight-forward, well documented way to get going. Still today, I can’t find a better supported installation for an Intel NUC with NVME system drive (there are some hackish looking workarounds, but not much more).
I don’t love building a OSs for fun. I’d really appreciate not being caught out again. Some better communication would help.
Do you have a succinct howto for that, or a page to point to? @kanga_who should probably include that point in his howto (if he hasn’t already).
I think this is the same. @mjoshd posted it in the Debian guide. I’m in the process of testing it in a Vanilla Debian VM to see if I can follow the ADR14 rules to make the guide 100% compliant.
# open/create a file with nano
sudo nano /etc/docker/daemon.json
# insert the following content then save (ctrl + s) and exit (ctrl + x)
{
"log-driver": "journald",
"storage-driver": "overlay2"
}
# restart docker
sudo systemctl restart docker
# wait ~10-15 seconds then restart Home Assistant
sudo ha core restart
Sorry @nickrout - what @kanga_who said. Note that my “out of the box” docker install already had the storage-driver set to overlay2, so I didn’t include that line in the daemon.json file.
If you’re not sure how your docker is configured, just run a docker info:
$ docker info
Client:
Debug Mode: false
Server:
Containers: 19
Running: 16
Paused: 0
Stopped: 3
Images: 17
Server Version: 19.03.12
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: cgroupfs
...
They’ll just change something again to shaft that concept 
.
The only 100% compliant way, is their way (ie HA OS).
4 Likes
Untrue. Stop spreading FUD.
The script sets this as the default config, so there should not be a need to do this anymore https://github.com/home-assistant/supervised-installer/blob/928e46db76912daaee8bf1eb3b8fd1f9af95ce5c/installer.sh#L49-L50
1 Like