What the hell is taking up my space?

[Dimtar]

Hi All.

 

I have rebuilt docker.img twice this month, both times back to the original 20GB image. After a week or so the docker image would be full and I would re-create. This time I created a 40GB image but its going to be full soon as well. One of my dockers is filling it with stuff. I have a standard lot of dockers and the 40GB version was created only a few days ago and I've only updated 2 dockers in that time so its not filling up with images etc. but something else.

 

25th January:

http://puu.sh/mK1v4/202eeb4123.png

26th January:

http://puu.sh/mK1vG/f73e99a12b.png

http://puu.sh/mK1wj/3c5110c9fb.png

My Docker List:

http://puu.sh/mK1q3/1c899158e3.png

 

Is there someway I can see which docker is doing this? My current thought is Jackett

 

 

 

[Dimtar]

Ok, I was able to find some information myself.

 

I ran:

df -lh

 

Found the docker.img is mounted here:

/var/lib/docker

 

Once inside I found this folder was 22GB:

/var/lib/docker/containers/45bb3bb55cc9d7f35e303868c513c4817db3e0404e39364961610ffcf7277f10

This file specifically:

22G    ./45bb3bb55cc9d7f35e303868c513c4817db3e0404e39364961610ffcf7277f10-json.log

 

According to the docker web interface this relates to the LimeTech BT Sync Docker:

http://puu.sh/mK25v/a022689653.png

 

It looks like there is no limit to how much it will log or is that just me? I am mostly guessing here but maybe the Docker needs to be set not to log so aggressively or something? The docker have been up for 45 hours and thats the size of the log file. Hopefully someone smarter then me can add to this?

[mdumont1]

Check out this thread: http://lime-technology.com/forum/index.php?topic=45249.0

 

It seems multiple dockers have the logging problem. Another user had a similar issue with the BTSync docker and was able to slow down the log growth with an extra BTSync option.

[Dimtar]

Check out this thread: http://lime-technology.com/forum/index.php?topic=45249.0

 

It seems multiple dockers have the logging problem. Another user had a similar issue with the BTSync docker and was able to slow down the log growth with an extra BTSync option.

 

Very helpful thank you. I've turned off "debug" logging in BT Sync as a start.