-
-
Save maeneak/851e883eca7cddd7114f7eaed201ca9d to your computer and use it in GitHub Desktop.
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 |
Hold on, this guide is asking for donations to download a 34 byte/character jobs.json file taken from an issue in the original project's repository? That's ridiculous to have to pay for a file containing {"ignore_conditions": ["healthy"]}
It does now, but didn't when I originally posted.
Hi,
I just tried this install method and also the guide from https://mariushosting.com/how-to-install-home-assistant-supervisor-on-your-synology-nas/, but I'm getting an error when I try to open the Add-ons page.
The page stays blank for a while, then it shows a Troubleshooting page.
If I look at the network tab on DevTools, I see the it failed to load "...:8123/api/hassio/app/entrypoint.js" with error 502 (Bad Gateway).
I am running DSM 6.2 on Synology 718+. There are 7 hassio containers running.
There seems to be some error regarding the Supervisor...
Any help would be appreciated.
I want to avoid the VM approach, because it'll use a lot more resources from my NAS.
To refresh installation
docker-compose down
thendocker-compose up --detach
. Supervisor will not remove containers ondocker-compose down
. Use:docker rm $(docker stop $(docker ps --filter name=hassio* -q))
docker rm $(docker stop $(docker ps --filter name=homeassistant -q))
Hi,
If i make it on working system i lost all HA setting ?
Where docker-compose.yaml should be placed ?
Hold on, this guide is asking for donations to download a 34 byte/character jobs.json file taken from an issue in the original project's repository? That's ridiculous to have to pay for a file containing {"ignore_conditions": ["healthy"]}