Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[DOCKER] kodi isengard headless

Featured Replies

  • Author

well

can you say which are both pros and cons of both?

 

pros of kodi headless.

 

i wrote the docker...

 

emby.. dunno don't use it.

  • 1 month later...
  • Replies 110
  • Views 26.3k
  • Created
  • Last Reply

Hello

 

A totally Noob question about this. I have KODI on many devices in my house and I use MySQL centralized database via advancedsettings.xml

 

Every time I add new media I manually run library scan on one of the devices (usually my main PC). How does this headless docker help me? I understand that it's on 24/7 but do I still need to manually trigger the library update or does it somehow watches for changes in my media library folders?

 

Ideally I would like something like Plex where adding new files triggers the update by itself.

 

thanks

  • 1 month later...

Is it possible to change the webserver to chorus, or possibly chorus2, and ports etc ? They've apparently gotten pretty good at the streaming of stuff from through chorus (although I''m not sure how many formats are supported). So people who don't need transcoding would have another streaming option outside of emby and plex, or using yatse. Their default webserver is GOD awful, but it does have the update and clean library buttons which is nice, especially for a centralized DB. Chorus is much nicer but it lacks the "clean" button, in an  easily accessible menu. You can access a tools menu through chorus that allows you to very easily send a whole ton of JSON commands (including all the "clean library" functions, so they are accessible through Chorus) in various ways to your kodi box. I would think it would be a much nicer option and infinitely more useful in your docker Sparkly, but obviously just a suggestion :D 

I'm thinking of installing this docker and moving to a shared DB, but I've never used a central DB. I have all giga networking and cat6, a more than capable home router, but I have a fairly large library and I am wondering how much noticeable lag people get when you just hold down the button on your remote and fly through your movies? Or if you try to play trailers, or bring up extended metadata is there any noticeable difference?  This would definitely be superior to what I do now, which is have each kodi box update at startup, and I have notifications from all of my automation to all of my different kodi boxes as well and if one isn't on, it obviously doesn't update until it wakes back up. This would eliminate that as well. In my opinion going to all of the trouble to build a nice NAS and collection, and proper htpc's, I want the best possible media experience. Meaning that I don't want any noticeable lag at all when browsing just about whatever sized library. I have the newest stable Isengard and Aeon Nox 3 on all of my htpc's and all of the nicer 1080p fanart, etc. enabled. What's the experience like for you guys?

There's no noticeable lag when using a shared database.  But, each client by default will store its own copies of the artwork.  And depending upon the size of the libraries, that can take a while to initially populate on each client.

Sorry for the ignorance, but do you mean initially there is some lag when it's each client first gets something added, or initially at startup each time? So it would just take some time to sync, but the day to day has no noticeable difference? Sounds great.

day to day no problem.  First time populating the artwork (one shot deal) takes a while

To be honest, probably better off switching to the linuxserver.io version at some point as Sparklyballs I imagine won't be developing this version any more.

  • Author

To be honest, probably better off switching to the linuxserver.io version at some point as Sparklyballs I imagine won't be developing this version any more.

 

Indeed.

Thanks very much, posted my question over there  8)

  • 2 months later...

Hi all!

 

I managed to get this headless version to work on my Synology NAS (DS412+)

 

Z0nNH0K.png?2

 

 

I have access to it, but cover art doesn't show up or just partly.

 

FdwPBJd.png?1

 

o16rd0H.png?1

 

Also I get this error message all the time: "Connection to server lost" When I refresh the message disappears, but comes back afterwards... I don't know if it's related.

 

 

I'm using path substitution in advancedsettings.xml for thumbnails to share them among my other Kodi clients

     	<substitute>
    		<from>special://masterprofile/Thumbnails/</from>
     		<to>nfs://my.ip.address/volume1/XBMCmedia/Thumbnails/</to>
    	</substitute>

 

 

I didn't mount a share in the volume tab, maybe that can be the issue??

 

dKTKMUK.png?1

 

 

Some suggested that it has someting to do with NFS permissions. As I know, everything is set right.

 

DL4qCd3.png?1

 

 

Does anyone has a suggestion on what to change or how to get it to work?

 

Thanks!

 

Logs:

2016-02-05 09:17:02	stdout	Feb  5 09:17:01 Kodi-Isengard /USR/SBIN/CRON[202]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 09:02:50	stdout	Feb  5 09:02:49 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-05 09:02:49	stdout	*** Runit started as PID 15
2016-02-05 09:02:49	stdout	*** Booting runit daemon...
2016-02-05 09:02:49	stdout	*** Running /etc/rc.local...
2016-02-05 09:02:49	stdout	using existing advancedsettings.xml
2016-02-05 09:02:49	stdout	using existing datafiles
2016-02-05 09:02:49	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-05 09:02:49	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-05 09:01:48	stdout	*** Killing all processes...
2016-02-05 09:01:48	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-05 08:57:36	stdout	Feb  5 08:57:36 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-05 08:57:35	stdout	*** Runit started as PID 15
2016-02-05 08:57:35	stdout	*** Booting runit daemon...
2016-02-05 08:57:35	stdout	*** Running /etc/rc.local...
2016-02-05 08:57:35	stdout	using existing advancedsettings.xml
2016-02-05 08:57:35	stdout	using existing datafiles
2016-02-05 08:57:35	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-05 08:57:35	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-05 08:57:29	stdout	*** Killing all processes...
2016-02-05 08:57:29	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-05 08:26:34	stdout	Feb  5 08:26:33 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-05 08:26:33	stdout	*** Runit started as PID 15
2016-02-05 08:26:33	stdout	*** Booting runit daemon...
2016-02-05 08:26:33	stdout	*** Running /etc/rc.local...
2016-02-05 08:26:33	stdout	using existing advancedsettings.xml
2016-02-05 08:26:32	stdout	using existing datafiles
2016-02-05 08:26:32	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-05 08:26:32	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-05 08:26:28	stdout	*** Killing all processes...
2016-02-05 08:26:28	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-05 08:17:50	stdout	Feb  5 08:17:50 Kodi-Isengard syslog-ng[23]: syslog-ng starting up; version='3.5.3'
2016-02-05 08:17:49	stdout	*** Runit started as PID 15
2016-02-05 08:17:49	stdout	*** Booting runit daemon...
2016-02-05 08:17:49	stdout	*** Running /etc/rc.local...
2016-02-05 08:17:49	stdout	using existing advancedsettings.xml
2016-02-05 08:17:48	stdout	using existing datafiles
2016-02-05 08:17:48	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-05 08:17:48	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-05 08:17:40	stdout	*** Killing all processes...
2016-02-05 08:17:39	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-05 08:17:02	stdout	Feb  5 08:17:01 Kodi-Isengard /USR/SBIN/CRON[452]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 07:17:01	stdout	Feb  5 07:17:01 Kodi-Isengard /USR/SBIN/CRON[449]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 06:25:01	stdout	Feb  5 06:25:01 Kodi-Isengard /USR/SBIN/CRON[325]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
2016-02-05 06:17:02	stdout	Feb  5 06:17:02 Kodi-Isengard /USR/SBIN/CRON[322]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 05:17:02	stdout	Feb  5 05:17:01 Kodi-Isengard /USR/SBIN/CRON[319]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 04:17:01	stdout	Feb  5 04:17:01 Kodi-Isengard /USR/SBIN/CRON[316]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 03:17:02	stdout	Feb  5 03:17:01 Kodi-Isengard /USR/SBIN/CRON[313]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 02:17:02	stdout	Feb  5 02:17:01 Kodi-Isengard /USR/SBIN/CRON[310]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 01:17:01	stdout	Feb  5 01:17:01 Kodi-Isengard /USR/SBIN/CRON[307]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-05 00:17:02	stdout	Feb  5 00:17:01 Kodi-Isengard /USR/SBIN/CRON[277]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-04 23:33:25	stdout	Feb  4 23:33:24 Kodi-Isengard syslog-ng[22]: syslog-ng starting up; version='3.5.3'
2016-02-04 23:33:24	stdout	*** Runit started as PID 15
2016-02-04 23:33:24	stdout	*** Booting runit daemon...
2016-02-04 23:33:24	stdout	*** Running /etc/rc.local...
2016-02-04 23:33:24	stdout	using existing advancedsettings.xml
2016-02-04 23:33:24	stdout	using existing datafiles
2016-02-04 23:33:24	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 23:33:24	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 23:23:50	stdout	*** Killing all processes...
2016-02-04 23:23:50	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 23:17:07	stdout	Feb  4 23:17:07 Kodi-Isengard syslog-ng[23]: syslog-ng starting up; version='3.5.3'
2016-02-04 23:17:06	stdout	*** Runit started as PID 15
2016-02-04 23:17:06	stdout	*** Booting runit daemon...
2016-02-04 23:17:06	stdout	*** Running /etc/rc.local...
2016-02-04 23:17:05	stdout	using existing advancedsettings.xml
2016-02-04 23:17:05	stdout	using existing datafiles
2016-02-04 23:17:05	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 23:17:05	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 22:54:53	stdout	Feb  4 22:54:53 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-04 22:54:51	stdout	*** Runit started as PID 15
2016-02-04 22:54:51	stdout	*** Booting runit daemon...
2016-02-04 22:54:51	stdout	*** Running /etc/rc.local...
2016-02-04 22:54:50	stdout	using existing advancedsettings.xml
2016-02-04 22:54:48	stdout	using existing datafiles
2016-02-04 22:54:48	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 22:54:47	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 22:53:58	stdout	*** Killing all processes...
2016-02-04 22:53:56	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 22:39:55	stdout	Feb  4 22:39:54 Kodi-Isengard syslog-ng[22]: syslog-ng starting up; version='3.5.3'
2016-02-04 22:39:52	stdout	*** Runit started as PID 15
2016-02-04 22:39:52	stdout	*** Booting runit daemon...
2016-02-04 22:39:52	stdout	*** Running /etc/rc.local...
2016-02-04 22:39:51	stdout	using existing advancedsettings.xml
2016-02-04 22:39:50	stdout	using existing datafiles
2016-02-04 22:39:50	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 22:39:49	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 22:39:15	stdout	*** Killing all processes...
2016-02-04 22:39:15	stdout	*** Shutting down runit daemon (PID 19)...
2016-02-04 22:30:43	stdout	Feb  4 22:30:42 Kodi-Isengard syslog-ng[27]: syslog-ng starting up; version='3.5.3'
2016-02-04 22:30:42	stdout	*** Runit started as PID 19
2016-02-04 22:30:42	stdout	*** Booting runit daemon...
2016-02-04 22:30:42	stdout	*** Running /etc/rc.local...
2016-02-04 22:30:40	stdout	using existing advancedsettings.xml
2016-02-04 22:30:39	stdout	using existing datafiles
2016-02-04 22:30:39	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 22:30:39	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 22:30:12	stdout	*** Killing all processes...
2016-02-04 22:30:11	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 22:29:41	stdout	Feb  4 22:29:41 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-04 22:29:40	stdout	*** Runit started as PID 15
2016-02-04 22:29:40	stdout	*** Booting runit daemon...
2016-02-04 22:29:40	stdout	*** Running /etc/rc.local...
2016-02-04 22:29:39	stdout	using existing advancedsettings.xml
2016-02-04 22:29:34	stdout	using existing datafiles
2016-02-04 22:29:34	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 22:29:33	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 22:21:13	stdout	*** Killing all processes...
2016-02-04 22:21:12	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 22:17:02	stdout	Feb  4 22:17:01 Kodi-Isengard /USR/SBIN/CRON[507]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
2016-02-04 21:59:30	stdout	Feb  4 21:59:29 Kodi-Isengard syslog-ng[22]: syslog-ng starting up; version='3.5.3'
2016-02-04 21:59:29	stdout	*** Runit started as PID 15
2016-02-04 21:59:29	stdout	*** Booting runit daemon...
2016-02-04 21:59:29	stdout	*** Running /etc/rc.local...
2016-02-04 21:59:28	stdout	using existing advancedsettings.xml
2016-02-04 21:59:28	stdout	using existing datafiles
2016-02-04 21:59:27	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 21:59:27	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 21:58:33	stdout	Feb  4 21:58:33 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-04 21:58:32	stdout	*** Runit started as PID 15
2016-02-04 21:58:32	stdout	*** Booting runit daemon...
2016-02-04 21:58:32	stdout	*** Running /etc/rc.local...
2016-02-04 21:58:32	stdout	using existing advancedsettings.xml
2016-02-04 21:58:31	stdout	using existing datafiles
2016-02-04 21:58:31	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 21:58:31	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 21:57:25	stdout	*** Killing all processes...
2016-02-04 21:57:24	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 21:57:20	stdout	Feb  4 21:57:20 Kodi-Isengard syslog-ng[22]: syslog-ng starting up; version='3.5.3'
2016-02-04 21:57:19	stdout	*** Runit started as PID 15
2016-02-04 21:57:19	stdout	*** Booting runit daemon...
2016-02-04 21:57:19	stdout	*** Running /etc/rc.local...
2016-02-04 21:57:19	stdout	using existing advancedsettings.xml
2016-02-04 21:57:18	stdout	using existing datafiles
2016-02-04 21:57:18	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 21:57:18	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 21:56:12	stdout	Feb  4 21:56:11 Kodi-Isengard syslog-ng[25]: syslog-ng starting up; version='3.5.3'
2016-02-04 21:56:10	stdout	*** Runit started as PID 16
2016-02-04 21:56:10	stdout	*** Booting runit daemon...
2016-02-04 21:56:10	stdout	*** Running /etc/rc.local...
2016-02-04 21:56:10	stdout	using existing advancedsettings.xml
2016-02-04 21:56:09	stdout	using existing datafiles
2016-02-04 21:56:09	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 21:56:09	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-02-04 21:55:15	stdout	*** Killing all processes...
2016-02-04 21:55:15	stdout	*** Shutting down runit daemon (PID 15)...
2016-02-04 21:54:49	stdout	Feb  4 21:54:48 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-02-04 21:54:47	stdout	*** Runit started as PID 15
2016-02-04 21:54:47	stdout	*** Booting runit daemon...
2016-02-04 21:54:47	stdout	*** Running /etc/rc.local...
2016-02-04 21:54:46	stdout	using existing advancedsettings.xml
2016-02-04 21:54:46	stdout	using existing datafiles
2016-02-04 21:54:45	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-02-04 21:54:45	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-01-06 20:27:50	stdout	*** Killing all processes...
2016-01-06 20:27:50	stdout	*** Shutting down runit daemon (PID 16)...
2016-01-06 20:24:22	stdout	Jan  6 20:24:21 Kodi-Isengard syslog-ng[24]: syslog-ng starting up; version='3.5.3'
2016-01-06 20:24:21	stdout	*** Runit started as PID 16
2016-01-06 20:24:21	stdout	*** Booting runit daemon...
2016-01-06 20:24:21	stdout	*** Running /etc/rc.local...
2016-01-06 20:24:21	stdout	using existing advancedsettings.xml
2016-01-06 20:24:20	stdout	using existing datafiles
2016-01-06 20:24:20	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-01-06 20:24:20	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
2016-01-06 19:22:15	stdout	*** Killing all processes...
2016-01-06 19:22:15	stdout	*** Shutting down runit daemon (PID 19)...
2016-01-06 19:17:54	stdout	Jan  6 19:17:54 Kodi-Isengard syslog-ng[28]: syslog-ng starting up; version='3.5.3'
2016-01-06 19:17:53	stdout	*** Runit started as PID 19
2016-01-06 19:17:53	stdout	*** Booting runit daemon...
2016-01-06 19:17:53	stdout	*** Running /etc/rc.local...
2016-01-06 19:17:53	stdout	creating advancedsettings.xml
2016-01-06 19:17:36	stdout	creating datafiles
2016-01-06 19:17:36	stdout	*** Running /etc/my_init.d/firstrun.sh...
2016-01-06 19:17:36	stdout	*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...

As indicated on the first post, this is for Unraid support only.  If you want support for a different platform please post on our forums at linuxserver.io or visit our IRC channel #linuxserver.io

 

 

EDIT: Just realised this is Sparklyballs' version which is now deprecated. Please use the linuxserver.io version.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.