I have been running a Hass.io docker in a Ubuntu 18.04 VM for quite a while with no issues.
Yesterday I shut down the VM, cleaned some snapshots, and powered it on again.
Now I can’t connect to the web interface and I have no idea where to start debugging.
When running “docker ps”, the image “homeassistant/qemux86-64-homeassistant:0.114.4” does not show any ports forwarded - is it supposed to?
Telnet’ing to the VM on port 8123, it doesn’t seem as if it’s listening.
The last two lines of “docker logs hassio_supervisor” says:
20-10-05 16:18:00 INFO (SyncWorker_5) [supervisor.docker.interface] Start homeassistant
20-10-05 16:18:00 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
And this is where I’m at.
Is HA getting stuck starting?
Anyone have any idea how to debug this? 
Edit: The web interface is accessible now. I didn’t do anything but wait.
This was the third time rebooting the VM since the issue occured. On previous restarts, HA has had considerably longer time to start than what was needed now – and it never seemed to start.
I have no idea what’s going on, but I’m hesitant on restarting it again!
The log lines following the ones above (and including) now reads:
20-10-05 16:18:00 INFO (SyncWorker_5) [supervisor.docker.interface] Start homeassistant
20-10-05 16:18:00 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
20-10-05 16:43:38 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
20-10-05 16:44:33 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
20-10-05 16:44:33 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' start 2 add-ons
How can I check what’s causing the startup delay?