Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral


  • Rank
    Advanced Member


  • Gender
  • Location
    Charleston, SC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks! It's been long enough since I first enabled Dockers I wasn't remembering. The image file was set to 10GB and I upped it to 30GB so now down to 23% usage. There is also something called Log rotation, which I imagine is saving 1, 2, or 3 files in history for troubleshooting purposes. Mine was set to 1 file 50 MB in size. I upped it to 3 files 100 MB. Not sure in relative terms how big this should be with on 7 dockers installed and 3 that run under daily normal situations. I assume the more dockers you have running the larger that file should be? Doesn't seem particularly important at this point but no download clients installed here. The only real active Docker is Plex. Thanks again, that should hopefully solve the issue.
  2. How do you expand the size of the docker image? Is this housed in RAM, or in Cache? None of my dockers "auto-update" and this warning comes around at seemingly random times. What "update" would be occurring to cause this? I'll provide this when I get home in the hour.
  3. I hope this is the correct area for this question. Every once in a while I get an email notification that says "unRAID Status: Warning - Docker image disk utilization of 88%. Then later it I get a "returned to normal" email. My docker and app data are stored on a cache disk (SSD) that is only used for appdata. It's a 250 GB disk and 27% full. I have attached two images that show my docker settings and memory usage (which shows docker usage at 76%). Is it possible when my Plex app is transcoding and/or doing DVR recording, and using up too much memory? If so can this be offloaded to the SSD Cache? I have plenty of cache drive space, is there a setting wrong that is driving it to use memory instead of the cache disk? how do I get more Docker Image space? Thanks for any help.
  4. Got it. Thanks, worked fine and DVR functional again!
  5. So does this mean the variable should be: (I think it used to just say "docker") docker:e5cc93306-ls58 or docker: or something else? Sorry if I'm asking what should be obvious, but admittedly not a "docker" expert here and continuing to learn more all the time.
  6. OK I'll have to do this tomorrow if I have to remove the image too. A few settings I need to re-create and its late. I'll drop a note tomorrow evening. Thanks.
  7. I tried this, restarted the docker, no luck. did a force update. no luck, still shows Version See image EDIT: I also tried it with only e5cc93306-ls58. It looked like it updated that time, but still shows the same version
  8. I did try this. I changed "docker" to an actual version number in the variable for "VERSION" I'm currently on Version I tried using "" and "" in place of the word "docker" I hit apply, then did a "force update" but the version number didn't change inside plex. Am I missing some syntax here?
  9. Isn't there a way to tell the docker to roll back to the previous version / release of Plex. This latest update apparently broke the DVR service (again). It worked yesterday, I ran the update right after a recording. Today 2 recordings failed. When I go into the guide and click on a show that is not recording the info page comes up. If I click on a show that is supposed to be recording I get "An unexpected error has occurred" Any help rolling back a version would be great. I know there is a place to change the version in the docker setup, just not sure what to put in there. Thanks in advance.
  10. I have migrated from one plex docker to the other and now ready to delete the old docker. The new install is mapped to the location of the old appdata rather than it's own default location. Question is when I remove the old docker, is it going to try to remove it's default appdata, which is now used by the new docker? Is there any way to prevent it? Should I also be checking "also remove it's image"? I don't want un-necessary software hanging around, but dont want to delete the data still being used. It would be a train-wreck to re-create it. thanks.
  11. I recently went through some difficulty with my Plex docker and permission rights for files. It took a week of back and forth on two sections of the forums before I had the answer. In the end it was a simple fix but it seems like very few know its there or can be an issue. I would assume this could potentially affect or be useful in other dockers as well. --Issue-- I use the Plex DVR with the Linuxserver.IO Plex docker. The video files being created by the Plex DVR were being created with limited access rights for anyone but the user "nobody" the owner of the file. I could not move, rename, delete any files without first running the "new permissions" utility on unRaid. --Cause-- linux has a UMASK default of 022, but this is not compatible with the unraid system. This limits user access to the user/group that created the folder and/or file, in this case "nobody." UMASK of 0000 will mean that all files / folders will be r/w access for all users with the appropriate permissions in unRAID. --Fix-- The Plexserver.IO docker has a variable for UMASK that isn't in the default list when first installed. You can add in the docker settings UMASK_SET, and you then assign 0000 there. This resolved the access rights issues to the DVR created files. If this is helpful to others, certainly can be added to any FAQ
  12. so marked (and I was looking for a "solved" button). The answer came inside the LinuxServer.IO - PlexServer forum. I did reply that it solved the issue, and the fix was simple. In the end they do have a variable setting for UMASK available, its just not in the default list, so you have to add it manually. If there is somewhere I should post a summary write up I'd be happy to contribute.
  13. This is now solved. LinusServer.IO provided info on setting the variable for UMSASK