Hi, 

 

I've been trying to track down my docker image usage. 
I haven't found much in the way of rhyme/reason on how it's getting larger.  Seems to be about 3% at a time though.

 

• System Version: 6.9.1
• System Memory Usage:
  
• Docker Information:
  
• Docker Settings:
  
• All docker containers have a "/" prefix before their path
• Log rotation is enabled
• Container size output:
  
• Output of command

  du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60

   
•  Output of command

  find /var/lib/docker/containers/ -type f -exec du -Sh {} + | sort -rh | head -n 15

  

•  Output of command

  docker system df -v

  
• I've been using this to find the largest folders on some containers

  du -Sh | sort -rh | head -5

   

• I've been using this to find the largest files on some containers 

  find -type f -exec du -Sh {} + | sort -rh | head -n 5

   

 

You probably have a bad mapping somewhere and one of the containers is storing files internally instead of externally. You could try looking at the docker run command for each container.

9 hours ago, John_M said:

You probably have a bad mapping somewhere and one of the containers is storing files internally instead of externally. You could try looking at the docker run command for each container.

 

I've gone through all my mappings and they seem correct.  They all are defined based on the template, docker run shows the prefixed "/"

 

Output of Command:

du -h -d 1 /var/lib/docker/

 

I've also been running the following command to see file size changes

docker ps | awk '{print $1}' | grep -v CONTAINER | xargs -n 1 -I {} sh -c "echo -e \\\n#================\\\nDocker container:{}; docker exec {} du -hx -d1 / "

 

59 minutes ago, ShadeZeRO said:

 

I've gone through all my mappings and they seem correct. 

Have you matched what's in the mappings to the internal configuration of each app? If the app is set to write to /Downloads and the mapping is /downloads you will end up writing to /Downloads inside the docker image.

22 minutes ago, jonathanm said:

Have you matched what's in the mappings to the internal configuration of each app? If the app is set to write to /Downloads and the mapping is /downloads you will end up writing to /Downloads inside the docker image.

NZBGet is the only application that downloads anything.  It's been working fine over over a year.
Anytime I select a path, I choose it through the drop down so anything case-sensitive is preserved. 

Reslio is another App that pulls data in occasionally:

 

Plex (mostly default settings)

Splunk:

 

Edited March 23, 20215 yr by ShadeZeRO

You could try narrowing down the problem by running only some of your containers for a while. With the various tools and charts you've shown you should be able to eliminate several of them quite quickly.

22 hours ago, John_M said:

You could try narrowing down the problem by running only some of your containers for a while. With the various tools and charts you've shown you should be able to eliminate several of them quite quickly.

I did some considerable digging.  It ended up being the "splunk" container.  
This was determined by doing a "force upgrade" and seeing the behavior after a restart.  The docker image usage spiked every time that action was performed.

 

After that, I shutdown docker, deleted the vdisk, and recreated (as XFS since this was a good opportunity to move off BTRFS) and re-imported my templates (except Splunk).

The usage has been exemplary now.  

 

Thank you to everyone who offered support.