I’ve been running my HA instance in a VM running Fedora Server 32 for a year and 1/2. A few days ago, there was an update to Docker-CE and that’s when the problems started. I tried removing Docker, deleting the /var/lib/docker, /var/lib/containerd and /usr/share/hassio folders and files. I’d reinstall and use the full restore feature during the supervised install after docker was reinstalled. When is was finished, all of the addons where up and running, but homeassistant wasn’t. I tried to manually start it, but it said it couldn’t find homeassistant. I verified this with docker ps -a, and it wasn’t there. I tried rebooting and only homeassistant-observer was running. I ran docker ps -a and saw all the addons. Each additional run of docker ps -a showed the addons were being deleted until only hassio_observer was running and the rest had been deleted. I tried this several more times before I thought something must be corrupt and I couldn’t find the issue… I deleted the VM and created a new one from the install ISO. I also created another VM using Debian Buster, since it’s the only supported version for Supervised install.
After the installs, I updated both the VM’s with their own updates and fixes, until they were up to date. I started the install on each using the installer script and saw again what I described up above, both on Fedora Server 32 and Debian Buster. I removed docker and all the folders related to it and HA, as I did above. I reinstalled docker and HA again. This time I created an account, logged in, added Google Backup, restored my latest backup. I did a restore of all the addons. I watched from the command line as each was started until all were running. I then reinstalled the HA config, local addons, SSL and share. When finished, HA disconnected my connection. I saw HA restart, but the connection didn’t restore, so I refreshed the web browser and logged in again. Everything was running as expected, so I tried a reboot and saw it was again only running the HA observer and watched as it HA and all of the addons were deleted until only the observer was left.
I had no choice but to switch to the Hassio vm file and install it that way. I did a full restore during the install and it worked as expected when the install was complete. I’m not particularly happy using Hassio instead of the supervised install and actually consider this a step backwards. I don’t have the level of control on the OS as I did with the supervised install.
I’m not sure if there’s something with the installer.sh or with the latest version of Docker. I wanted to document this and see if anyone else had this issue or hopefully getting a dev to look into this, especially since this occurred with Debian Buster, the officially supported version of Linux for a supervised install.