2015-05-20, 09:56
(2015-05-19, 22:56)B3rt Wrote: I also have a synology NAS and running docker.
How do you enter the kodi container by SSH?
I tried port forwarding but when i connect my SSH connection is simply not accepted
SSH into the NAS first, then use the 'docker' command from within the NAS.
First run 'docker ps' to get a list of whats running. It'll spit out something like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
18e7d80a897f registry.hub.docker.com/sparklyballs/headless-kodi-helix:latest "/sbin/my_init" 6 days ago Up 5 days 9777/udp, 0.0.0.0:8008->8080/tcp headless-kodi-helix
Next, run 'docker exec -it 18e7d80a897f bash' (replacing 18e7d80a897f with the container ID with the output from running docker ps above). You'll then be in a shell running in the container.
(2015-05-19, 22:56)B3rt Wrote: Also i have on all my kodi clients a sources.xml with the correct paths to my media (located on the nas), how do i set this in kodi headless (in docker on a synology nas)?
I do have the media vissible on the web interface, but i don;t understand how this headless version scan for new media and where it scans, i cannot set this?
Does it scan automaticly using cron/intervals or more like watchdog?
Who can explain how this works and how to set this?
Not sure I can help you there... I have Sickbeard adding via the web API (rather than relying on the headless Kodi to scan).
Though I did also copy across the sources.xml / passwords.xml files from an existing Kodi client into the container's Kodi profile folder (/opt/kodi-server/share/kodi/portable_data/userdata), just in case.
Maybe the XBMC Library Updater addon might do what you need?