sparklyballs

https://github.com/ejurgensen/forked-daapd#spotify last line in particular "You also can only listen to your music by letting forked-daapd do the playback - so that means you can't stream from forked-daapd to iTunes." ^^^ redundant.

Are you by any chance using protected shares ?

the space in the volume name is the issue, i'm not sure what the fix is for that regards unraid and docker other than don't use spaces in linux folder names.

When I check for the crash report in the directory given, there are no .dmp files. The directory is empty. What is going on? This only started happening with the latest update. i'm unable to reproduce locally on my 6.2 final unraid box. can you please provide the output obtained by following this post. http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150 root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexMediaServer" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -v "/mnt/cache/appdata/plexmediaserver/":"/config":rw -v "/mnt/user/Media/Movies/":"/Movies":rw -v "/mnt/user/Media/Music/":"/Music":rw -v "/mnt/user/Media/TV/":"/TV":rw limetech/plex 7935be23a4ccf35f3eb8839ea52d3f61fb8f689fb716c8055963c901fbb16039 "limetech/plex" this is the support thread for linuxserver/plex

moved to our lsiocommunity repository.

When I check for the crash report in the directory given, there are no .dmp files. The directory is empty. What is going on? This only started happening with the latest update. i'm unable to reproduce locally on my 6.2 final unraid box. can you please provide the output obtained by following this post. http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150

i'm unable to reproduce locally on my 6.2 final unraid box. can you please provide the output obtained by following this post. http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150

belt and braces... lol.

I have tried deleting and recreating as per suggestion here -> http://lime-technology.com/forum/index.php?topic=40937.msg481138#msg481138 and now get the foloowing trying to reinstall; first glance---- does /mnt/user/data/docker/roon/library/ still exist ?

needs moar video....

For reasons unknown, the push to the hub over the weekend of this image was broken somehow, it passed testing on the local server prior to the push less than a minute later. but pulling it from the hub just now i saw the same error, a new push to the hub and it doesn't seem to do it anymore. can you try a complete new pull from the hub, after deleting any containers and images for openvpn-as you may have locally.

and so it begins, welcome to my world system => updates click install..... on the update, then the reload button when completed. job done.

When will this be happening? Just so I know when to look for the update Soon ™

So if you do not update then you're good There is no issue with the current docker and the version of sabnzbd (1.0.3) that it is using. but 1.10 is currently at RC4 and the issue between python, alpine and sabnzbd occurs with that branch.

This image will be rebased back to ubuntu, there is an issue between python, alpine and one of the configuration screens in the upcoming 1.1x branch of sabnzbd. Discussion with sabnzbd developers led to the decision to rebase this to ubuntu xenial.

that doesn't explain exactly the same issue on an ubuntu based image of kodi-headless Jarvis. http://lime-technology.com/forum/index.php?topic=42439.msg493789#msg493789 ^^^ that image is ubuntu based, the only thing keeping it up is the --restart=always option in the run command. take that out and the whole container crashes with the same problem.

/usr/local/bin/par2

thanks, good information. and thanks for not posting the version here.

I too would like to know this - possibly create a version of this docker app that doesn't update automatically and lets you install a package manually ? The only way you can install this beta now is to install the plugin plex are providing themselves and use that instead of plex in your docker. I would back up your app data tho, just in case the beta screws something up! Be warned though, anyone posting specifics about how to do this on this thread, I'll ask a moderator to remove those posts. That would be infringing upon plex's legal property.

I too would like to know this - possibly create a version of this docker app that doesn't update automatically and lets you install a package manually ? You can disable updates by taking out the version variable, but I cannot advise you to look at the container structure on our git repository in regards as to installing a .deb file.

Reading the blog post here, https://www.plex.tv/blog/air-human-plex-dvr-divine/ the dvr beta is currently only available as a download from the forum and for plexpass users only. Since we cannot determine who are plexpass users and who are not, we cannot supply a version of plex containing this beta without breaking plex's rules regarding non-plexpass users access to content meant only for plexpass users. We have already had one warning from plex on this very issue that forced us to change our container some months ago. Also contained in the blog post is the line "rest assured this will be available as an automatic update for Plex Pass users before long." You will have to wait until then, if someone else offers a container with it, that is their concern and their fight with plex.

This docker has been rebased to alpine with s6 overlay, please make sure you backup your appdata first before you update to this latest image. For more information, please read : http://lime-technology.com/forum/index.php?topic=50793.0

Docker compose could be a boon for some of the less tech-savvy users, still a little scared of docker, especially the thought of having to link containers together, ie SQL and kodi etc... Compose absolutely excels in that area.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7fe23da3da5b celedhrim/kodi-server "/opt/kodi-server/lib" 2 minutes ago Up 18 seconds tender_meitner sparklyballs@Docker-Slave1:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7fe23da3da5b celedhrim/kodi-server "/opt/kodi-server/lib" 2 minutes ago Restarting (139) Less than a second ago tender_meitner sparklyballs@Docker-Slave1:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7fe23da3da5b celedhrim/kodi-server "/opt/kodi-server/lib" 2 minutes ago Up 1 seconds tender_meitner the only thing keeping that particular docker alive is the --restart=always flag , other than that it is having exactly the same issue as the linuxserver docker.

it should also be noted it's something that is intermittent. my current container over the last couple of days has bombed out about 3 times, and i've had mixed success at different times with with starting a new container on my test server from several different authors of kodi headless dockers, the only constant being that they're jarvis variants.