2017-01-10, 20:41
On jarvis release tag, I too was able to access the webserver after disabling add on updates by setting addonupdates to 2 in the guisettings.xml file. Sweet!
However, it looks as though the container is in a boot loop. When I sit and cat the log over and over again it looks like the container is stuck in a boot loop because I get continuous repeated startup messages (including the one that indicates the webserver being started). Is this a bug? As anyone seen this on the jarvis (16.1) tag? Any advice on how can I confirm whether or not the kodi container is running stably or is endlessly starting up over and over again? The webserver is behaving fine...
However, it looks as though the container is in a boot loop. When I sit and cat the log over and over again it looks like the container is stuck in a boot loop because I get continuous repeated startup messages (including the one that indicates the webserver being started). Is this a bug? As anyone seen this on the jarvis (16.1) tag? Any advice on how can I confirm whether or not the kodi container is running stably or is endlessly starting up over and over again? The webserver is behaving fine...