Docker Configuration via Synology Docker GUI

[Carlton Bale]

I installed the SageTV Java 10 Docker on my Synology NAS. Docker is configured via a GUI and I want to make sure I'm implementing the original instruction correctly. Feedback appreciated.

Original instructions I'm following:

docker run -d --name sagetv-server \
  -v /home/seans/unRAID/mnt/user/sagemedia:/var/media \
  -v /home/seans/unRAID/mnt/user/mediaext:/var/mediaext \
  -v /home/seans/unRAID/mnt/user/apps/sagetv3:/opt/sagetv \
  -v /home/seans/unRAID:/unraid \
  --net host \
  --env PUID=1000 \
  --env PGID=1000 \
  --env VIDEO_GUID=19 \
  --env OPT_GENTUNER=Y \
  --env OPT_COMMANDIR=Y \
  --env OPT_COMSKIP=Y \
  --env JAVA_MEM_MB=768 \
  --env VERSION=latest \
  --env OPT_SETPERMS=Y \
  --privileged \
  -t -i stuckless/sagetv-server-java8

Here' the General Settings screen. Container Name takes care of: --name sagetv-server and high privilege takes care of --privileged \


The Volumes tab takes care of the -v ... commands:


Port settings are auto, taking care of --net host \


Environment settings take care of the --env settings



Question: After removing all of the GUI-entered commands, the original run command distills down to this:

docker run -d -t -i docker/sagetv-server-java10

Is this correct? Do I need the the -d, -t, and -i arguments?

What's the purpose of the "docker/sagetv-server-java10" path? Do I need that?

Thanks in advance!

[stuckless]

I don't think your volumes are correct.

the -v commands map NAS volumns to CONTAINER volumes. (ie, path on your synology file system to path INSIDE the docker container)

  -v /home/seans/unRAID/mnt/user/sagemedia:/var/media \
  -v /home/seans/unRAID/mnt/user/mediaext:/var/mediaext \
  -v /home/seans/unRAID/mnt/user/apps/sagetv3:/opt/sagetv \
  -v /home/seans/unRAID:/unraid \

So in your case you are not using /var/media or /opt/sagetv and as such recordings and sagetv configurations will be stored INSIDE your container and restarts/upgrades will likely blow it all away.

So in your UI it would appear that your RIGHT HAND side must be values like /opt/sagetv and /var/media/ and the LEFT HAND side will be full paths to where you want this information stored on your NAS. And neither of them can be READ ONLY (sagetv will need to write to those paths)

The ENV section will need some tweaking as well

  --env PUID=1000 \
  --env PGID=1000 \
  --env VIDEO_GUID=19 \
  --env OPT_GENTUNER=Y \
  --env OPT_COMMANDIR=Y \
  --env OPT_COMSKIP=Y \
  --env JAVA_MEM_MB=768 \
  --env VERSION=latest \
  --env OPT_SETPERMS=Y \

PUID and GUID MUST be the linux user and group ON YOUR SYNOLOGY system under which sagetv will run. (on unRAID this is 99,100 respectively, on my personal linux system this is 1000,1000 respectively).

The VIDEO_GUID needs to be group id of the "video" group which generally has read access to the /dev/video# nodes.

SETPERMS if set to Y will change the ownership of all files under /var/media and /opt/sagetv (is your mounted paths) to be the PUID and PGUID so that when you access the files over smb or some other means, you actually have access to those files.

[Carlton Bale]

Thanks Stuckless. This helps tremendously. I now understand what the volume mount commands are doing and got everything in the container mapped.

For UIDs, my initial thought is that everything could go under root. SSH into the Synology system gives root UID/GID/Groups = 0 and and an existing docker container shows similar. Or should I run it under a specific user account?


For the Video_GUID, I'm completely lost. I can't find any reference to that in the Synology system for any user or group, and no reference for /dev/video#. There is no video output from the Synology; it's completely headless. I'm not sure what I need to do that Video_GUID, if anything. Thoughts?

[stuckless]

Originally Posted by Carlton Bale

Thanks Stuckless. This helps tremendously. I now understand what the volume mount commands are doing and got everything in the container mapped.

For UIDs, my initial thought is that everything could go under root. SSH into the Synology system gives root UID/GID/Groups = 0 and and an existing docker container shows similar. Or should I run it under a specific user account?


For the Video_GUID, I'm completely lost. I can't find any reference to that in the Synology system for any user or group, and no reference for /dev/video#. There is no video output from the Synology; it's completely headless. I'm not sure what I need to do that Video_GUID, if anything. Thoughts?

if you can ssh into your NAS, then you can figure out these UIDs like this..

$ cat /etc/group | grep video

It will show something like,

video:x:44:

so 44 is the video guid.

So the next would be to figure out is Synology is owning everything as root or not. So use the 'ls -al' command on some media file that you copied to your nas.

ie, when ssh'd to the your NAS if you have files in /media/videos/ (as an example), then
$ ls -al /media/videos
it will show complete username and group ownerships
-r--r--r-- 1 seans seans 828 Feb 15
if the user shows up as root root then yeah, synology runs as root and owns everything as root. But if it shows something else, that likely that is the user that the NAS is using for file ownerships, and you need to set the PUID and PGUID to their numeric user and group values.

$ cat /etc/passwd | grep seans
seans:x:1000:1000:Sean Stuckless,,,:/home/seans:/bin/bash

in the above case seans user has a user:group ids of 1000 and 1000.

[Carlton Bale]

Thanks for the tip on the "ls -al" command. It looks like the files are owned by the default admin account (1024) and the users account group (100).

Originally Posted by stuckless

if you can ssh into your NAS, then you can figure out these UIDs like this..

$ cat /etc/group | grep video

It will show something like,

video:x:44:

so 44 is the video guid.

I previously tried something similar, and unfortunately, there is nothing in /etc/group for video. Here's the full list via "cat /etc/group", and nothing obviously links to video.

#$_@GID__INDEX@_$276949$
administrators:x:101:sysadmin
avahi:x:84:
bind:x:53:
daemon:x:2:daemon,root
dbus:x:81:
dovecot:x:143:dovecot
ftp:x:21:ftp
http:x:1023:user1
ldap:x:439:
log:x:19:root
lp:x:7:lp
maildrop:x:126:
mysql:x:66:
nobody:x:99:
ntp:x:87:
postfix:x:125:postfix
postgres:x:55:
root:x:0:
rpc:x:32:
smmsp:x:25:sysadmin,smmsp
StorageAnalyzer:x:276949:
SynoFinder:x:195341:
SynologyGuests:x:106:
system:x:1:system
users:x:100:
wheel:x:10:

I don't think I can just remove the video environment variable. It doesn't seem to launch, and I'm assuming that's the issue.

[stuckless]

So the video group only comes into play, later, if you are actually using video hardware. Based on your group list, you can probably set it to 1, and it won't be used until you add video hardware (and you don't add video hardware, then no worries either).

If sagetv is not starting up, then you'll want to check the docker logs to see if there is a problem.

How does synology start your docker container? Does it provide a log?

[Carlton Bale]

Thanks for all of your help. I finally got it up and running. The container was starting properly, but I mistakenly had the container ports set to "automatic", which resulted in them being mapped to 32xxx port numbers on the host. Once I manually mapped the container port the matching port numbers on the host, I was able to connect and configure.

I am still having a problem with network auto-discovery. My SageTV extenders and clients are unable to auto-discover the server. I have to manually connect to the server via IP address. Additional, the server was unable to discover the SiliconDust HDHR turners on my network. I read through multiple other threads but couldn't find an obvious solution. Any suggestion as to where I should start looking?

[7up]

Do you have HDHomerun package installed? I am very interested in this project as I would love to run SageTV server on Synology NAS.

[stuckless]

Originally Posted by Carlton Bale

Thanks for all of your help. I finally got it up and running. The container was starting properly, but I mistakenly had the container ports set to "automatic", which resulted in them being mapped to 32xxx port numbers on the host. Once I manually mapped the container port the matching port numbers on the host, I was able to connect and configure.

I am still having a problem with network auto-discovery. My SageTV extenders and clients are unable to auto-discover the server. I have to manually connect to the server via IP address. Additional, the server was unable to discover the SiliconDust HDHR turners on my network. I read through multiple other threads but couldn't find an obvious solution. Any suggestion as to where I should start looking?

I know for unRAID I have to set the networking to "HOST" (which means that port mapping is not really required, as it exposes the ports directly). What is your network type set to?

[Carlton Bale]

Originally Posted by 7up

Do you have HDHomerun package installed? I am very interested in this project as I would love to run SageTV server on Synology NAS.

That package isn't installed. How can I install it in such a way that it's maintained between upgrades?

I know for unRAID I have to set the networking to "HOST" (which means that port mapping is not really required, as it exposes the ports directly). What is your network type set to?

I had networking set to BRIDGE (separate subnet and gateway) instead of HOST (i.e. "Docker Host" in the Synology initial docker image configuration process.) Changing that should resolve the networking issue.

[7up]

Originally Posted by Carlton Bale

That package isn't installed. How can I install it in such a way that it's maintained between upgrades?

By upgrades am I correct you are referring to DSM? I've been running Version 1.0.1-1 for a while now and have not an issue thus far with each DSM update. Whether it will allow you to see network tuners I don't know but it may be worth trying.

[Carlton Bale]

Originally Posted by 7up

By upgrades am I correct you are referring to DSM? I've been running Version 1.0.1-1 for a while now and have not an issue thus far with each DSM update. Whether it will allow you to see network tuners I don't know but it may be worth trying.

I was talking about maintaining the file through upgrades of the docker image. The mapped directories for /var/media , /var/mediaext , and /opt/sagetv are all that is retained when a new version of docker image auto-installs. So it's necessary for the HDHR files to be maintained outside of the docker image itself.

[7up]

Any updates and were you able to get the tuners recognized?

[Carlton Bale]

Originally Posted by 7up

Any updates and were you able to get the tuners recognized?

No, I haven't figured that out yet. So SageTV Windows is still my primary.

[7up]

Bummer. How difficult would it be to build a native (non-Docker) package?

[Protoman]

So in D&D I play a Death Cleric. The reason this is relevant is that I am raising this post from the dead!


I have been running SageTV from my Synology DS1019+ for the past week, and with great success so far. I found SSHing into the DS1019 and then running the Docker command is much better than the Docker GUI that comes on Synology NASes. I have two Hauppuage HVR-950Q currently attached and will be moving the other two at some point.

So far this looks to be a great solution instead of having a full PC running 24x7 only doing one thing... I also have my movie and music library running in Plex. I am going to experiment with running a Windows 10 Pro as a VM as well.

This is the docker command I am running, and I have the container limited to 2 GB RAM.

sudo docker run -d -m 2g --name sagetv-server \
  -v /volume2/Recordings:/var/media \
  -v /volume1/docker/SageTV/Config:/opt/sagetv \
  -v /volume1/docker/SageTV/resolv.conf:/etc/resolv.cnf \
  --net bridge \
  --env PUID=1024 \
  --env PGID=100 \
  --env VIDEO_GUID=1 \
  --env OPT_GENTUNER=N \
  --env OPT_COMMANDIR=N \
  --env OPT_COMSKIP=Y \
  --env JAVA_MEM_MB=1024 \
  --env VERSION=latest \
  --env OPT_SETPERMS=Y \
  --publish 8080:8080/tcp \
  --publish 31099:31099/tcp \
  --publish 31100:31100/udp \
  --publish 42024:42024/tcp \
  --publish 7818:7818/tcp \
  --publish 7760:7760/tcp \
  --publish 8270:8270/udp \
  --publish 8271:8271/udp \
  --publish 6969:6969/tcp \
  --publish 16867:16867/udp \
  --publish 16869:16869/udp \
  --publish 16881:16881/udp \
  --publish 8000:8000/tcp \
  --publish 9010:9010 \
  --privileged \
  --restart always \
  -v /dev/dvb:/dev/dvb \
  -t -i stuckless/sagetv-server-java11:latest