hassio is not just one docker container. It’s one for the supervisor, one for HA, and then one per add-on.
The install script also configures systemd to start the supervisor as/when needed - e.g. on boot.
You may be able to get hassio unofficially working by doing the following, but I cannot check it as I dont have synology/DSM:
-
Check what CPU architecture you have (ARM or X86) here:
https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model
It will inform you which version of supervisor to pull. -
Review the hassio linux install script to understand how the systemd script starts hassio supervisor - you’ll need to start it with the same parameters/arguments (e.g. volume mounts etc)
-
Essentially do what the install script does: create dirs, pull the supervisor image, start the supervisor etc.
docker run --name hassio_supervisor
-v /var/run/docker.sock:/var/run/docker.sock
-v /var/run/hassio-hc.sock:/var/run/hassio-hc.sock
-v %%DATA_SHARE%%:/data
-v /var/log/supervisor-log:/var/log
-e SUPERVISOR_SHARE=%%DATA_SHARE%%
-e SUPERVISOR_NAME=hassio_supervisor
-e HOMEASSISTANT_REPOSITORY=%%HOMEASSISTANT_IMAGE%%
%%SUPERVISOR_IMAGE%%
You need to have an up-to-date version of docker.
If you can read shell scripts you have a relatively good chance, but honestly though as someone who is not using DSM I have no way to test this, and the long term supportability of such an install is not good IMO.