Hey,
I have a question about My Home Assistant Installation in Docker.
I know, that HomeAssistant Supervised is a Docker Installation, and if I Install HomeAssistant in a Docker Container, it is just HomeAssistant Core without Supervisor.
I have an Ubuntu Server with Docker running, and an HomeAssistant Core Container.
But What is Best Practice if I want to use the features of Supervisor.
Should I Install HomeAssistant Supervised outside my Docker Installation?
Or is there a Way I can add the Supervisor to my HomeAssistant Core?
I found therefore on DockerHub this Container: https://hub.docker.com/r/homeassistant/amd64-hassio-supervisor
But I didn’t get it for what it is? If you can add the Supervisor with this Container, Is there somewhere an How-to?
I’m searching for Some Days now for a Solution, what’s the Best Way to get HomeAssistant Supervised on my Linux Server, preferred combined with my Docker installation.
Some things I need Supervisor for, I can use some other Docker Container.
But I would prefer the Supervised Installation because of The Backup Functionality, an Add-on called IsItWorkday, and the Add-on Store itself.
I hope you can help me and bring me on the right Way how to Do it Best.
If you install Home Assistant Supervised on Ubuntu, the Supervisor will indicate that your system is “unsupported”. You can run an unsupported system but if you encounter a problem, there’s no official support available from the development team, only from the community. Only Debian is officially supported.
If you install it along with other Docker containers, there are some containers that Home Assistant disallows and will indicate your system is “unhealthy”. Similarly if Home Assistant doesn’t have complete control over the docker system, it will report it as “unhealthy”. When “unhealthy” it will block all upgrades to Home Assistant and prevent installing/upgrading Add-ons.
I run a test supervised install on Debian 9 and have over 30 containers running not installed by the supervisor (I have 0 installed by the supervisor) and my system doesn’t report as unhealthy, just as unsupported and I’ve never been blocked from an update.
I can’t speak to the “some containers” statement but I’ve never run into that yet either.
Some containers will also conflict with the operations of the Supervisor, if you run any of those your system will also be marked as unhealthy. These containers will be shown in the Supervisor log as errors.
It does not appear that running Supervisor itself as a docker container is something HA or the community choose to explicitly support. If you can install Supervisor on linux, you can “easily” (depending on your linux & container familiarity) install it in a container. You would be exposing the Docker Sock directly to the Supervisor container so that it can orchestrate the other services running alongside it (other containers). This is different than DinD, and is done for many reasons in some SaaS app backends as well as edge devices, but it’s not a perfect abstraction here.
I was searching to see if it was supported, as it would be the easiest path for me, personally. Since there is no official Supervisor image you can be pretty sure it’s not a well-trod path :). As a result, I’ll probably install Supervisor (and docker) using LXD, which is easier (for me) to manage than another full VM.