December 30, 201411 yr Author 8080 definitely free. In fact I can see the Kodi web interface it is just content empty. Struggling to carve out quality time to debug this. Suspect it will be a simple "doh" moment Once the new year starts I should have time as I want to deprecate a VM dedicated to this so its important to me. PS added in kodi-send on a test build i'm running at the moment , it's doing the main compile of kodi as i type this. kodi-send has installed already (from the ppa, which i removed after the install of kodi-send) so hopefully it should be there in the image when completed. not certain how to use it though.
December 30, 201411 yr I tried your docker from the template, but I am getting errors *** Killing all processes... *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... I changed the port to 8089 and I changed the kodi path to /mnt/cache/kodi which has been created but it's empty. so I don't quite know where else to look.
December 30, 201411 yr Author I tried your docker from the template, but I am getting errors *** Killing all processes... *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... I changed the port to 8089 and I changed the kodi path to /mnt/cache/kodi which has been created but it's empty. so I don't quite know where else to look. i've just deleted my container and image from my unraid and deleted my local config files so i am in the same start position as you are. i'm now readding the image from my template.
December 30, 201411 yr Author I tried your docker from the template, but I am getting errors *** Killing all processes... *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... I changed the port to 8089 and I changed the kodi path to /mnt/cache/kodi which has been created but it's empty. so I don't quite know where else to look. root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles creating advancedsettings.xml *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 20 Can't open display The command finished successfully!
December 30, 201411 yr Author I tried your docker from the template, but I am getting errors *** Killing all processes... *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... I changed the port to 8089 and I changed the kodi path to /mnt/cache/kodi which has been created but it's empty. so I don't quite know where else to look. 2 questions, 1 . are you using my normal repo or have you somehow got my private repo ? 2. have you tried deleting the image and container, the contents of /mnt/cache/kodi and pressing reload info on the docker page in unraid webui ?
December 30, 201411 yr I am using the normal repro, no private one root@localhost:# /usr/bin/docker run -d --name="KODI-Headless" --net="bridge" --privileged="true" -e MYSQLip="192.168.0.24" -e MYSQLport="3306" -e MYSQLuser="xbmc" -e MYSQLpass="xbmc" -e TZ="Europe/London" -p 8089:8080/tcp -v "/mnt/cache/appdata/kodi":"/root/.kodi":rw sparklyballs/headless-kodi-helix 3788b29dea96d5867957bbb5ed3aa7056a78d207d4da82f36bcc291aa86d2dd4 The command finished successfully! shortly afterwards this again root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... root@Tower:/mnt/cache/appdata/kodi# ls -ltr total 0 root@Tower:/mnt/cache/appdata/kodi# cd .. root@Tower:/mnt/cache/appdata# ls -ltr total 0 drwxrwxrwx 1 nobody users 0 Dec 30 12:30 kodi/
December 30, 201411 yr Author I am using the normal repro, no private one root@localhost:# /usr/bin/docker run -d --name="KODI-Headless" --net="bridge" --privileged="true" -e MYSQLip="192.168.0.24" -e MYSQLport="3306" -e MYSQLuser="xbmc" -e MYSQLpass="xbmc" -e TZ="Europe/London" -p 8089:8080/tcp -v "/mnt/cache/appdata/kodi":"/root/.kodi":rw sparklyballs/headless-kodi-helix 3788b29dea96d5867957bbb5ed3aa7056a78d207d4da82f36bcc291aa86d2dd4 The command finished successfully! shortly afterwards this again root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles cp: target '/opt/kodi-server/share/kodi/portable_data/' is not a directory creating advancedsettings.xml cp: cannot create regular file '/opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml': No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory sed: can't read /opt/kodi-server/share/kodi/portable_data/userdata/advancedsettings.xml: No such file or directory *** /etc/my_init.d/firstrun.sh failed with status 2 *** Killing all processes... did you reload info ? because that's the old mapping for config files pre the last update to running in portable mode. the reload info button is hidden, just mouse over the bar and it appears.
December 30, 201411 yr Author -v "/mnt/cache/appdata/kodi":"/root/.kodi":rw it's there the -v mapping is now /opt/kodi-server/share/kodi/portable_data to reflect the change to running in portable mode to better fit with unraid permissions.
December 30, 201411 yr Author I am going to guess that at some point the -v mapping was dropped by mistake. i've added kodi-send in a test build and it works sending a quit signal to my main kodi player box. not certain how to see if it sends to the kodi instance in the container.
December 30, 201411 yr Author I am going to guess that at some point the -v mapping was dropped by mistake. exec'd into my test-build and issued kodi-send --host=127.0.0.1 --port=9777 --action="Quit" it quits and then respawns kodi (because of it being in runit)
December 30, 201411 yr thanks was not aware of this, changed this now, and now the output has changed to this root@localhost:# /usr/bin/docker logs --tail=350 KODI-Headless *** Running /etc/my_init.d/firstrun.sh... creating datafiles creating advancedsettings.xml *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 18 Can't open display terminate called after throwing an instance of 'dbiplus::DbErrors' Can't open display The command finished successfully!
December 30, 201411 yr Author @NAS i'm wondering whether kodi-send can be used via command line in unraid to the container to trigger an update library.
December 30, 201411 yr Hi well I started from scratch with some success, I can now populate the kodi window but no movies are displaying not sure how or where to put the path to my movie directory. I don't want to start trying things at this stage that I'm this close does the movie path have to be inserted in host path and container volume of the kodi container or is this something done in another container? Lou
December 30, 201411 yr Author Hi well I started from scratch with some success, I can now populate the kodi window but no movies are displaying not sure how or where to put the path to my movie directory. I don't want to start trying things at this stage that I'm this close does the movie path have to be inserted in host path and container volume or is this something done in another container? Lou do you have a mysql based setup with a library scanned in to it ?
December 30, 201411 yr Hi well I started from scratch with some success, I can now populate the kodi window but no movies are displaying not sure how or where to put the path to my movie directory. I don't want to start trying things at this stage that I'm this close does the movie path have to be inserted in host path and container volume or is this something done in another container? Lou do you have a mysql based setup with a library scanned in to it ? No, not sure how to do this sorry very new with this stuff. By the way it seem for what ever reason the docker.img was corrupt I reinstalled unraid and loaded docker container and worked first time. Lou
December 30, 201411 yr Author Hi well I started from scratch with some success, I can now populate the kodi window but no movies are displaying not sure how or where to put the path to my movie directory. I don't want to start trying things at this stage that I'm this close does the movie path have to be inserted in host path and container volume or is this something done in another container? Lou do you have a mysql based setup with a library scanned in to it ? No, not sure how to do this sorry very new with this stuff. By the way it seem for what ever reason the docker.img was corrupt I reinstalled unraid and loaded docker container and worked first time. Lou ok, cool. this is primarily designed for use in a kodi environment with a mysql/mariadb library setup. it's so sickbeard, couchpotato etc... can send updates to the library, it does have a upnp element to it, but i've never used that and don't know anything about it or it's capabilties in this usage if i'm honest. most people use a mysql setup for their kodi/xbmc library to have multiple play units have the same library and resume points and watched status etc.... although it can be used in a single player home and have the server handle library updates sent from your downloads apps etc, all on unraid. makes for a pretty neat setup IMHO.
December 30, 201411 yr I am going to guess that at some point the -v mapping was dropped by mistake. exec'd into my test-build and issued kodi-send --host=127.0.0.1 --port=9777 --action="Quit" it quits and then respawns kodi (because of it being in runit) FYI i dont think you need host or port if your running it locally its one of the cool things about it
December 30, 201411 yr Author I am going to guess that at some point the -v mapping was dropped by mistake. exec'd into my test-build and issued kodi-send --host=127.0.0.1 --port=9777 --action="Quit" it quits and then respawns kodi (because of it being in runit) FYI i dont think you need host or port if your running it locally its one of the cool things about it i'm wondering whether it can be used in a docker run command to the container to initiate a library update of the container kodi instance, there is a library update command in the list of commands and i sent it from the container to my main player box and it triggered a library update there.
December 30, 201411 yr So do I have to point mariadb to my movie directory in the mariadb Host path and container volume? Lou
December 30, 201411 yr I am going to guess that at some point the -v mapping was dropped by mistake. exec'd into my test-build and issued kodi-send --host=127.0.0.1 --port=9777 --action="Quit" it quits and then respawns kodi (because of it being in runit) FYI i dont think you need host or port if your running it locally its one of the cool things about it i'm wondering whether it can be used in a docker run command to the container to initiate a library update of the container kodi instance, there is a library update command in the list of commands and i sent it from the container to my main player box and it triggered a library update there. This is exactly the kind of thing you can do :0 kodi-send --action="UpdateLibrary(video)" kodi-send --action="CleanLibrary(video)"
December 30, 201411 yr Author So do I have to point mariadb to my movie directory in the mariadb Host path and container volume? Lou nope, you should point the maraidb host path to a path on your unraid box to save config files. then on another kodi box make an advancedsettings.xml file in the userdata folder (differs on location, depending on OS) with the same mysql/mariadb settings as you set for the container in it. similar to this, but changing the host settings to suit your setup. <advancedsettings> <videodatabase> <type>mysql</type> <host>192.168.1.90</host> <port>3306</port> <user>kodi</user> <pass>kodi</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>192.168.1.90</host> <port>3306</port> <user>kodi</user> <pass>kodi</pass> </musicdatabase> </advancedsettings>
December 30, 201411 yr Author So do I have to point mariadb to my movie directory in the mariadb Host path and container volume? Lou nope, you should point the maraidb host path to a path on your unraid box to save config files. then on another kodi box make an advancedsettings.xml file in the userdata folder (differs on location, depending on OS) with the same mysql/mariadb settings as you set for the container in it. similar to this, but changing the host settings to suit your setup. <advancedsettings> <videodatabase> <type>mysql</type> <host>192.168.1.90</host> <port>3306</port> <user>kodi</user> <pass>kodi</pass> </videodatabase> <musicdatabase> <type>mysql</type> <host>192.168.1.90</host> <port>3306</port> <user>kodi</user> <pass>kodi</pass> </musicdatabase> </advancedsettings> you should be aware that doing this on an already scanned in library not setup for mysql will likely mean you rescanning everything back in, do you have much of an existing library ?
December 30, 201411 yr Author I am going to guess that at some point the -v mapping was dropped by mistake. exec'd into my test-build and issued kodi-send --host=127.0.0.1 --port=9777 --action="Quit" it quits and then respawns kodi (because of it being in runit) FYI i dont think you need host or port if your running it locally its one of the cool things about it i'm wondering whether it can be used in a docker run command to the container to initiate a library update of the container kodi instance, there is a library update command in the list of commands and i sent it from the container to my main player box and it triggered a library update there. This is exactly the kind of thing you can do :0 kodi-send --action="UpdateLibrary(video)" kodi-send --action="CleanLibrary(video)" cool, i'm uncertain about how to pass that from the unraid command line to the container (not in exec mode), but i'll work it out.
Archived
This topic is now archived and is closed to further replies.