Thanks for the guide, all the details were helpful!
I’ll just add that I also had to add the two lines mentioned by @SadGamerGeek to my sources.list file.
I’m really happy with the results already.
1 Like
Those lines are already in the file, but commented out, so they don’t need to be added, just have the comment removed.
I’ve tried to replicate that issue with a couple more test installs myself, and don’t have the problem. Perhaps it’s a region issue.
1 Like
It looks like this install method won’t work on a 32 bit machine, unless perhaps there is extensive tinkering. In fact, I cannot find any install method, even for Core, that will work on my netbook. I’d really appreciate confirmation of this, then I can stop my search and consider getting a 64 bit device.
1 Like
I just tried ‘sudo apt-get install docker-ce’ on my debian 10 32-bit : no available installation candidate.
There are some scripts on the net to build docker yourself on a 32-bit machine, but as you said : extensive tinkering.
I enjoy the tinkering bit. My concern is that once it’s up and running, an update (which are pretty frequent) to the system could break it, necessitating another bout of find and fix.
1 Like
Docker does require a 64 bit installation. You’re better off getting your hands on something that can support it properly from the bottom up. This install choice is already finicky.
1 Like
If so, How am I running Docker on my Raspbian RPi? Do you mean a Debian 64 bit installation?
If so that should be in the ADR as a requirement (I don’t remember seeing it - but could be wrong).
Docker requires 64bit on intel/amd. On RbPi it runs on 32bit.
1 Like
this installation method is not officially supported
I think you can now change this to this the only officially supported way to run supervised on a non-hassbian OS ;-). Your install method might differ a bit from what they put into the official docs and the installer they make, but I’d bet it is pretty damned close for someone who just has to try now. At least it hits all the supported components.
1 Like
this should be part of the main procedure … thanks!
2 Likes
Meant to say at the time, the precise lines I added were not in my file. The lines that were commented out were a little different, as in my pasted text.
[Error] Please set machine for armv7l
I get this when trying to run your last script on a RPi 4B
The guide is made for Intel/AMD Machines.
Replace
curl -sL "https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh" | bash -s
with
curl -sL "https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh" | bash -s -- -m raspberrypi4
4 Likes
I am also interested in installing Home Assistant Supervised via Docker. I tried the old script (install on generic Linux) which was comparable to your script. However, I don’t like the whole systemctl part, as I have OMV also installed on the system.
I found on reddit (https://www.reddit.com/r/homeassistant/comments/ghih2y/new_path_for_ha_on_docker/?utm_source=share&utm_medium=ios_app&utm_name=iossmf), that it is also possible to install the Linux dependencies but instead of running the script, running the following command:
docker run --name hassio_supervisor
–detach
–restart always
–privileged
–security-opt apparmor:unconfined
–security-opt seccomp=unconfined
-v /run/docker.sock:/run/docker.sock
-v /home/USER/ha:/data
-e SUPERVISOR_SHARE=/home/USER/ha
-e SUPERVISOR_NAME=hassio_supervisor
-e HOMEASSISTANT_REPOSITORY=homeassistant/amd64-homeassistant
homeassistant/amd64-hassio-supervisor
Can anyone say if the missing systemctl part can cause major problems? What are the advantages of the systemctl actions?
Just wanted to add my thanks for this guide.
I installed HA Supervised in a Docker container on Debian with only a few small dependency issues, but this helped massively for someone who is new to Debian and HA, so thanks for the effort. Really please with my set up and it’s been rock solid for weeks now.
1 Like
I bought a Wyse 5020 Thin Client I want to run as dedicated Home Assistant. It is 4GB memory and 32 GB drive. Would this method of install be a good solution for it?
Yep, that machine should work well.
I Just rebuild an upgraded server, but when trying to install, the supervisor cannot pull in the other docker containers for some reason, inside the supervisor i can ping google etc… Any ideas?
20-08-13 17:43:33 INFO (MainThread) [supervisor.bootstrap] Initialize Supervisor Sentry
20-08-13 17:43:35 INFO (MainThread) [supervisor.bootstrap] Setup coresys for machine: null
20-08-13 17:43:35 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 232
20-08-13 17:43:35 ERROR (MainThread) [supervisor.docker] Docker logging driver json-file is not supported!
20-08-13 17:43:35 INFO (MainThread) [__main__] Setup Supervisor
20-08-13 17:43:35 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-08-13 17:43:35 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-08-13 17:43:36 WARNING (MainThread) [supervisor.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
20-08-13 17:43:36 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.info] Update local host information
20-08-13 17:43:36 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.services] Update service information
20-08-13 17:43:36 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-08-13 17:43:36 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-08-13 17:43:36 INFO (MainThread) [supervisor.host.services] Reload local service hassio-apparmor.service
20-08-13 17:43:36 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-08-13 17:43:36 INFO (MainThread) [supervisor.plugins.dns] No CoreDNS plugin Docker image homeassistant/amd64-hassio-dns found.
20-08-13 17:43:36 INFO (MainThread) [supervisor.plugins.dns] Setup CoreDNS plugin
20-08-13 17:43:36 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:43:36 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:43:36 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:44:06 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:44:06 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:44:06 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:44:36 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:44:36 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:44:36 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:45:06 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:45:07 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:45:07 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:45:37 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:45:37 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:45:37 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:46:07 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:46:07 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:46:07 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
20-08-13 17:46:37 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-13 17:46:37 WARNING (MainThread) [supervisor.updater] Can't process version data: 'null'
20-08-13 17:46:37 WARNING (MainThread) [supervisor.plugins.dns] Error on install CoreDNS plugin. Retry in 30sec
Any ideas would be appreciated, as installing supervised has become really tedious, missing official documentation, a defective official script, … One would start to think they’re still trying to kill it off? 
So with this configuration I will be able to use ssh and samba to manage Home Assistant. If I need to reboot the thin client is that possible.
I am getting the same error.
Looks like something in the script or the version json file is broken at the moment.