Update not possible; installation of addons failed - an unsupported installation

Installation
1

Hello dear community,

first of all I wish you a happy new year!

My HA including supervisor is running on a Docker.
On the host I run OpenVaultMedia.
This is just an introduction.

Now I bought the SONOFF Zigbee USB stick and wanted to run this, unfortunately “Zigbee2mqtt” can not be installed. The following message appears:
‘AddonManager.install’ blocked from execution, system is not healthy

Have also noticed that Supervisor can not be updated

Under “Supervisor” → “System” I also get some messages displayed under Supervisor which are:

“You are running an unsupported installation”

when I click on “learn more”:

DBUS
Docker Configuration
OS Agent
Network Manager
Systemd
Operating System

DBUS-Deamon is running on my host, I already checked that.

In the file: /etc/docker/daemon.json I have also already added the following entry:

{
“log-driver”: “journald”,
“storage-driver”: “overlay2”
}

I installed the Network Manager briefly, but uninstalled it again. After the installation I could not reach my containers as usual under their IP address.
After uninstalling everything ran as usual.

I would be really grateful if you could help me. I have the possibility to install HA on a RaspberryPi 3, but I prefer to install it on my server, because I use it anyway.

Kind regards

Attached the log of Supervisor:

2

How exactly did you install this?

Home Assistant Supervised or Home Assistant Container (with an erroneously installed supervisor container - this is not supported).

3

thank you for your answer

2022-01-01 13_18_19-Portainer _ local
2022-01-01 13_18_19-Portainer _ local1263×815 80.5 KB

attached a screenshot of my container.

I wouldn’t mind reinstalling HA including supervisor as long as I do it clean and on the server.

How do I install HA cleanly under Docker as a container?

4

You didn’t answer the question. Are you running a Supervised or Container install?

5

I would be happy to answer them if I could understand them.

I have downloaded HASS.io and installed it. Quite normally, as if I install any other software. I guess it was a guided installation, because I then had to enter the ip address and do the “initial setup”. Is this, according to your understanding, a guided installation?

6

So, which instructions from here, did you follow?

7

this one:

However, I’m a bit confused right now, because I think this only installed HA WITHOUT supervisor and (if so) I went another way, but through the official support site.

EDIT:
stop.

have not relaized it via the input console, but if then under docker-compose

8

Then you have installed Home Assistant Container.

This does not have a supervisor or addons.

No idea how you got those containers.

9

ok, unfortunately it is no longer comprehensible for me.
I only know that I installed HA at that time (probably via the way the support page describes) and noticed (as you described) that I could not install addons and use supervisor.
So I guess I followed a guide (not from the support page) that described how to install HASS.io in a Docker container.

It’s my fault, sorry.

But in other words, can I somehow run HA WITH supervisor in a Docker container?
I don’t want to put HA directly on the host, because I run OpenMediaVault there and this is the priority.

10

Go to Configuration > Settings > Info

Under System Health, what does it report for “Installation Type”?

In the example below it reports “Home Assistant Supervised”.

Screenshot_20220101-110044~2

11

Hassio has not been a thing for two years.

12

2022-01-01 17_16_28-Window
2022-01-01 17_16_28-Window612×948 48.7 KB

attached the screenshot.

sorry, I do not want to seem rude and I am very grateful for your answers.
but, what can I do with this answer now?
“No thing” means: does not work for two years?
or
sure, since two years it is pretty easy to install as Docker container.
or
Hass.io is obsolete since two years, better use xy

these answers leave quite a lot of room for interpretation :frowning:

Because I’m slightly confused, because if I had proceeded according to the support page, you yourself write that it would have been only the core version, with which you can not install addons and no supervisor runs.

As mentioned, I would also delete the containers and reinstall HA with supervisor (i.e. in a new Docker container). But unfortunately I don’t know what instructions to follow. Not that I can really only use the core version later.

again… please forgive, I don’t want to seem unfriendly or ungrateful

13

Have a read of this (note the date).

You are running Home Assistant Supervised. There are some very strict requirements for this.

What type and version of Linux are you using?

14

If a system is “Unhealthy” it will be prevented from upgrading Home Assistant (and you can’t install/upgrade Add-ons). We have to fix that first. Click the link named “Mehr info” to get more information for why your system’s health (Gesund) is considered to be Unhealthy.

15

ok, after clicking on the further information i am then redirected to the area i described in the opening post, subsequently a list appears which things need to be fixed (also described in the opening post).

I have now understood the new designation. Thanks for the link.

Question, since I am noticeably not so well versed:

How can I run HA with Supervisor on Docker so that the system works?
Again… I would like to install the system CLEAN.
Is the operation at all possible with supervisior in the container?

16

You have to fix everything shown in the list that makes your system Unhealthy.

Did you ever install os-agent? It was announced a few months ago and is necessary for the proper operation of Home Assistant Supervised.

Follow the installation instructions in the official documentation.

17

thank you very much for your answer.

to follow the red thread now:

I now uninstall (delete) under portainer all docker containers that have something to do with homeassistant (see screenshot of the container volumes).

Then I proceed according to these instructions:

Docker-Compose section.

when i have completed this successfully, for i check out the installation instructions from GitHub:

But now it says in the installation instructions of os-agent:

sudo dpkg -i os-agent_1.0.0_linux_x86_64.deb

Note: Replace the deb file in the above example with the file you have downloaded from the releases page.

how do i get the correct filename?
because i only enter the following in docker-compose yml:
“ghcr.io/home-assistant/home-assistant:stable”

and don’t download a .deb file from the release page

now the important question that has not yet been conclusively answered:
If I follow the instructions on the linked support page, is homeassistant automatically installed with supervisor? So I could theoretically also install addons?

18

OSAgent needs to be installed on the HOST not in a docker container.
You need to download it from Releases · home-assistant/os-agent · GitHub and install it on the HOST.

19

this is exactly how i understood it, but the installation instructions refer to the supposed “deb.file” that you have to specify. Consequently, the naming of this file, the link to docker and host.
But, what if I have not downloaded a deb file before, but only triggered the installation via the yml command (see my last answer).

which filename do i specify then?

I have not written anything else

20

You HAVE to download the deb file DIRECTLY on to the host and then install it. It has nothing to do with docker.

Quite literally:

curl https://github.com/home-assistant/os-agent/releases/download/1.2.2/os-agent_1.2.2_linux_x86_64.deb
sudo dpkg -i os-agent_1.2.2_linux_x86_64.deb