[JumboMumbo]

Hello  

What I currently have

1. One Kodi headless (18.4, Linuxserver.io) running in Docker on my Synology in DSM 6.2 (and 3 normal NUC HTPC's in my LAN).
   
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. The Synology does not have any firewall enabled.
   

The problem

1. I keep on getting the above error messages.
   
2. I do have about 75% of all the video images in my Kodi Docker (100% exists on my normal HTPC's in LAN).
   

Log file: https://paste.kodi.tv/eseqeyaray.kodi

Thank you for any help,

Bye,

[asavah]

I see quite a few problems:
1) You are trying to do a weird and advanced setup without needed knowledge for the underlying technology.
2) ERROR: NFS: Failed to mount nfs share: /volume1/zsabnzbd - check you nfs server permissions, docker has to have access to your nfs server shares
3) ERROR: CCurlFile::Exists - Failed: Couldn't resolve host name(6) for http://image.tmdb.org/t/p/original/65L88...CyB5hQ.jpg - make sure your docker has internet access.

[JumboMumbo]

I see quite a few problems:
1) You are trying to do a weird and advanced setup without needed knowledge for the underlying technology.
2) ERROR: NFS: Failed to mount nfs share: /volume1/zsabnzbd - check you nfs server permissions, docker has to have access to your nfs server shares
3) ERROR: CCurlFile::Exists - Failed: Couldn't resolve host name(6) for http://image.tmdb.org/t/p/original/65L88...CyB5hQ.jpg - make sure your docker has internet access.

Thank you for your reply

1. I'm sorry if it is considered weird. All I want is not having to manually start up one of my HTPC's in order to update my library, when my Synology is allways on.
2. Fixed (it's my SABNZBD download directory). It didn't change the problem 'though, the error messages remain.
3. This is a tricky one: my Synology has access to the internet, but it seems the Docker Kodi image doesn't have the PING command, so I can't test if it has access. It should have access though, as all Dockers do have access: https://ibb.co/VMNJdxf and connection from another Docker container: https://ibb.co/LNQYGtn.