You are running an unsupported installation.

[Actpohomoc]

I have my Hassio LXC container on zfs proxmox local drive.

After update to the Home Assistant 0.114.4

Version 235
Latest version  235

There is this info: You are running an unsupported installation. Learn more

Also I can see in log:

20-08-31 11:33:24 ERROR (MainThread) [supervisor.docker] Docker storage driver aufs is not supported!
20-08-31 11:33:24 ERROR (MainThread) [supervisor.docker] Docker logging driver json-file is not supported!
20-08-31 11:33:24 INFO (MainThread) [__main__] Setup Supervisor
20-08-31 11:33:24 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-08-31 11:33:24 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-08-31 11:33:24 WARNING (MainThread) [supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-08-31 11:33:24 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager

Is it possible to do something with this information and log errors? Or I have to recreate lxc container? Is it possible because of zfs drive?

[WARNING] Some containers may not work properly due to ZFS not supporting 'fallocate'.

[codedmind]

As of today, i'm having the same message because of networkmanager Supervisor 249 unsupported instalation, Network Manager

[codedmind]

@whiskerz007 sorry, how can we "solve" the issue when the installation is already done?

[whiskerz007]

@codedmind The code being produced is to create a new LXC container with Home Assistant functioning inside. Maintaining already created LXCs will be a lot more complex and require a lot more considerations. The decision has been made to be concerned with only creating the LXC and setting up Home Assistant, since LXCs are easy to dispose of. A great deal of effort has been made to ensure readability of the code. The code for configuring NetworkManager is altogether. Please understand that other considerations of how the LXC was configured were made to ensure proper functionality.

[Actpohomoc]

Thank you

[tomcassi]

As of today, i'm having the same message because of networkmanager Supervisor 249 unsupported instalation, Network Manager

I created a new lxc container yesterday and I’m still seeing the same message.

[whiskerz007]

This is a known problem. According to any documentation I can find, the script is properly configuring NetworkManager but the supervisor isn't resolving to a functioning state. Any assistance is welcome.

[whiskerz007]

From what I can tell, HA is still functioning properly with the exception of being able to configure the network settings from the supervisor.

[gdreelin]

I noticed the same message a few months back and redid the container too but got the same. It all seems to be working fine at this time.

[gdreelin]

Now when I did the script it recommends to resolve it I get an error that "apparmor" is missing from the host system. Not sure if that helps or means anything. I am not a programmer so not 100% sure on that. Below is the screen output I got.

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 8401 100 8401 0 0 38714 0 --:--:-- --:--:-- --:--:-- 38714 root@hassio-server:/etc/network# bash installer.sh

[warn] If you want more control over your own system, run [warn] Home Assistant as a VM or run Home Assistant Core [warn] via a Docker container. [warn] [warn] If you want to abort, hit ctrl+c within 10 seconds... [warn] [warn] The following is missing on the host and needs [warn] to be installed and configured before running this script again [error] missing: apparmor root@hassio-server:/etc/network#