After rebooting the machine, Home Assistant doesn’t appear to be running. Going to http://localhost:8123/ results in a page “Firefox can’t establish a connection to the server at localhost:8123.”
sudo docker stats returns:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
3e8d357d9ec7 hassio_supervisor 0.00% 44.93MiB / 7.788GiB 0.56% 31.1kB / 1.6kB 0B / 135kB 17
ed2b72e8af57 hassio_dns 0.02% 4.566MiB / 7.788GiB 0.06% 12.3kB / 0B 0B / 0B 10
I had used a docker install before and to install it a docker command (running in a systemd file) runs that pulls the latest version and then runs it. The generic Linux install doesn’t require that step and it just started on its own on running the install script. Is it supposed to start on its own after a reboot too or is there something I need to do? Do I need to create a systemd file with the same docker command as when doing a docker install?
It’s been a while since i installed Home Assistant (formerly known as Hass.io) on a generic linux (ubuntu 16.04), but i think i have done nothing to autostart it.
I think the supervisor should start the HA container, but not 100% sure.
Are there any problems in the logs? docker logs hassio_supervisor
It could be a config error stopping it from starting. If you can get Portainter installed, then try to manually start it and like David suggested, see if auto-start is set.
I have never had to change anything when doing a generic Linux install of Hass.io Home Assistant (Supervised) install.
Yeah but when you install docker you have to run a command so docker starts when linux starts… if he missed that then docker isn’t running so no HA-Supervised…
Well…thank you so much everyone for the comments and hints…but it’s looking OK now. No, I can’t explain it! After posting this message, I turned the machine off and went for something to eat. Have come back, seen the messages and switched the machine on again to get the logs. The docker logs command produced messages that all looked OK and ended with “hassio up and running”. So I went into the browser interface and it’s all come up fine within about 20 seconds of booting.
So I really don’t know why it didn’t work on that first reboot.
With regard to setting docker to autostart…I was originally able to run the docker stats command so I assume docker was already up and running. To install docker in the first instance, I had followed all the instructions on the Docker CE site at https://docs.docker.com/install/linux/docker-ce/ubuntu/, including the post-install steps which has the systemctl enable commmand.
Anyway…isn’t it embarrassing when these things happen. It’s a learning curve.
Oh, and homeassistant now appears as a third running service in the docker stats command.
on a generic linux (ubuntu 16.04), but i think i have done nothing to autostart it.