Simple install command for installing Hass.io on a Generic Ubuntu/Debian machine

hassio_ubuntu_install_commands.sh

Unbuntu is no longer support by the Home Assistant project.

The installation commands previous listed here, are not up 2 date, not recommended, not supported and, therefore, removed.

Can you provide this to builder repository?

If you're running ubuntu 18.04 you need to add the universe repo to get jq installed.

add-apt-repository universe && sudo apt-get update

source: Tried this on a fresh ubuntu server install and it gave me an error about not being able to find jq, and this website recomended doing that repo add and line 3 worked after https://bonani.tech/how-to-install-hass.io-on-ubuntu-server-18.04/

Hi what is the next step after install ?
coming from openhab...

@aihysp Well for installing Hass.io on a Linux system, that is actually it.

From that point on, you can just use the documentation/getting started tutorials as listed on the Home Assistant website.

it all went well up until the last command (curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install" | bash -s) I constantly get error 404 bash command not found - what am i doing wrong?

Hi, I've installed Hass.io on my Ubuntu server 18.04 using this tutorial but now I'm not able to enable any addon that I install on my Hass.io ussing the Hass.io addons menu.
Somebody knows how can I fix that?
Thanks!

Thanks for the work here! I have the docker running on Ubuntu but cannot figure out how to connect to it with the browser.
I have tried hassio.local and all of the ip address I can find pertaining to the hassio images.

I am missing something!

@rlust: Did you try hassio.local:8123, works for me

Hi there,
I'm a newbe so please don't be angry with me :-)
Can I install this hassio docker on my Qnap NAS please ?
Usually I copy and paste a docker-compose yaml file

Thanks a lot
Denis

Anyone able to point me to how to install HASSIO..latest(hassos) image onto Synology. ( I have the Synology version of docker running on the Synology Nas). I think I just need the docker make file that the latest version of HASSIO uses.

Hi there,

thank you for the script, but it doesn't work for me.
After executing all steps from above (Without any error) ther is no HASSIO installed.

root@MediaServer:/usr/share/hassio# sudo curl -sL "https://raw.githubusercontent.com/home-assistant/hassio->build/master/install/hassio_install" | bash -s
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io`
that seems to be OK

but after checking the running instances:

root@MediaServer:/usr/share/hassio# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
root@MediaServer:/usr/share/hassio#
there is no hassio

So I check the "installation" directory:

root@MediaServer:/usr/share/hassio# ll
insgesamt 20
drwxr-xr-x 3 root root 4096 Jan 2 22:24 ./
drwxr-xr-x 334 root root 12288 Jan 2 22:24 ../
drwxr-xr-x 4 root root 4096 Jan 2 22:35 apparmor/
It seems more to be empty?

then I've checked the log:

root@MediaServer:/usr/share/hassio# journalctl -u hassio-supervisor.service -b
...
Jan 03 21:10:00 MediaServer systemd[1]: Started Hass.io supervisor.
Jan 03 21:10:01 MediaServer hassio-supervisor[1237]: time="2019-01-03T21:10:01+01:00" level=error msg="error waiting for container: context canceled"
Jan 03 21:10:01 MediaServer hassio-supervisor[1237]: Error response from daemon: error while creating mount source path '/usr/share/hassio': mkdir /usr/share/hassio: read-only file system
Jan 03 21:10:01 MediaServer hassio-supervisor[1237]: hassio_supervisor
Jan 03 21:10:02 MediaServer hassio-supervisor[1237]: docker: Error response from daemon: error while creating mount source path '/usr/share/hassio': mkdir /usr/share/hassio: read-only file system.

So it seems to be something wrong in the installation script?
Could please anyone help me?

Thank's a lot,
Shamane2000

PS:
my Environment is a running and hopefully actual Ubuntu 18.04.1 LTS.
Please ask for any other needed and missing Information.

@Shamane2000 Try running "wget https://raw.githubusercontent.com/home-assistant/hassio->build/master/install/hassio_install" to first download the install script. Then use ./hassio_install. It seems like you have a permissions issue. Apparently the script isn't run completely as sudo when you use curl.

Sidenote: When you first download the script, the permissions may be set to only read(check by running "ls -lah"). In that case run "sudo chmod 755 hassio_install"

@Shamane2000 Try running "wget https://raw.githubusercontent.com/home-assistant/hassio->build/master/install/hassio_install" to first download the install script. Then use ./hassio_install. It seems like you have a permissions issue. Apparently the script isn't run completely as sudo when you use curl.

Sidenote: When you first download the script, the permissions may be set to only read(check by running "ls -lah"). In that case run "sudo chmod 755 hassio_install"

@KasperNS Thank you for your quick reply, but it doesn't makes a difference.

root@MediaServer:/usr/share/hassio# wget https://raw.githubusercontent.com/home-assistant/hassio->build/master/install/hassio_install-bash: build/master/install/hassio_install: Datei oder Verzeichnis nicht gefunden
root@MediaServer:/usr/share/hassio# wget https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install
--2019-01-04 20:26:17-- https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install
Auflösen des Hostnamens raw.githubusercontent.com (raw.githubusercontent.com) … 151.101.112.133
Verbindungsaufbau zu raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: 5033 (4,9K) [text/plain]
Wird in »hassio_install« gespeichert.
hassio_install 100%[==========================================================>] 4,92K --.-KB/s in 0s
2019-01-04 20:26:17 (11,4 MB/s) - »hassio_install« gespeichert [5033/5033]
root@MediaServer:/usr/share/hassio# ll
insgesamt 32
drwxr-xr-x 3 root root 4096 Jan 4 20:26 ./
drwxr-xr-x 334 root root 12288 Jan 2 22:24 ../
drwxr-xr-x 4 root root 4096 Jan 2 22:35 apparmor/
-rw-r--r-- 1 root root 5033 Jan 4 20:26 hassio_install
root@MediaServer:/usr/share/hassio# chmod 755 hassio_install
root@MediaServer:/usr/share/hassio# ./hassio_install
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io
root@MediaServer:/usr/share/hassio# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

There is the same output as before.

So, I found a solution/workaround.

Iv'e added to the systemd file "/usr/sbin/hassio-supervisor" the docker "--privileged" flag, and now it works.
It would be great to have this change also in the install script. Or is there any point against that fix?

runSupervisor() {
docker rm --force hassio_supervisor || true
docker run --name hassio_supervisor --privileged
$APPARMOR
--security-opt seccomp=unconfined
-v /var/run/docker.sock:/var/run/docker.sock
-v /var/run/dbus:/var/run/dbus
-v ${HASSIO_DATA}:/data
-e SUPERVISOR_SHARE=${HASSIO_DATA}
-e SUPERVISOR_NAME=hassio_supervisor
-e HOMEASSISTANT_REPOSITORY=${HOMEASSISTANT}
${SUPERVISOR}
}

HI. I have a problem running the last command

connecting to the docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I'm running these commands via the ubuntu windows app on windows 10. I have a full featured home assistant already setup this way.

I don't know if this is anything to do with my problem but systemd is not PID 1.

Great stuff, thanks.
How can I ensure that the Hass.io container run automatically when restarting the machine?

I followed the directions at the top of this thread and they worked flawlessly.

Great stuff, thanks.
How can I ensure that the Hass.io container run automatically when restarting the machine?

Restart=always

thank you. this works perfect! <3

How would you go about updating this?

How would you go about updating this?

Go to Hass-io dashboard - add-ons and update from there, you should have a card with an update and release notes.

How do you increase the amount of disk that the docker image uses?
I am running low on space on my HASSIO environment.

After running your script:
url -sL "https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install" | bash -s

docker container is starting but quitting after a few seconds later and then restarting again and then quitting again in an endless loop. Docker logs show the following error:

docker.errors.APIError: 403 Client Error: Forbidden (“cannot create network 944af717b2ab356d08c3d52cd179c39a71a47f8bfceab5b67bd29151cd2d171c (hassio): conflicts with network b88ab28cdd7484f95d26fadf685338fd1e585ef2653ab1d42eaa95f7fefdc873 (br-b88ab28cdd74): networks have overlapping IPv4”)

What can I do with that?

Had a problem with my Ubuntu server and had to reinstall everything. Using the same method you have listed here I was able to get hassio installed, however, this time around that last part is giving me an error regardless if I type it in or copy and paste, the error starts with install supervisor Docker container then invalid reference format

I've rebooted the server just incase but the problem persists...

How do I uninstall all of this and start from scratch on my ubuntu 18.04?

Install Portainer on docker and then use that to delete the Hassio and start from Scratch

Is anyone else running out of disk space on the image?

Amazing Frenck works out of the box!

Hello @frenck ,
Thanks for the script, is great.
The only thing I am missing is how to change the hassio container (docker run) command. I'd like to add the --device argument so I can access USB port and enable z-wave. How can I do that? I have looked inside the services code, but as far as I can see, they only start the supervisor container.
Thanks.

Hello @frenck,

i can't get it installed on my ubunut server 19.04.
Docker won't install

this is the output of the script.
`root@automation:~# sudo curl -sSL https://get.docker.com | sh

Executing docker install script, commit: 2f4ae48

• sh -c apt-get update -qq >/dev/null
• sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
• sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
  Warning: apt-key output should not be parsed (stdout is not a terminal)
• sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu disco stable" > /etc/apt/sources.list.d/docker.list
• sh -c apt-get update -qq >/dev/null
• [ -n ]
• sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
  E: Package 'docker-ce' has no installation candidate`

Hi @frenck,

The link at the end needs changing to the following - https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh

I changed the line to
curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
Finaly I get an error

[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
Failed to enable unit: File hassio-supervisor.service: Invalid argument

So I changed the install.sh the following

#URL_BIN_HASSIO="https://raw.githubusercontent.com/home-assistant/hassio-installer/master/install/files/hassio-supervisor"
URL_BIN_HASSIO="https://raw.githubusercontent.com/home-assistant/hassio-installer/1da6261ec7b46166fa7e77998a38dab7bcf013bf/files/hassio-supervisor"
#URL_BIN_APPARMOR="https://raw.githubusercontent.com/home-assistant/hassio-installer/master/install/files/hassio-apparmor"
URL_BIN_APPARMOR="https://raw.githubusercontent.com/home-assistant/hassio-installer/1da6261ec7b46166fa7e77998a38dab7bcf013bf/files/hassio-apparmor"
#URL_SERVICE_HASSIO="https://raw.githubusercontent.com/home-assistant/hassio-installer/master/install/files/hassio-supervisor.service"
URL_SERVICE_HASSIO="https://raw.githubusercontent.com/home-assistant/hassio-installer/1da6261ec7b46166fa7e77998a38dab7bcf013bf/files/hassio-supervisor.service"
#URL_SERVICE_APPARMOR="https://raw.githubusercontent.com/home-assistant/hassio-installer/master/install/files/hassio-apparmor.service"
RL_SERVICE_APPARMOR="https://raw.githubusercontent.com/home-assistant/hassio-installer/1da6261ec7b46166fa7e77998a38dab7bcf013bf/files/hassio-apparmor.service"
URL_APPARMOR_PROFILE="http://s3.amazonaws.com/hassio-version/apparmor.txt"

@ageurtse for 19.04 you would need to install docker from test channel at the moment and you would use:
curl -fsSL get.docker.com | CHANNEL=test sh

And things have been moved so the last line would be:
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s

The urls @jossie67 pointed out have been fixed now

Thank you @stringy92, that missing .sh was causing all of the 404 errors. I now have it installed on my Ubuntu Server 18.10 laptop.

Gist updated with new locations.

Using this method - how can we run validate config from the VM ? most of the documentation points to running hass -c /config but I can't seem to find the hass executable once the installation completes using above method.

@Shamane2000 I am having the same issue you were. Can you expand on how you solved it with the information above? I am not good with Linux.

This is what I get...running latest Raspbian on RP3B+. I got HA running, just can't install Hassio.

root@raspberrypi:~# wget https://raw.githubusercontent.com/home-assistant/hassio->build/master/install/hassio_install.sh
-bash: build/master/install/hassio_install.sh: No such file or directory

root@raspberrypi:~# curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
[ERROR] Please set machine for armv7l

On Container Station of my QNAP I have loaded a container Ubuntu 18.04, with all prerequisites for running this script (I think).
At first systemctl start on systemctl start hassio-apparmor.service command I have this error:

. . . 
[Info] Install AppArmor scripts
+ mkdir -p /home/hassio/hassiocfg/apparmor
+ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/files/hassio-apparmor
+ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/files/hassio-apparmor.service
+ curl -sL http://s3.amazonaws.com/hassio-version/apparmor.txt
+ chmod a+x /usr/sbin/hassio-apparmor
+ systemctl enable hassio-apparmor.service
+ systemctl start hassio-apparmor.service

**System has not been booted with systemd as init system (PID 1). Can't operate.**

Any help ? Thanks

just for information at my debian the installation was ok, but i needed modify the hassio-supervisor file and added the docker argument
-p 8123:8123 to access the server
indeed my installation is done on a server that has a local ip in form 192.168.1.X
whereas the supervisor seems to have a docker IP that is different from my local network.

I already setup the hassio environment on Ubuntu Server 18.04, using the instructions from OP. Worked perfect. Now my question is, can I use the same process to setup a second hassio environment on the same server? I assume I'd need to adjust the script, but I'm not sure. Or would I be better off creating another Ubuntu server as a VM on the machine and setting everything up there?

My end goal is to have a hassio dev/test instance for playing with. I do have an used RPi if needed, but I was hoping to create the dev instance as close to prod as possible.

I'm open to alternative ideas. Thanks!

Thanks heaps for this. Worked perfectly except for my snapshot restore :(
For some reason I don't get my lovelace UI, and some other stuff is missing like node red.
Only thing in the log is:

2019-07-25 22:36:07 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 275, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp\_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method

Any help appreciated

Failed to connect to bus: No such file or directory

please help!
root@u:~# curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
Created symlink /etc/systemd/system/multi-user.target.wants/hassio-supervisor.service, pointing to /etc/systemd/system/hassio-supervisor.service.
[Info] Install AppArmor scripts
Created symlink /etc/systemd/system/multi-user.target.wants/hassio-apparmor.service, pointing to /etc/systemd/system/hassio-apparmor.service.
Failed to connect to bus: No such file or directory

@hoatienii

Failed to connect to bus: No such file or directory

did you install dbus ?

@hoatienii

Failed to connect to bus: No such file or directory

did you install dbus ?

yes, installed

Hi all and thank op for the scripts
Everything worked perfectly on a Ubuntu server 18.04.3 virtualbox vm beside this error:
WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
Is this a normal behaviour ?

Hi all and thank op for the scripts
Everything worked perfectly on a Ubuntu server 18.04.3 virtualbox vm beside this error:
WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
Is this a normal behaviour ?

Yes, totally fine. That's something that will only work on HassOS (the Ota updates), not generic Linux.

Hi all and thank op for the scripts
Everything worked perfectly on a Ubuntu server 18.04.3 virtualbox vm beside this error:
WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.
Is this a normal behaviour ?

Yes, totally fine. That's something that will only work on HassOS (the Ota updates), not generic Linux.

Thank you

On Container Station of my QNAP I have loaded a container Ubuntu 18.04, with all prerequisites for running this script (I think).
At first systemctl start on systemctl start hassio-apparmor.service command I have this error:

. . . 
[Info] Install AppArmor scripts
+ mkdir -p /home/hassio/hassiocfg/apparmor
+ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/files/hassio-apparmor
+ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/files/hassio-apparmor.service
+ curl -sL http://s3.amazonaws.com/hassio-version/apparmor.txt
+ chmod a+x /usr/sbin/hassio-apparmor
+ systemctl enable hassio-apparmor.service
+ systemctl start hassio-apparmor.service

**System has not been booted with systemd as init system (PID 1). Can't operate.**

Any help ? Thanks

@clabnet Did you manage to get Hass.io running on QNAP in Container Station?
If so, could you let me know how (preferably with a step-by-step instruction)?

THanks so much!
Script work fine on debian and ubuntu

script works amazing! Is there anyway to run hassio manually using docker run so that I can specify an ip address instead of it using the host adapter? I need hassio on a different VLAN.

I posted this same basic question over on HA: https://community.home-assistant.io/t/cant-update-hass-io-installed-on-linux-docker/139674

After following the above everything work fine for a few days, but then I am all of a sudden unable to do updates or install add-ons, I get an error like this:

19-09-28 16:10:20 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.99.3
19-09-28 16:10:20 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.99.2 to homeassistant/qemux86-64-homeassistant:0.99.3
19-09-28 16:10:20 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.99.3.
19-09-28 16:10:23 ERROR (SyncWorker_3) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.99.3 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.99.3: No such image: homeassistant/qemux86-64-homeassistant:0.99.3").
19-09-28 16:10:23 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Format reinstall fixes it for a few days and then the problem comes right back. Rebooted, upgraded, updated and rebooted again (all via Linux) didn't help. Any ideas?

Looks like I was just running out of disk space - HA got installed on my boot partition. Not sure how to move it, and I'm not very far in. Just going to do a single partition for now.

At end of this script on QNAP LXC Ubuntu 18.04, the hassio_supervisor container restart continuously. Any suggestion please ? Thank

Interestingly installed great for a windows guy like me, but, what URL must I use? I dont see any port mentioned. Http or Https? Does not respond to default 80 and 443 ports.

Never mind, had to google it but found it. Http and port 8123.

Not sure if it's been mentioned but there is no "Universe" repository for Debian, only Ubuntu.

https://unix.stackexchange.com/questions/113590/how-to-add-debian-universe-in-etc-apt-sources-list

Thank you. This works perfectly on 18.04 desktop. Just awesome.

After running your script:
url -sL "https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install" | bash -s

docker container is starting but quitting after a few seconds later and then restarting again and then quitting again in an endless loop. Docker logs show the following error:

docker.errors.APIError: 403 Client Error: Forbidden (“cannot create network 944af717b2ab356d08c3d52cd179c39a71a47f8bfceab5b67bd29151cd2d171c (hassio): conflicts with network b88ab28cdd7484f95d26fadf685338fd1e585ef2653ab1d42eaa95f7fefdc873 (br-b88ab28cdd74): networks have overlapping IPv4”)

What can I do with that?

@nor500 I am having this same issue. Did you get it resolved?

Thank you for the script. I tried to install hass.io on a fresh ubuntu 18.04 (proxmox lxc).

Docker version 19.03.5, build 633a0ea838

I get the following error:

Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Home Assistant docker now installed
Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Start Home Assistant
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (SyncWorker_2) [hassio.docker] Can't start homeassistant: 400 Client Error: Bad Request ("OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "write sysctl key kernel.domainname: open /proc/sys/kernel/domainname: permission denied"": unknown")
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (MainThread) [hassio.homeassistant] Can't start Home Assistant!
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 INFO (SyncWorker_4) [hassio.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:landingpage']

Can someone help me? I red something about dongrading docker, but that didnt worked either.

Thank you for the script. I tried to install hass.io on a fresh ubuntu 18.04 (proxmox lxc).

Docker version 19.03.5, build 633a0ea838

I get the following error:

Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Home Assistant docker now installed
Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Start Home Assistant
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (SyncWorker_2) [hassio.docker] Can't start homeassistant: 400 Client Error: Bad Request ("OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "write sysctl key kernel.domainname: open /proc/sys/kernel/domainname: permission denied"": unknown")
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (MainThread) [hassio.homeassistant] Can't start Home Assistant!
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 INFO (SyncWorker_4) [hassio.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:landingpage']

Can someone help me? I red something about dongrading docker, but that didnt worked either.

You're running docker as root (sudo) or you added your user to the docker group, correct? It looks like its just permissions issues, but I could be wrong too.

Thank you for the script. I tried to install hass.io on a fresh ubuntu 18.04 (proxmox lxc).

Docker version 19.03.5, build 633a0ea838

I get the following error:

Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Home Assistant docker now installed
Dec 07 18:07:02 hass hassio-supervisor[15792]: 19-12-07 18:07:02 INFO (MainThread) [hassio.homeassistant] Start Home Assistant
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (SyncWorker_2) [hassio.docker] Can't start homeassistant: 400 Client Error: Bad Request ("OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "write sysctl key kernel.domainname: open /proc/sys/kernel/domainname: permission denied"": unknown")
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 ERROR (MainThread) [hassio.homeassistant] Can't start Home Assistant!
Dec 07 18:08:50 hass hassio-supervisor[15792]: 19-12-07 18:08:50 INFO (SyncWorker_4) [hassio.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:landingpage']

Can someone help me? I red something about dongrading docker, but that didnt worked either.

You're running docker as root (sudo) or you added your user to the docker group, correct? It looks like its just permissions issues, but I could be wrong too.

Yes iam running docker as root. I thought the error was about the domainname as described in docker/for-linux#743 (comment)

I downgraded docker to Docker version 18.09.8, build 0dd43dd87f
but now i get the following error:

Dec 07 18:26:35 hass hassio-supervisor[1190]: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "rootfs_linux.go:70: creating device nodes caused \"open /var/lib/docker/vfs/dir/de666361efc37e70511cd17c63798fa75127a3914c96ace31616499977c69bf3/dev/tty: no such device or address\""": unknown

I've encountered the following error during final step of installation:

[ERROR] Please set machine for aarch64

Fixed with:

curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s--m aarch64

Cheers.

I've encountered the following error during final step of installation:

[ERROR] Please set machine for aarch64

Fixed with:

curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s--m aarch64

Cheers.

I'm getting the same error and have tried your fix, and i get "-- invalid option"
then i've tried other permutations like "bash -s -m aarch64" and then get an error that "[Error] Unrecognized option aarch64'
any ideas?

EDIT: nvm. i dug through the script and figured it out. i needed to enter this at the end

| bash -s -- -m raspberrypi4

that did the trick

Hello to everyone, when I try to run the last command it responds:

[Info] Install supervisor Docker container                                                                                                               
[Info] Install supervisor startup scripts                                                                                                                
[Info] Install AppArmor scripts                                                                                                                          
[Info] Run Hass.io  

I'm trying to run it in Container station on QNAP, with a Ubuntu system v 16.04 LXC
Any suggestions?
Thank you very much for the help.

That means it is done @sciaio

Hello to everyone, when I try to run the last command it responds:

[Info] Install supervisor Docker container                                                                                                               
[Info] Install supervisor startup scripts                                                                                                                
[Info] Install AppArmor scripts                                                                                                                          
[Info] Run Hass.io  

I'm trying to run it in Container station on QNAP, with a Ubuntu system v 16.04 LXC
Any suggestions?
Thank you very much for the help.

Can you provide some instructions/installation method on this?
I have QNAP TS-253Be and trying hard to not use VM.
thank you in advance.

Can you provide some instructions/installation method on this?
I have QNAP TS-253Be and trying hard to not use VM.
thank you in advance.

Hi @mercenaruss

Unfortunately I abandoned the installation via docker or LXC because of many complications. I am currently using it on a linux VM in Virtualization Station on Ubuntu 18.04, and with a core and 1 GB of RAM it is more than enough.

any news on this failure ?

OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "write sysctl key kernel.domainname: open /proc/sys/kernel/domainname: permission denied"": unknown")#033[0m

I'm trying this script on Debian 10 and got to the end then when I run this command:-
curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s

I get this:-
bash line 1: 404:: command not found

Has the github location changed as hassio is now called Home Assistant?

Thanks

Just looking around and I think it might have changed to this link now??

curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

I'll try it and let you know how I get on.

Yep, I can confirm the link has changed and is working. Please use this one in the future:-

curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

I am using OMV(openmediavault) where already docker and portainer is installed on.
Now I wanted to install hassio in my docker.

After doing the following commands:
sudo -i
sudo apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
apt-get install apparmor-utils avahi-daemon dbus jq network-manager socat
curl -sL https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh | bash -s -- -m raspberrypi3

i cannot reach my OMV and portainer installation.
Anyone idea what broke my installation?

Yep, I can confirm the link has changed and is working. Please use this one in the future:-

curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

Worked several days ago. Today it doesn't work.

Is there any update on this issue?

Yep, I can confirm the link has changed and is working. Please use this one in the future:-
curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

Worked several days ago. Today it doesn't work.

Is there any update on this issue? I am having the same problem. Thanks

Get this one locally and go on with it: https://gist.githubusercontent.com/frenck/28ead2ef4ed2b3d3d3aa9b4084e66484/raw/9acf6d699ba0a24788c254d9ef9ff16548e630f3/hassio-install.sh

I encountered the same error (bash: line 1: 404:: command not found) while running the command curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
Using the command from the official website did the trick :
docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/home-assistant:stable

I encountered the same error (bash: line 1: 404:: command not found) while running the command curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
Using the command from the official website did the trick :
docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/home-assistant:stable

This was for Home Assistant and not HASSIO.
The command for HASSIO docker installation is curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s
The link has changed.

Actually, as I saw, theres no relation between this script and debian/ubuntu based distros. It's work for any non-obscure distro.

When trying to run this curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s
I get this msg:
[Warning] This installer is no longer supported.
[Warning]
[Warning] Home Assistant might work today, tomorrow maybe not.
[Warning]
[Warning] If you want more control over your own system, run
[Warning] Home Assistant as a VM or run Home Assistant Core
[Warning] via a Docker container.
[Warning]
Please typ "not supported" to continue this installation
bash: rad 17: syntaxfel nära den oväntade symbolen ”then”

Sorry for the last row, its in swedish.
Im runing docker in OVM. curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s this worked before, but now it doesn´t.
/jerry

When trying to run this curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s
I get this msg:
[Warning] This installer is no longer supported.
[Warning]
[Warning] Home Assistant might work today, tomorrow maybe not.
[Warning]
[Warning] If you want more control over your own system, run
[Warning] Home Assistant as a VM or run Home Assistant Core
[Warning] via a Docker container.
[Warning]
Please typ "not supported" to continue this installation
bash: rad 17: syntaxfel nära den oväntade symbolen ”then”

Sorry for the last row, its in swedish.
Im runing docker in OVM. curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s this worked before, but now it doesn´t.
/jerry

I have the very same issue when installing hassio on Ubuntu 18.0.4 running on a Oracle VM machine.....

Is there any fix for this or is just not longer supported?

Is there any fix for this or is just not longer supported?

You can use this script instead: https://raw.githubusercontent.com/uherting/supervised-installer/master/installer.sh

I forked the repository yesterday and changed the installer.sh file only. It is literally the same without the annoying error and the question.

This looks like it was great - but unfortunately as of 26th May 2020 - it would appear that the support from this has been removed. To save hunting for it - for anyone wondering why and what to do about it, see this forum post: https://www.home-assistant.io/blog/2020/05/26/installation-methods-and-community-guides-wiki/ with some apparent back-history for bedtime reading: https://www.home-assistant.io/blog/2020/05/09/deprecating-home-assistant-supervised-on-generic-linux/

I need some help... while i started hassio supervisor by using command journalctl -f -u hassio-supervisor i've got following errors:

May 28 12:08:00 ubuntu-xenial-armhf-1 systemd[1]: Started Hass.io supervisor.
May 28 12:08:01 ubuntu-xenial-armhf-1 hassio-supervisor[27046]: time="2020-05-28T12:08:01Z" level=error msg="error waiting for container: context canceled"
May 28 12:08:01 ubuntu-xenial-armhf-1 hassio-supervisor[27046]: Error response from daemon: OCI runtime create failed: container with id exists: e2ebd34e2380cd96b534215e90d6b4c0040139abaa05eade7c2642dfd7c53c8f: unknown
May 28 12:08:02 ubuntu-xenial-armhf-1 hassio-supervisor[27046]: hassio_supervisor
May 28 12:08:05 ubuntu-xenial-armhf-1 hassio-supervisor[27046]: docker: Error response from daemon: cgroups: cannot find cgroup mount destination: unknown.
May 28 12:08:05 ubuntu-xenial-armhf-1 hassio-supervisor[27046]: time="2020-05-28T12:08:05Z" level=error msg="error waiting for container: context canceled"
May 28 12:08:05 ubuntu-xenial-armhf-1 systemd[1]: hassio-supervisor.service: Main process exited, code=exited, status=125/n/a
May 28 12:08:05 ubuntu-xenial-armhf-1 docker[27205]: hassio_supervisor
May 28 12:08:05 ubuntu-xenial-armhf-1 systemd[1]: hassio-supervisor.service: Unit entered failed state.
May 28 12:08:05 ubuntu-xenial-armhf-1 systemd[1]: hassio-supervisor.service: Failed with result 'exit-code'.
May 28 12:08:11 ubuntu-xenial-armhf-1 systemd[1]: hassio-supervisor.service: Service hold-off time over, scheduling restart.
May 28 12:08:11 ubuntu-xenial-armhf-1 systemd[1]: Stopped Hass.io supervisor.
May 28 12:08:11 ubuntu-xenial-armhf-1 systemd[1]: Starting Hass.io supervisor...
May 28 12:08:11 ubuntu-xenial-armhf-1 docker[27214]: hassio_supervisor

bash: line 1: 404:: command not found
Please help

Any updates to this? trying to install hassio on ubuntu 18.04

bash: line 1: 404:: command not found
Please help

I'm having the same issue.

Hi guys. Line 8 can be replaced with:

curl -Lo installer.sh https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh
bash installer.sh

This should not be used anymore.

I'm therefore removing the content of this gist.

Why has this been broken? I removed my containers and re-ran the script only to be surprised by 404 errors. I'm running the newer installer.sh and it's ALMOST working ....except that homeassistant frontend won't install it seems. Very sad if this isn't supported anymore.. This was working great on my Fedora 31 system (docker) with a few tweaks to the script (minimal detection of apparmor and dbus).

@gr33k lol this has been long gone.... Here are the officially supported ways to install HomeAssistant:

https://www.home-assistant.io/docs/installation/

Thank you @snipes040 - I am trying the Supervised version here and the same results - it installs after commenting out dbus and apparmor (Fedora 31..got it working like this in hassio_installer.sh) as expected. However, I still don't have homeassistant installed/running...am I missing something? I don't see any errors and the output shows:

[info] Home Assistant supervised is now installed
[info] First setup will take some time, when it's ready you can reach it here:
[info] http://192.168.10.144:8123

I'm not sure why it's not attempting to install it. Supervisor is setup and working properly as far as I can tell...I can remove the containers and it appears to rebuild/start them. This is great! but no HA ? puzzled here :(

Note: I am using -d to tell it where my previous installation was located at - not sure if that's relevant perhaps:
sudo ./installer.sh -d /data/Containers/hassio

Script as I am using it is almost like original besides the two commented out lines:
https://paste.thec0de.com/?f3fcd70c26f617c9#4YFwnSdVSSkQcqCSkM1U237S6i3hrnctjSZfxUs8St9D

Sadly nobody has an answer to a script that was working fine before the creator decided to pull the original code.

Could you please put back the old code the way it was - post that it's NOT supported, and make old and new users happy? I hate it when code is pulled folks. There's no need to kill old code that works great for people :(

@gr33k I guess you meant to say:

"I don't now how to look into revision history in GitHub"

Or

"Where can I find information about installing a Home Assistant Supervised system?"

So revisions can be found here:

However, as I stated in the current contents, that is outdated, doesn't work and isn't supported either.

The installer Home Assistant Supervised installer can be found here: https://github.com/home-assistant/supervised-installer

---

There's no need to kill old code that works great for people :(

I didn't. Your own knowledge of GitHub is the thing lacking here. And honestly, if you don't know how this stuff here on GitHub works already, I would strongly recommend NOT to use the Supervised based installation method. It is expected someone to have an independent and sufficiently of level technical knowledge (which considering your answer is not the case).

@frenck the script itself gets 404 because the links no longer are valid. It would have been nice if they didn't 404 - but if you're saying they wouldn't work anymore anyway....ok fair enough.

I'd love to have a currently supported script that works I suppose - I did use that link you and snipes040 provided. Everything installs except for Home Assistant itself. Any idea why it wouldn't install the container? I've removed the old one and nothing is listening on 8123 of course. How can I debug this? No errors are displayed and I'm not sure what part of the script is particularly failing...I thought supervisor was supposed to create it?

Thank you

@gr33k I linked the source repository containing the installer script: https://github.com/home-assistant/supervised-installer. Which is actively maintained.

If you need support on setting up an instance, I highly recommend joining the Home Assistant Discord server: https://www.home-assistant.io/join-chat. Please, be sure to have a supported setup, one that matches the requirements listed in the supervised-installer repository.