I had a docker image named hassio, which installed avahi and everything else like socat and jq.
It would then start the install script, which would kick off the systemd calls. But that would fail as systemd can’t run inside a docker image.
systemd ins’t available for alpine, so I changed the base image from Ubuntu to the official Docker base image, which is based off alpine. However you need to use the alpine equivalent of systemd, which I couldn’t get to work properly inside the container.
Sorry for the late reply, no I didn’t unfortunately. I’ve been informed I can install HASSIO in a virtual environment (guide on here somewhere) but my Synology is not in the right state to use Virtual Machine Manager at present so not tried that route.
Still hoping someone who knows a lot more about this than me can come up with a ready to roll docker install though. Looking at you @philhawthorne
This might be a bit overkill, but what about:
creating a docker container with lets say ubuntu that runs on the synology nas.
That Ubuntu instanstance runs home assistant with hass io and everything you need.
`Hey Phil, did u mamange to get this sored or what did u end up doing, i am facing the same issue trying to run hssio on a qnap nas on container station using the option amd64-hassio-supervisor-1 within docker and it installs but does not start up. did u end up installing linux first and the hassio
Looking to do the same thing on unRAID docker with Hass.io. I have the Home assistant standalone docker container but feel like Hass.io would be a better way to go.
sed -i “s|%%SUPERVISOR_IMAGE%%|$HASSIO_DOCKER|g” “$BIN_DIR/hassio-start”
sed -i “s|%%HOMEASSISTANT_IMAGE%%|$HOMEASSISTANT_DOCKER|g” “$BIN_DIR/hassio-start”
sed -i “s|%%DATA_SHARE%%|$DATA_SHARE|g” “$BIN_DIR/hassio-start”
I’m not liking the responsiveness of my RaspberryPi Hass.io and it seems the SD card finally gave in this morning (or the Pi itself, haven’t had the time to look into it yet), so I decided to look into (re)creating it all on the home unRAID server.
I’ve seen it done in an VM (diyfuturism dude) but would first like to try what I imagine is a bit more direct aproach, doing it directly in unRAID docker(s).
Im really interested at this.
I own a Micro Server with Xeon and Server grade hardware where I run Unraid in it.
I would love to move hassio to the docker or to a VM at least so I can free up my pi3 for something else (looking at DIY 4k Ambilight)
I have a FreeNAS system that uses RancherOS for a docker host. I am brand new to it and haven’t actually used any dockers so I’m not sure what is and isn’t possible. Is it possible to use the docker images linked above since there are hassio supervisor, homeassistant, and addon images?
A lot of attempts have been made by people who know a lot more about docker and the underlining Home assistant architecture than me and they have come up which issues while trying to get it to work.
You’ll be better off using HA under docker for now, like myself and a lot of others like @philhawthorne.
Hello, I know your post is quite old. I was able to get hass.io installed and running, but once I shut it down the docker container for it disappeared and will not come back. I see the hass.io supervisor container, but hass.io is not running nor am I able to figure out how to get it to run. Any insights?
I think I’ve had that issue couple of times. for some reason the supervisor container ‘thinks’ that the home-assistant container is valid and doesn’t fir it up again. Haven’t spent lot of time to check the why but what I’ve done is to remove the supervisor again and fire the installation again. That solved my problem.
Also, do a copy of your Config, etc before running this…
Right, actually when you said that I realized that I’m deleting also the volume for the supervisor container. never tried to remove only the volume but makes a lot of sense as i guess it’s storing some cache information that is exactly what is wrong.
when that is deleted the supervisor will restart all the processes included the home-assistant contaner