Hass.io via Docker

I have a noob question about the Home-Assistant distros… so, I have a RP3b running Hass.io image based on HassOS - everything works OK.
I’m planning to build a NAS with OpenMediaVault, running in a ROCK64, but before that, I’m testing the OVM in a VM.
In that VM I installed the OpenMediaVault with Docker running. For testing, I have installed via Docker the HomeAssistant latest build, the problem is that, the Hass.IO settings are now showing. Image of what is not showing for reference:

Is there any way to install via docker the same image as we have in HassOS? Or anyway to add the Hass.io setting to the image?

Thanks in advance

EDIT: Answer to my own question can be found here:
->Hass.io via Docker

Home Assistant and hassio are different things in a sense.

Hassio is an “appliance” and home assistant is the application that runs on hassio (or via any other method you like). You won’t get ANY hassio features like add-ons and the hassio menu if you aren’t running hassio.

Located on this page:

You will find this link:

Wow! Things seem to be getting WAY more complicated trying to keep track of the multitude of installation permutations around.

Not that I have anything useful to add since I don’t use Hassio or HassOS. Just throwing my observation out there.

1 Like

thanks for your explanation.

-> So, it’s possible to install the hass.io tools in my HomeAssistant docker installation using the below instructions?
https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio

please read the script and understand what it does. The answer is in the script. If you blindly follow directions you will not know what is going on. Just read the script itself and piece it together.

2 Likes

Just wanted to be sure - thanks anyway.

“Beside the usage of the images it’s also possible to run Hass.io on a generic system without flashing an image.”

see this line here?

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

It’s literally telling the system to pull that file from the internet and run it.

What I want YOU to do is go read THAT script. Not the README.MD that is on that first page. Read the actual SCRIPT.

top!

I guess I’m understanding a bit better now.
After running the script on the docker, I have now the supervisor and the hass-io tools available :smiley:

Thanks for your help

1 Like

Sorry if my post came off harshly. I just want to help people understand what they are installing. :wink: Scripting is great, but sometimes its just good to know what is going on behind that magic script, especially if you have to modify something to work in your environment.

4 Likes

hey @TiagoRoxo I’ve got hassio running on an OMV install but I’m having some issues setting up the samba share to upload the snapshot from my raspberry pi hassio install.

Are you using the samba plugin from the add-on store or are you using an OMV shared folder to upload the snapshot? Any advice to set that up would be appreciated!

I’m also curious how your experience has been since you last posted here.

@TiagoRoxo you can help how do this on omv please?

How do this is? Simple (i’ve try and test on virtuabl with omv):

open shell omv and run this command ( found here: https://github.com/home-assistant/hassio-build/tree/master/install):
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s – -m intel-nuc (i’ve choose intel nuc because testing on virtual box)

I hope help you.

I ssh’d into my OMV computer and ran the generic install script:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

follow the configuration instructions on this video to map the /config location to some place on your OMV computer:

I went to my.omv.ip.address:8123 and home assistant was running.

I had to disable the SMB share on OMV and enable the samba addon in home assistant to upload my latest snapshot from my raspberry pi. Once that was uploaded, I added all my 3rd party addon repositories and restored.

I set the static IP address of my raspberry pi to the OMV computer. DuckDNS automatically started working.

Finally, I enabled SMB on the OMV computer and disabled the samba addon in Home Assistant.

I’m still trying to figure out the SMB setup but I have home assistant running and can flip back and forth for the time being.

1 Like

Could you explain how to run script in docker?

You don’t run it in docker you run it from the command line.

How? I have tried from the command line.
Please have a look at this post:

Thanks in advanced!

Hello guys
I will try this week to create a step by step on how to do it in OMV.
I will keep you posted.
:wink:

1 Like

How to Install Hass.IO in OMV?

  • I’m currently running OMV on an ODROID XU4/HC2 (ARMV7)
  • Open your OMV webpage
  • Enable SSH
  • Connect via SSH to the OMV
  • Execute the following cmd:
apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat software-properties-common
  • Then:
curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install" | bash -s -- -m odroid-xu -d "/sharedfolders/AppData/HA"

Note: The above share ( "/sharedfolders/AppData/HA” ) it’s a share that I can access remotely later via SMB(as example) to have access to the HA configuration.
Also, the above Hass.IO version it’s special for my device ( odroid xu4 ), you can check in the following page, what’s the version according your device: https://github.com/home-assistant/hassio-build/tree/master/install

  • After the installation finishes, in your browser enter the IP of your OMV and the port number 8123 (192.168.1.30:8123). You should see the following:

  • Wait around 20 minutes. Depends on device performance and Network link speed. During this waiting period, you can check in the Docker Container the Log for the Supervisor to track the progress. Open your docker in OMV and you should see something like this:

  • Open your docker in OMV and you should see something like this:

  • Everything should be running smoothly now. If you open your Home Assistant page, after setup your username and password, you should see the Home Assistant Dashboard page and in the left side, the Hass.IO tools:

  • If something goes wrong with your setup, you can also connect via SSH and remove all repositories and containers related to HA with the following cmdlets:
    List the Containers and repositories:
    docker container ls
    docker image ls
    <take note of the image ID of HA&HAsupervisor>
    Remove all the Containers and Reprositories associated with HA:
    docker rm --force <IMAGE ID>
    docker rm --force <IMAGE ID>
    docker rmi --force <IMAGE ID>
    docker rmi --force <IMAGE ID>
    List again the Containers and repositories to double check if any remaining are left from previus installations
    docker container ls
    docker image ls

More Info:
-> https://github.com/home-assistant/hassio-build/tree/master/install
-> https://www.home-assistant.io/hassio/installation/

10 Likes

hi @TiagoRoxo great job with the write up! it really helped me out especially the
-d "/sharedfolders/AppData/HA" which allowed me to set the config directory to a shared folder (using the OMV native SMB versus using the hassio samba plugin).

The documentation on the -d flag was added after I had installed hassio on OMV, but I just took a snapshot and deleted everything and started over and followed your instructions.

One thing I want to add for others reading this, if you’re having trouble deleting the HA Supervisor container and image, you need to first stop the service and disable it:

sudo systemctl stop hassio-supervisor.service
sudo systemctl disable hassio-supervisor.service

once I disabled the service, I could forcefully remove the container and image without it restarting, as you instructed above:

I also deleted all the hassio addon containers before restoring from a full snapshot and everything worked.

Thanks again!

1 Like

This works also great on a RPI3b with usb boot on Raspbian strech desktop + Docker! Thanks for this.

But for me there is one minor downside. I like to use Teamviewer Host to control the pi of some family members. After some testing I found out that after the first command ‘apt-get install…’ Teamviewer Host doesn’t work properly anymore after a reboot. After the reboot I have to link Teamviewer Host again with my account.

Does someone have a idea what would be the cause of this problem and how to solve it?