Kode Posted July 25, 2015 Share Posted July 25, 2015 Go to Settings / Docker Change Enable Docker to No and hit Apply Increase the size and Enable Docker and Apply Link to comment
MyKroFt Posted July 30, 2015 Share Posted July 30, 2015 I am going to try and build my own docker - in part to see if I can do it. Can I use some of your formatting and scripts/layouts that you use. I like to configuration you use to layout everything. Thanks Myk Link to comment
lonix Posted July 30, 2015 Share Posted July 30, 2015 I am going to try and build my own docker - in part to see if I can do it. Can I use some of your formatting and scripts/layouts that you use. I like to configuration you use to layout everything. Thanks Myk sure Link to comment
bmdegraaf Posted July 31, 2015 Share Posted July 31, 2015 When UNRAID is rebooted Plex will not start. Only once I manually reset Plex it start up properly. The log shows: setuser: cannot execute /usr/sbin/start_pms: [Errno 2] No such file or directory The config directory is located on a separate share outside the array using unassigned devices. Maybe it has a correlation. I am using plexpass... Link to comment
saarg Posted July 31, 2015 Share Posted July 31, 2015 When UNRAID is rebooted Plex will not start. Only once I manually reset Plex it start up properly. The log shows: setuser: cannot execute /usr/sbin/start_pms: [Errno 2] No such file or directory The config directory is located on a separate share outside the array using unassigned devices. Maybe it has a correlation. I am using plexpass... Sounds like the disk gets mounted later than the docker container get started. You either have to move the appdata to your cache drive or start the docker manually. Link to comment
bmdegraaf Posted July 31, 2015 Share Posted July 31, 2015 Did not have this problem when using needo's plex... And my other dockers startup normal Link to comment
sparklyballs Posted July 31, 2015 Share Posted July 31, 2015 When UNRAID is rebooted Plex will not start. Only once I manually reset Plex it start up properly. The log shows: setuser: cannot execute /usr/sbin/start_pms: [Errno 2] No such file or directory The config directory is located on a separate share outside the array using unassigned devices. Maybe it has a correlation. I am using plexpass... can you post a screenshot of your mappings for the container please. click/right click the docker icon, select edit and screenshot the section for volumes... and the location of your docker.img. Link to comment
bmdegraaf Posted July 31, 2015 Share Posted July 31, 2015 The docker image location is /mnt/disks/appdata/docker.img Config location is /mnt/disks/appdata/plexmediaserver Link to comment
sparklyballs Posted July 31, 2015 Share Posted July 31, 2015 The docker image location is /mnt/disks/appdata/docker.img Config location is /mnt/disks/appdata/plexmediaserver thanks for those.... another question... have you recently changed from needo plex to linuxserver plex ? Link to comment
bmdegraaf Posted July 31, 2015 Share Posted July 31, 2015 Yup.. A week ago or so. Kept the config directory Link to comment
sparklyballs Posted July 31, 2015 Share Posted July 31, 2015 Yup.. A week ago or so. Kept the config directory thank you for the information. Link to comment
Benni-chan Posted July 31, 2015 Share Posted July 31, 2015 I think I had a similar issue a week ago or so... to fix it, I redownloaded the PMS Docker. Works fine at the moment (but I use my appdata on the cache drive. afaik the unassigned disk addon mounts drives before docker starts, so this should work fine, too) Update: I now remember, what caused the problem for me. I restarted the container, while it was downloading a new PMS release. On the next start, the download would start again, but with an other filename (I think it added "-1" at the end of the file), but it tried to install the previous (failed) download. so no PMS would get installed and the docker couldn't run it. not quite the same issue but maybe related... Link to comment
mr-hexen Posted July 31, 2015 Share Posted July 31, 2015 When I first converted to LinuxServer PMS from needo's it ran a permissions update script on the config folder that ran for about 5 minutes.... maybe related? Link to comment
bmdegraaf Posted July 31, 2015 Share Posted July 31, 2015 Re installed and the issue persist. Only when i manual restart the docker plex will start. This is only needed after unraid is rebooted. Once plex is up and running (after a manual plex restart)i can start stop without issues. Link to comment
lonix Posted August 3, 2015 Share Posted August 3, 2015 Re installed and the issue persist. Only when i manual restart the docker plex will start. This is only needed after unraid is rebooted. Once plex is up and running (after a manual plex restart)i can start stop without issues. Would you be so kind that you could provide me with a complete set of logs from it failing to start, i shall then commence investiating. Link to comment
bmdegraaf Posted August 9, 2015 Share Posted August 9, 2015 Attached the log from the plex docker.... First log is the automatic start. Second log is when I stop the docker and start it again. No idea why it is logging Invalid response packet from host 192.168.1.100. This is my Windows 10 VM and has no interaction with Plex whatsoever. Log.txt Log_after_stop_start.txt Link to comment
sparklyballs Posted August 9, 2015 Share Posted August 9, 2015 Attached the log from the plex docker.... First log is the automatic start. Second log is when I stop the docker and start it again. No idea why it is logging Invalid response packet from host 192.168.1.100. This is my Windows 10 VM and has no interaction with Plex whatsoever. it's an avahi bug in relation to OSX machines on your network, and now it seems win10 too. https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400 Link to comment
CHBMB Posted August 9, 2015 Share Posted August 9, 2015 Attached the log from the plex docker.... First log is the automatic start. Second log is when I stop the docker and start it again. No idea why it is logging Invalid response packet from host 192.168.1.100. This is my Windows 10 VM and has no interaction with Plex whatsoever. it's an avahi bug in relation to OSX machines on your network, and now it seems win10 too. https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400 Yep, can confirm it's on Windows 10, surprised to see Sparkly providing support on a Plex thread.. Link to comment
lonix Posted August 9, 2015 Share Posted August 9, 2015 Sparklyis working on This container with me Link to comment
CHBMB Posted August 9, 2015 Share Posted August 9, 2015 Sparklyis working on This container with me How did you persuade him, I think it's fair to say he's not Plex's biggest fan Link to comment
lonix Posted August 9, 2015 Share Posted August 9, 2015 He is a part of the linuxserver.io team, which I am the head off Link to comment
CHBMB Posted August 10, 2015 Share Posted August 10, 2015 Oh, I see, you pulled rank, that explains it... Hehe Link to comment
linuxserver.io Posted August 12, 2015 Share Posted August 12, 2015 Thread now replaced: http://lime-technology.com/forum/index.php?topic=42148.0 MODS: Please close this thread, Link to comment
Recommended Posts