Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
HASSIO (Home Assistant Supervised) for Synology DSM 7 (Unsupported Installation but allows updates and fully functional)
version: '3'
services:
hassio:
image: homeassistant/amd64-hassio-supervisor
container_name: hassio_supervisor
privileged: true
security_opt:
- seccomp:unconfined
- apparmor:unconfined
environment:
- HOMEASSISTANT_REPOSITORY=homeassistant/qemux86-64-homeassistant
- SUPERVISOR_SHARE=/PATH/TO/FOLDER/A
- SUPERVISOR_NAME=hassio_supervisor
volumes:
- /PATH/TO/FOLDER/A:/data
- /var/run/docker.sock:/var/run/docker.sock
- /var/run/dbus:/var/run/dbus
@maeneak
Copy link
Author

maeneak commented Aug 11, 2021

SHH to NAS and run as root: docker-compose up --detach
To get USB working see https://github.com/robertklep/dsm7-usb-serial-drivers

@maeneak
Copy link
Author

maeneak commented Aug 12, 2021

To refresh installation docker-compose down then docker-compose up --detach.
Supervisor will not remove containers on docker-compose down.
Use:
docker rm $(docker stop $(docker ps --filter name=hassio* -q))
docker rm $(docker stop $(docker ps --filter name=homeassistant -q))

@maeneak
Copy link
Author

maeneak commented Sep 2, 2021

Best to upgrade system by using the method above. This will pull the latest images and avoid any confilcts

@dwl99
Copy link

dwl99 commented Sep 9, 2021

I've managed to install HASSIO using your guide but whenever I try to install any add-ons I get an error message "XXXXX blocked from execution, system is not healthy" which I suspect is due to the obsolete version of Docker that comes bundle with DSM7. IIRC this didn't seem to be an issue in DSM6. Any suggestions?
Thanks

@draftpunk
Copy link

draftpunk commented Sep 9, 2021

I've managed to install HASSIO using your guide but whenever I try to install any add-ons I get an error message "XXXXX blocked from execution, system is not healthy" which I suspect is due to the obsolete version of Docker that comes bundles with DSM7. IIRC this didn't seem to be an issue in DSM6. Any suggestions?
Thanks

I faced the same issue and found the following workaround: home-assistant/supervisor#2288 (comment)

add jobs.json {"ignore_conditions": ["healthy"]} in the hassio folder just above config. This ignores unhealthy conditions

Occasionally the supervisor container will crash for some reason, but overall it is working fine.

@dwl99
Copy link

dwl99 commented Sep 9, 2021

I've managed to install HASSIO using your guide but whenever I try to install any add-ons I get an error message "XXXXX blocked from execution, system is not healthy" which I suspect is due to the obsolete version of Docker that comes bundles with DSM7. IIRC this didn't seem to be an issue in DSM6. Any suggestions?
Thanks

I faced the same issue and found the following workaround: home-assistant/supervisor#2288 (comment)

add jobs.json {"ignore_conditions": ["healthy"]} in the hassio folder just above config. This ignores unhealthy conditions

Occasionally the supervisor container will crash for some reason, but overall it is working fine.

Thanks for your quick reply, that worked perfectly after I rebooted the NAS, a HA restart wasn't sufficient.

@dwl99
Copy link

dwl99 commented Sep 9, 2021

To refresh installation docker-compose down then docker-compose up --detach.
Supervisor will not remove containers on docker-compose down.
Use:
docker rm $(docker stop $(docker ps --filter name=hassio* -q))
docker rm $(docker stop $(docker ps --filter name=homeassistant -q))

Sorry, I'm a bit confused - which of these procedures and in what order should we follow for an upgrade?

@FloMaetschke
Copy link

FloMaetschke commented Sep 28, 2021

Sorry, I'm a bit confused - which of these procedures and in what order should we follow for an upgrade?

have you tried:

docker-compose down
docker rm $(docker stop $(docker ps --filter name=hassio* -q))
docker rm $(docker stop $(docker ps --filter name=homeassistant -q))

i also added
docker rm $(docker stop $(docker ps --filter name=addon* -q))
here

docker-compose up --detach

@FloMaetschke
Copy link

FloMaetschke commented Sep 28, 2021

@dwl99
Copy link

dwl99 commented Sep 28, 2021

Thanks - my Home Assistant Core version was outdated but I successfully updated it via the "update" button! I didn't want to risk it with the Supervisor version.

@exigency1
Copy link

exigency1 commented Oct 10, 2021

Starting hassio_supervisor ... error

ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists

ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists
ERROR: Encountered errors while bringing up the project.

Please help. Thank you

@dwl99
Copy link

dwl99 commented Oct 17, 2021

Starting hassio_supervisor ... error

ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists

ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists ERROR: Encountered errors while bringing up the project.

Please help. Thank you

You need to create a folder in your NAS, give it the appropriate permissions then edit the script with the path to the folder. For instance, the line in my docker-compose.yaml reads
- SUPERVISOR_SHARE=/volume1/hassio

@exigency1
Copy link

exigency1 commented Oct 17, 2021

Starting hassio_supervisor ... error
ERROR: for hassio_supervisor Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists
ERROR: for hassio Cannot start service hassio: Bind mount failed: '/PATH/TO/FOLDER/A' does not exists ERROR: Encountered errors while bringing up the project.
Please help. Thank you

You need to create a folder in your NAS, give it the appropriate permissions then edit the script with the path to the folder. For instance, the line in my docker-compose.yaml reads - SUPERVISOR_SHARE=/volume1/hassio

Thanks :-)

@dwl99
Copy link

dwl99 commented Feb 16, 2022

I keep getting error messages about hassio supervisor containers stopping unexpectedly every few minutes. When I looked at the running containers thare are several instances of hassio supervisor. Any idea what's going on?
hassio

@Ivan-L
Copy link

Ivan-L commented May 29, 2022

Note that I added the following to the hassio node under services because I wanted the supervisor container to be automatically restarted if it crashes.

restart: always

So:

services:
    hassio:
        image: homeassistant/amd64-hassio-supervisor
        container_name: hassio_supervisor
        privileged: true
        restart: always
        ....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment