I've gotten quite a few suggestions on this Reddit Thread I started concerning my issue.  I've tried them all to no avail.  Some of the things that were suggested that I have already completed:

 

1. Scrubbing the Docker system
2. Stopping the Docker system and turning on the Rotation log and setting max size to 100MB
3. Making the Docker IMG bigger (it just fills up again)
4. Install Portainer Docker and going through there and cleaning out the unused files

 

I'm at my wits end.  I'm running the "Devils update" of 6.6.6 

 

Obviously I believe the culprit is "PiHole Docker":

 

Name                              Container     Writable          Log
---------------------------------------------------------------------
pihole                              4.58 GB      4.28 GB      7.80 GB
binhex-krusader                     2.23 GB      19.1 MB       139 kB
VNCWebBrowser                       1.59 GB      62.3 kB      2.83 kB
DigiKam                             1.41 GB      33.7 MB      76.7 kB
Google-MusicManager                  618 MB          0 B      24.2 MB
jellyfin                             483 MB          0 B      24.2 MB
PlexMediaServer                      395 MB       330 kB       161 kB
hdhomerundvr                         337 MB        15 kB      34.3 kB
Netdata                              267 MB          0 B      24.2 MB
HandBrake                            265 MB      34.9 kB      3.15 MB
MKVToolNix                           255 MB      23.8 kB      86.0 kB
tautulli                             235 MB      45.8 MB      55.0 kB
openvpn-as                           228 MB      1.84 MB      14.4 kB
QDirStat                             201 MB      23.8 kB      50.3 kB
beets                                182 MB          0 B      24.2 MB
FileZilla                            161 MB      23.9 kB       156 kB
heimdall                             153 MB      49.2 MB      13.0 kB
duckdns                             20.7 MB      6.62 kB       251 kB

But I can find NO information on how to stop that insane logging....

Edited January 2, 20197 yr by CoZ

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564310

https://forums.unraid.net/topic/57181-real-docker-faq/?tab=comments#comment-564312

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564326

 

Would also be useful for you to go to Docker Tab, and post a screen shot of what appears when you hit Container Size

Not sure how the forum software handles what you did. Instead of replying to Squid's post, you edited your first post so it included the information he asked for. I don't know if he will know that you responded to his request the way you did it, so he might not even look back at this thread.

 

I recommend always posting any response you have in a new post in the same thread. And even if the thread appears to be "bumped" when you do that, it might not be obvious that someone should go back to the first post (especially if it is further up the page) to find your new information.

1 hour ago, CoZ said:

pihole 4.58 GB 4.28 GB 7.80 GB

Don't run piHole, but it certainly looks like this is your big offender.  Logging is out of control, its definitely saving *something* in the image.

1 hour ago, CoZ said:

• Stopping the Docker system and turning on the Rotation log and setting max size to 100MB

Probably log rotation only happens once per day.  Not quite sure since I've never had any runaway logging.

 

10 minutes ago, trurl said:

I don't know if he will know that you responded to his request the way you did it, so he might not even look back at this thread.

I wouldn't have, as I never would have realized there was more info.

4 minutes ago, Squid said:

runaway logging.

Actually, now that I'm thinking about it, I'm not 100% convinced that the log rotation setting in docker settings does what it is intended to do.  There is a possibility that it only handles the rotation on the docker log, and not on the container log.  Add to the extra parameters of piHole

--log-opt max-size=50m --log-opt max-file=1

 

Quick research, and the docker log options in the GUI do actually do what they are supposed to do, but not without a big gotcha that isn't obvious.

 

All existing containers must be removed and reinstalled for the change to take effect.  Going to issue a PR for a wording change in the UI

Just now, Squid said:

Quick research, and the docker log options in the GUI do actually do what they are supposed to do, but not without a big gotcha that isn't obvious.

 

All existing containers must be removed and reinstalled for the change to take effect.  Going to issue a PR for a wording change in the UI

Someone else mentioned that in the Reddit thread I started, that he had to delete his entire Docker system for the docker log rotation setting to go into effect.  I was hoping it was just a fluke on his end and it did, indeed take effect without having to do that.

5 minutes ago, Squid said:

Actually, now that I'm thinking about it, I'm not 100% convinced that the log rotation setting in docker settings does what it is intended to do.  There is a possibility that it only handles the rotation on the docker log, and not on the container log.  Add to the extra parameters of piHole

--log-opt max-size=50m --log-opt max-file=1

 

I apologize ahead of time, but I know just enough about unRaid to be dangerous to myself and the OS.  lol

 

Where would I place that?  Edit the container "Add another Path/Port/Variable" I'm assuming?  But which one do I choose?

Advanced view when editing the container.  There's a field called extra parameters

Thanks for that bit of hand holding.  I did that and this dialogue box popped up after hitting apply:

- Docker image disk utilization returned to normal level
Docker utilization of image file /mnt/user/system/docker/docker.img

I was also able to log in to the GUI of PiHole (last time I tried to map the log DIR to some other spot on the array and was unable to get into the GUI.)  Hopefully this solves it.... 

 

Thanks!

14 minutes ago, CoZ said:

he had to delete his entire Docker system for the docker log rotation setting to go into effect

Not as traumatic as you might think. You can delete any and all dockers, and in fact, we often recommend deleting the docker image itself (where all docker code lives) for some problems.

 

You can always reinstall any and all of your dockers with all the same settings as before using the Previous Apps feature on the Apps (Community Applications) page. They will even have all of their data (assuming you haven't deleted their appdata). Anytime you create or edit a docker, its template is saved to flash where it can be used again, and Previous Apps makes it easy.

 

I've raised an issue on GitHub to let @limetech decide what approach to take on this

1. Status Quo, but with a warning
2. Only allow changes to the log options when the image doesn't exist * <-- Best option in my opinion, especially if the default setting instead of being no rotation changes to be say 50Meg.   After all, when was the last time ANYONE looked at a log file larger than 50Meg?
3. Append in the docker run commands the appropriate log option extra parameters.  This has the same problem as the status quo.

In the meantime, I've changed the wording on the entry in the Docker FAQ to reflect this.

Edited January 2, 20197 yr by Squid