hey all-

 

about every 24hrs, my dockers become unresponsive, and none of the gui's will load. 

trying to reload the docker brings an "execution error" pop up.

if I restart unraid, everything works again, but only for a short period of time.

 

I do see this error repeating in my logs

 

Oct 17 06:49:42 NextGen-Tower shfs/user: err: shfs_write: write: (28) No space left on device

 

I have plenty of room on all my disks as well.  not sure why i am getting this

diag attached

 

thanks

nextgen-tower-diagnostics-20161017-0720.zip

I think I may have found the issue.

 

my docker.img file was reporting at 42.6gb, when my total size was set to 40gb.

 

just set it to 80gb, and the errors have cleared.  all dockers operating normally

 

curious though, do these docker.img file sizes sound accurate?  Everything I have read on the forums call out much smaller size files.

 

Thanks

 

I think I may have found the issue.

 

my docker.img file was reporting at 42.6gb, when my total size was set to 40gb.

 

just set it to 80gb, and the errors have cleared.  all dockers operating normally

 

curious though, do these docker.img file sizes sound accurate?  Everything I have read on the forums call out much smaller size files.

 

Thanks

You are just going to fill it up again. Very unlikely you will ever need more than 15-20 GB if you are doing things right.

 

You must have some docker(s) misconfigured and they are writing data inside docker.img instead of to mapped storage on the host. See the Docker FAQ sticky.

I have been digging into this, and even had another guy look it over.  We are seeing all proper settings on our side, and cannot see how this is happening. 

 

I have gone through the FAQ, installed the "fix common problems" plugin, and its reporting that my var/log file is full (100%), and to seek assistance here

 

thanks again

The reason why /var/log is full is because your bombing the syslog with all of the no space left messages.  Easiest solution is to reboot.

 

As far as the image filling up, you DO have a container misconfigured.  Probably either crash plan or a download client.    Post the screen shot of the docker page and we'll go from there

 

Sent from my SM-T560NU using Tapatalk

 

 

This was my previous set-up.  I have since located over 14 orphaned docker.img files, which I have now removed.

I also followed the *Official Guide to Restoring your docker* post, performed it and loaded back up my dockers via templates-user files.

 

pretty slick i must say...

 

All looks to be working now, and I am testing and checking .img file size to see if its increasing. 

 

Log files are crystal clear as well.

 

Thanks

For instance, the MakeMKV-RDP container defaults to writing its output files to /nobody (inside the container) instead of /output. (The mounted output path.)

The volume mappings look OK, but I notice you often use lower and upper case letters differently in the mappings. Perhaps you have the applications using the wrong path when you set the application up.

 

Post a screenshot of the Paths Settings in NZBGet, for example.

here you go

 

thanks

NZBGet looks OK. Plex is the only other one you have that I use and if it is working probably OK. Maybe CouchPotato or Sonarr, where you have a lot of paths.

 

Might have to try them one at a time to find which one is making docker.img grow.

Question for you ?

 

why do you have both sonarr and couch potato on ? ?

Question for you ?

 

why do you have both sonarr and couch potato on ? ?

sonarr = tv, couchpotato=movies