Originally posted by connoleg
View Post
Announcement
Collapse
No announcement yet.
HS3 on Synology
Collapse
X
-
Updated Docker Container for HomeSeer should work now with updated instructions.Last edited by FastFreddi; March 17, 2017, 05:04 PM.
Comment
-
I love that this concept has been made a reality. Much kudos to FastFreddi.
EDIT 9/23/2017 If anyone is having trouble getting the scheduled task to run on boot, and manually running from the task scheduler is fine, but when the synology reboots not so much I enabled output recording under settings, pointing output to a dedicated directory under /tmp (volume1)
Script is shown below. Seems that without sleep, only portainer will start, which may be something timing related.
Code:#!/bin/sh sleep 15 echo "Starting docker portainer" docker start portainer sleep 15 echo "Starting docker Syno-HomeSeer" docker start Syno-HomeSeer sleep 15 echo "Script exiting"
On a seperate note, I was able to access portainer via the web UI, but after a reboot and a 'docker start portainer' starts fine but cannot be accessed any more. Not sure what to make of that.
Code:root@diskstation-1:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8126cbbbe34e portainer/portainer "/portainer" 5 days ago Up 2 minutes 0.0.0.0:9000->9000/tcp portainer 782e4e9c02b2 fastfreddi/ubuntu-baseimage-homeseer:latest "/sbin/my_init" 5 days ago Up 2 minutes Syno-HomeSeer
Last edited by jjwatmyself; September 23, 2017, 12:17 PM.
Comment
-
I'm not sure what the issue is with Portainer web GUI, I can't reproduce it.
As for HomeSeer restart on reboot, I think the easiest way to make it happen is to use
docker run -it -d --net=pub_net --ip=10.0.3.2 --device=/dev/ttyACM0:/dev/ttyACM0 \
--name=Syno-HomeSeer --restart always fastfreddi/ubuntu-baseimage-homeseer:latest
instead of --restart on-failure when creating the container.
Comment
-
Originally posted by FastFreddi View PostI'm not sure what the issue is with Portainer web GUI, I can't reproduce it.
As for HomeSeer restart on reboot, I think the easiest way to make it happen is to use
docker run -it -d --net=pub_net --ip=10.0.3.2 --device=/dev/ttyACM0:/dev/ttyACM0 \
--name=Syno-HomeSeer --restart always fastfreddi/ubuntu-baseimage-homeseer:latest
instead of --restart on-failure when creating the container.
portainer has been running but I'm still unable to access via the web UI since the first reboot. I also turned off Windows firewall to see if there was some blocking and no luck
Code:root@diskstation-1:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8126cbbbe34e portainer/portainer "/portainer" 4 weeks ago Up 14 minutes 0.0.0.0:9000->9000/tcp portainer 782e4e9c02b2 fastfreddi/ubuntu-baseimage-homeseer:latest "/sbin/my_init" 4 weeks ago Up 8 minutes Syno-HomeSeer
Otherwise, I'm loving the ability to run on my Synology and thanks for sharing all the hard work. Eliminating dedicated hardware is a major win.
Comment
-
Ok try
Code:docker commit Syno-HomeSeer Private-homeseer:v1
Code:docker run -it -d --net=pub_net --ip=10.0.3.2 --device=/dev/ttyACM0:/dev/ttyACM0 \ --name=Syno-HomeSeer-Private --restart always Private-homeseer:v1
you may need to add docker commit Syno-HomeSeer fastfreddi/Private-homeseer:v1 or something similar.
If all works, then you can delete your original container
Comment
Comment