A:
cbee9b21d558 homeassistant/qemux86-64-homeassistant “/bin/entry.sh pytho…” 14 seconds ago Created homeassistant
400ac829176b homeassistant/amd64-hassio-supervisor “python3 -m hassio” 28 minutes ago Up 28 minutes hassio_supervisor
B: Systemd appears to be running (shows up in ps -aux)
C:
Feb 15 14:19:55 hassio hassio-supervisor[3769]: 19-02-15 14:19:55 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker!
Feb 15 14:19:55 hassio hassio-supervisor[3769]: 19-02-15 14:19:55 INFO (SyncWorker_3) [hassio.docker.interface] Clean homeassistant/qemux86-64-homeassistant Docker application
Feb 15 14:19:56 hassio containerd[3132]: time=“2019-02-15T14:19:56.853026053Z” level=info msg=“shim containerd-shim started” address="/containerd-shim/moby/9e0642d27460cb0a2c20a88a1207d8c254b62dcc414d059f90502f4737bb4908/shim.sock" d
Feb 15 14:19:56 hassio containerd[3132]: time=“2019-02-15T14:19:56.952954966Z” level=info msg=“shim reaped” id=9e0642d27460cb0a2c20a88a1207d8c254b62dcc414d059f90502f4737bb4908
Feb 15 14:19:56 hassio dockerd[3300]: time=“2019-02-15T14:19:56.963586479Z” level=error msg=“stream copy error: reading from a closed fifo”
Feb 15 14:19:56 hassio dockerd[3300]: time=“2019-02-15T14:19:56.963582551Z” level=error msg=“stream copy error: reading from a closed fifo”
Feb 15 14:19:57 hassio dockerd[3300]: time=“2019-02-15T14:19:57.067066557Z” level=error msg=“9e0642d27460cb0a2c20a88a1207d8c254b62dcc414d059f90502f4737bb4908 cleanup: failed to delete container from containerd: no such container”
Feb 15 14:19:57 hassio dockerd[3300]: time=“2019-02-15T14:19:57.067147990Z” level=error msg="Handler for POST /v1.39/containers/9e0642d27460cb0a2c20a88a1207d8c254b62dcc414d059f90502f4737bb4908/start returned error: OCI runtime create
Feb 15 14:19:57 hassio hassio-supervisor[3769]: 19-02-15 14:19:57 ERROR (SyncWorker_3) [hassio.docker] Can’t start homeassistant: 500 Server Error: Internal Server Error ("OCI runtime create failed: container_linux.go:344: starting c
Feb 15 14:19:57 hassio hassio-supervisor[3769]: 19-02-15 14:19:57 ERROR (MainThread) [hassio.tasks] Watchdog Home Assistant reanimation fails!
D: There are no HA log files (looking in /var/log)
I am guessing Part C shows that things are not right!
Not what I asked. I asked about the hassio systemd service.
Seems it’s trying to use a version that is incompatible with your CPU architecture?
There won’t be any HA log files in /var/log, because the log file is in the same directory as the config file. Reading the script you installed it should be in /usr/share/hassio?
Right, but that error generally means it’s trying to run a version that is not compatible with that CPU arch. It could be an LXC problem, but you also have apparmor issues, which are also probably an LXC problem.
Why not install docker-ce on the host, and run it from there? Or run a KVM VM?
Ref the logs: thats where I looked and its an empty folder.
Perhaps it is LXC putting its foot in there somewhere, I will go and have a read. I have a few things on the LXC host running so just wanted to get hass on there as well.
Many, many thanks for your speedy help as well, greatly appreciated!
It appears to do it all correctly, picking up the x86_64 version.
Managed to read the truncated output of systemctl status hassio-supervisor.service and found a couple of errors relating to docker itself:
ERROR (SyncWorker_4) [hassio.docker] Can't start homeassistant: 500 Server Error: Internal Server Error ("OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:70: creating device nodes caused \\\"open /var/lib/docker/btrfs/subvolumes/b2c519f7177bf62ef1e02fba8f6de9fcc99769e720d92ba2f930ee53a897c178/dev/tty: no such device or address\\\"\"": unknown")
Which, to be honest means nothing to me as this is the first time I have played with docker (apart from installing Hass on RPi).
i was also interested in installing hass.io to an lxc, with no luck. There is this docker thing I am struggeling with. I have also my host running several lxc containers and I have home-assistant successfully running in one. Its started with root inside the container, but if you are interested, I can post you my installation steps.
I will take a look through the installation script for hass.io soon. Maybe there is an option to port it to lxc, without docker.
That would be brilliant if you did - I gave up on Hass.io in the end. Would like to say I could help however, my knowledge doesn’t run that deep. I could try to beta test for you if needs be though.
The plain vanilla Home Assistant installed without a problem so have been playing with that - however, I did like the addons that Hass.IO provided.
Hey @happyhippy,
What hardware are you running the LXC container on? I’m possibly looking to buy a Qnap nas which supports LXC. Hoping it may be a viable and efficient way to run Hass.io
