v18 Help with Docker?
#1
Tongue 
Hello   Big Grin

What I currently have
  1. I have 3 HTPC's running LibreElec 9.2 = Kodi 18.2.
  2. My media is stored on a Synology.
  3. The database is in the Synology package MariaDB5 (setup long time ago, forgot how I did it, because I wanted "one single source of the truth and be able to continue in my bedroom where I left of in my sports room).
  4. I use TinyMediaManager to "prepare" my newly added videos with the right NFO before I manually run an "Update Library" in LibreElec/Kodi.


What I currently am
  1. A complete noob on Docker (amongst others)

What my wish is
  1. TinyMediaManager is a superb application, but it runs very slow in my Windows 7 box (since it has to index my media via SMB on my Synology). So I managed to install it in Docker on my Synology yesterday and there it is very fast: lovely. (This one, should you want to know: https://github.com/romancin/tinymediamanager-docker).
  2. LibreElec/Kodi also takes a lot of time to update the library (for the same reason, I take it: indexing through the network on my Synology, albeit via NFS). So I would love to have an installation of LibreElec on my Synology, assuming that then will be fast as well. I say LibreElec assuming the compatibility with my current database and my other LibreElec HTPC's will be 100% (assumption).
  3. There doesn't exist a LibreElec Docker image, but there does exist a LinuxServer.io headless Kodi Docker image, which, as is known from LinuxServer.io, installs superbly simple. I just installed it. It is Kodi version 18.4.

What my questions are
  1. A Docker question (since I am a Docker noob): how do I connect a Kodi running in a Docker container to my MariaDB that runs outside of Docker, directly as a package on my Synology Server? [A] Can I simply copy the advancedsettings.xml from one of my HTPC's to my Docker-Kodi-container, in the mapped config directory? /volume1/docker/kodi-headless/ is mapped to the Docker mount point /config/.kodi) [B] How do I make the Docker-Kodi talk to the non-Docker MariaDB that runs directly on my Synology (@ http://192.168.2.21/phpMyAdmin/index.php)? The reason I ask here is: I don't want to 'just go ahead and try it', and mess up the whole MariaDB which will also ruin the viewing pleasure on my 3 HTPC's, and will get me into trouble with The Family.
  2. Will the database in MariaDB be messed up since the LibreElec on my HTPC's is Kodi 18.2, where the Docker Kodi version is 18.4? My current MyVideos is MyVideos116, in MariaDB. https://ibb.co/kMQM0nw In other words: suppose I get the previous step solved, will my HTPC's and the Kodi running in Docker all use the same database? Or will 18.4 create a new MyVideos which the 18.2 LibreElecs will not use? (LibreElec isn't on 18.4 yet it seems).

Thank you in advance very much for your help,

Bye,
Reply
#2
Well that didn't work Confused

I copied sources.xml, advancedsettings.xml, profiles.xml, guisettings.xml from one of my working HTPC's (LibreElec 9.0.2/Kodi 18.2) to the Docker Kodi (18.4).

The Docker container itself starts and keeps on running. But when I try to access it, I get "This site can't be reached", "This page isn't working - didn't send any data".

The log is here: zinuxiseyo.kodi (paste)

EDIT: when I put back the original advancedsettings.xml I can connect to Kodi (but I don't have my connection to my MySQL/MariaDB database on my Synology server, so this way of connecting is useless).

The ORIGINAL advancedsettings.xml that is installed with the Docker image is here: agavocuhij.kodi (paste)

The one I copied over from my working LibreElec HTPC is here: fucuqujanu (paste)

What might be causing the problem in my own (LibreElec) advancedsettings.xml?

(PS My Synology is running the MariaDB/MySQL on itself @192.168.2.21, port 3306 (so not in Docker). I can access it fine from the LAN with PHPMyAdmin).

Thank you for any help,

Bye,
Reply
#3
Ok, I copied a bunch of parameters from the Docker container advancedsettings.xml into the advancedsettings.xml of my LibreElec, and it seems to be doing something now.

I however would like to know which particular setting it is in advancedsettings.xml that changed it into working? Would one of the Gods of Kodi be willing to answer my question?

Also, it says "lost websocket connection", and many images are not showing up, even though I copied the neccessary files per step 5 of: MySQL/Setting_up_Kodi (wiki)

So currently my screen in DockerKodi on my Synology looks like this: https://ibb.co/R7RqSBB

If I click ALL MOVIES I get: https://ibb.co/Kz37fNS
Reply
#4
It's completely randomly showing movies: https://ibb.co/3dvGRBr

Would anybody happen to know how I can fix this?

Or should I simply forget about it?

Thank you,

Bye,
Reply
#5
Ok, next step:

After changing NFS permissions to * in my Synology, it now complains about Movie and TV-directories not existing: cejiqovela.kodi (paste)

All these directories DO exist, and contain movies/tv shows.

How can I fix this?

Thank you,

Bye,
Reply
#6
I don't have a Synology, but your error log indicates that Kodi can't see those directories. 

What does '*' mean ?  Anyone can connect ?  Because by the look of it, they can't.   You can fix it by setting the permissions for your NFS exports properly because if the directories exist and are properly exported and available to the network then the only other thing stopping Kodi seeing them is the access permissions for the NFS exports. 

I don't have a clue how to do that on a Synology, but the export permissions on both of my file servers are 192.168.1.1/24(rw,all_squash,insecure,no_subtree_check)  That means any machine on my local network (192.168.1.1/24), read/write access (rw), map all users to the anonymous user (all_squash), use ports over 1024 for connections (insecure), don't check if the file requested is in the exported tree as well as the filesystem (no_subtree_check).
Learning Linux the hard way !!
Reply
#7
(2019-09-12, 13:06)black_eagle Wrote: I don't have a Synology, but your error log indicates that Kodi can't see those directories. 

What does '*' mean ?  Anyone can connect ?  Because by the look of it, they can't.   You can fix it by setting the permissions for your NFS exports properly because if the directories exist and are properly exported and available to the network then the only other thing stopping Kodi seeing them is the access permissions for the NFS exports. 

I don't have a clue how to do that on a Synology, but the export permissions on both of my file servers are 192.168.1.1/24(rw,all_squash,insecure,no_subtree_check)  That means any machine on my local network (192.168.1.1/24), read/write access (rw), map all users to the anonymous user (all_squash), use ports over 1024 for connections (insecure), don't check if the file requested is in the exported tree as well as the filesystem (no_subtree_check).

Thank you very much for your reply(!)

I changed the Synology settings, it seems to have changed many error messages.

My Synology permissions now look like this: https://ibb.co/tpPS8FD

(Using map to guest didn't work, since still hardly any thumbs for my movies. Map users to admin showed many more thumbnails for my movies - though not all (which are shown in LibreElec on my HTPC).

So now I have two three problems left:

1. The logs complains about directories that aren't there. It is right, they no longer exist. So why does it complain about (and where did it get the information about the deleted directories from in the first place? (??)). uwucupijug.kodi (paste)

EDIT: hmmm. Aside from the TV-shows directories, it also complains about some movie directories not being there (but only few movie directories not being there, as opposed to previous, when it was a big load of movies). The movie-directories DO exist, however:


https://ibb.co/5BWmcPV

https://ibb.co/K9QvsHg

Thank you for your help,

bye,



2. It still doesn't load all the images: https://ibb.co/8NbWgzP

3.  It still constantly complains about: "lost websocket connection". It's running on the Synology and the Synology firewall is off.
Reply
#8
If there are directories in the log that actually don't exist and therefore Kodi is skipping them, then the paths must still be in your database.  Try cleaning your database and see if that helps.
Learning Linux the hard way !!
Reply
#9
(2019-09-12, 22:59)black_eagle Wrote: If there are directories in the log that actually don't exist and therefore Kodi is skipping them, then the paths must still be in your database.  Try cleaning your database and see if that helps.

Thanks for your reply. I agree with you, a library clean should solve it. But it doesn't.

I cleaned the library 3 times from one of my HTPC's (the Docker Kodi headless doesn't have a library clean option), then ran the library update again from the Docker Kodi, and the error remains exactly the same: for a number of TV shows that aren't there anymore it keeps on complaining:
Quote:2019-09-14 17:37:28.294 T:139761613469440 WARNING: Process directory 'nfs://192.168.2.21/volume1/media/vids/Series/The Fresh Prince of Bel-Air/' does not exist - skipping scan.
Reply
#10
(2019-09-14, 19:49)JumboMumbo Wrote:
(2019-09-12, 22:59)black_eagle Wrote: If there are directories in the log that actually don't exist and therefore Kodi is skipping them, then the paths must still be in your database.  Try cleaning your database and see if that helps.

Thanks for your reply. I agree with you, a library clean should solve it. But it doesn't.

I cleaned the library 3 times from one of my HTPC's (the Docker Kodi headless doesn't have a library clean option), then ran the library update again from the Docker Kodi, and the error remains exactly the same: for a number of TV shows that aren't there anymore it keeps on complaining:
Quote:2019-09-14 17:37:28.294 T:139761613469440 WARNING: Process directory 'nfs://192.168.2.21/volume1/media/vids/Series/The Fresh Prince of Bel-Air/' does not exist - skipping scan.

Hmmm, I ran an update from my normal, non Docker, HTPC, this gives the same errors in the log. So it isn't just Docker that has problems. I'll create a new thread for this problem.
Reply
#11
Check what you have added into your sources.  Maybe you have added full paths to some shows instead of a root path that Kodi would follow.  If you just go around deleting directories without sorting out your sources and removing stuff from inside Kodi first then your database will more than likely end up in a mess and contain paths that aren't valid anymore.
Learning Linux the hard way !!
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Help with Docker?00