OK, I need to explain what has happened this week, so that everyone can explain what I have done wrong and hopefully I can get back to a fully working system.
The beginning
I have had hassio running in a docker environment on Xubuntu on a old laptop for around 6 months (after going through 2 SD cards on a Pi3B+ over 18 months previously). It was working ok, but I found I needed to reboot the laptop around once a week otherwise it would lock up and crash (think there was something wrong with the RAM, it was an old laptop). So on Tuesday it locked up and when I did a hard reset of the laptop, when hassio came up, I could ssh in, and I could see the samba shares but the front-end didn’t come up. I tried all the cli commands - hassio ha restart, stop even the update etc. and they all returned with a blank error message - 'error: ’
So crazy me went and bought a new laptop but with some mod cons, ssd drive, 8gb ram, and after much annoyance with USB keys and UEFI/BIOS options I finally got the same version of Xubuntu (18.04) installed in a partition and went through the standard installing of docker - which wouldn’t work.
Eventually I used snap to install docker rather than apt-get and then I tried to install (using the docker pull) portainer and that just wouldn’t install, eventually I found a mention in a github issue that i686 architecture machines are not supported. But this doesn’t seem to be listed on any of the docker information.
I tried to use the Hassio installer directly (https://github.com/home-assistant/hassio-installer) and it would do all the right things and say [INFO] Run Hass.io but it didn’t appear on localhost:8123 or as a docker container or anywhere else, and I could find any files that in /share I thought it might create so I gave up on this as well.
But I got HA running in the docker environment but I really want to use HASSIO, while I get it that people want to control everything, in the end the ease of using add-ons etc. and my setup for the last 2 odd years has been in Hassio so I don’t want to give that up. And as I wouldn’t have portainer to help manage the docker environment I just don’t want to invest the time in setting up and managing all the containers myself. (I am running appdaemon and node-red and duckdns etc.)
So I switched back to the original windows on the new laptop (I left it in its partition when I installed xubuntu) and installed Hassio in a virtualbox instance with lots of ram and a few cores, and it worked. But when I then restored any of my snapshots, it did not (guessing as they were in a linux/docker setup and the new machine was in a virtualbox linux environment). So I gave that up and just brought my config from github back, reloaded my addons and cleaned up some of the ip addresses, and everything seemed to work, but when I do a restart it is taking 25+ minutes to restart! I eventually after again commenting out and removing parts of my config I found that it is google calendar that is causing it to take so long, so I have commented that out, but it is still taking 5-7 minutes to restart and I was using the calendar to trigger and control various parts of my setup, that I am now missing.
So if you have made it this far, you are probably feeling as frustrated as I am, but hopefully you have spotted all the things that I did wrong and can give me a critique of what I should do to get some things working as expected. As to me it seems crazy that a modern laptop is less capable than one 5 or 6 years old with dodgy ram.
On the bright side at least I have my lights back working.
Any ideas, thoughts, instructions, pity or condolences welcome,