HAOS on Debian and Apparmor. Docker fails. Gurus needed

Configuration
1

Followed the unsapported the installation path. Everything is fine and working. Until i decided to remove apparmor. Upon doing that container ls showed nothing. Wen through the internet. Found out that the cause might be because of snapd. Installed apparmor and snapd back. Now the containers show up (xx in id brought intentionally)

sudo docker container ls -a
CONTAINER ID   IMAGE                                                      COMMAND                  CREATED        STATUS                      PORTS                  NAMES
9ff5dc9xx435   homeassistant/amd64-addon-mosquitto:6.0.1                  "/init"                  39 hours ago   Exited (129) 36 hours ago                          addon_core_mosquitto
8772568xx4c0   ghcr.io/home-assistant/amd64-hassio-multicast:2022.02.0    "/init"                  39 hours ago   Exited (0) 36 hours ago                            hassio_multicast
745a95xx620c   ghcr.io/home-assistant/amd64-hassio-audio:2021.07.0        "/init"                  39 hours ago   Exited (0) 36 hours ago                            hassio_audio
2d1abxx74a8a   ghcr.io/home-assistant/amd64-hassio-dns:2021.06.0          "/init"                  39 hours ago   Exited (0) 36 hours ago                            hassio_dns
00910xx37bc1   ghcr.io/home-assistant/amd64-hassio-cli:2021.12.0          "/init /bin/bash -c …"   39 hours ago   Exited (0) 36 hours ago                            hassio_cli
f44c1xx58834   ghcr.io/home-assistant/qemux86-64-homeassistant:2022.3.4   "/init"                  42 hours ago   Exited (0) 36 hours ago                            homeassistant
d5594xxf354d   homeassistant/amd64-addon-zwave_js:0.1.54                  "/init"                  42 hours ago   Exited (0) 36 hours ago                            addon_core_zwave_js
812f6xxd4a85   esphome/esphome-hassio-amd64:2022.2.6                      "/init"                  42 hours ago   Exited (129) 36 hours ago                          addon_a0d7b954_esphome
8706xx7cc10c   zigbee2mqtt/zigbee2mqtt-amd64:1.24.0-1                     "/init"                  42 hours ago   Exited (129) 36 hours ago                          addon_45df7312_zigbee2mqtt
bba9dxx6fca7   ghcr.io/hassio-addons/node-red/amd64:11.0.4                "/init"                  42 hours ago   Exited (0) 36 hours ago                            addon_a0d7b954_nodered
85d6axx93535   homeassistant/amd64-addon-configurator:5.3.3               "/init"                  42 hours ago   Exited (0) 36 hours ago                            addon_core_configurator
ffd2exx4d5cd   ghcr.io/home-assistant/amd64-hassio-supervisor             "/init"                  44 hours ago   Exited (0) 36 hours ago                            hassio_supervisor
cdf5dfxx99dc   ghcr.io/home-assistant/amd64-hassio-observer:2021.10.0     "/init"                  3 weeks ago    Up Less than a second       0.0.0.0:4357->80/tcp   hassio_observer

But they don’t auto start. And trying to start them manually gives this

$sudo docker run -d --restart unless-stopped hassio_supervisor
Unable to find image 'hassio_supervisor:latest' locally
docker: Error response from daemon: pull access denied for hassio_supervisor, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

How can this be fixed?

2

Are you trying to run Home Assistant Supervised?

It is impossible to tun the HAOS operating system on the Debian operating system unless you are running it within a virtual machine. An operating system needs to be installed directly on the hardware or in a VM.

Home Assistant Supervised is on ly supported on a vanilla Debian installation. Removing AppArmor makes it unsupported except by you. If removing AppArmor broke it, try reinstalling that. Adding any other software services to the same OS also makes it unsupported. This compromise was reached after it was announced that the Supervised option was going to be removed.

1 Like
3

I have a dedicated VM Debian 11 on top ESXi which is running the semi supported installation. Chose it vs the pure HAOS on top of esxi as it has a finier control over networking and USB device (rteally don’t know how to write a udev rule in pure HAOS)

As i have stated i have reinstalled apparmor. Got my containers back. But i’m unable to start them

4

In case someone stumbles the same issue:
Just issue dpkg -i homeassistant-supervised.deb
The configs will stay intact and everything will get back

2 Likes