nathanj Posted October 7, 2017 Share Posted October 7, 2017 (edited) Im confused as to what is filing up my 100gb docker file. Here are some outputs of commands, does anyone have any ideas that dont involve me deleting my docker file and starting from scratch? root@UNRAID:~# docker ps -s CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZE ff50f41b2b2d linuxserver/plexpy:latest "/init" 2 hours ago Up 2 hours 0.0.0.0:8181->8181/tcp plexpy 89.75 MB (virtual 324.9 MB) 3504eaccf15c linuxserver/plex:latest "/init" 3 hours ago Up 3 hours plex 228.4 MB (virtual 663.3 MB) 07dec786d85b titpetric/netdata:latest "/run.sh" 9 hours ago Up 9 hours Netdata 21.39 MB (virtual 285.6 MB) 1541473b596d centurylink/watchtower "/watchtower" 8 months ago Up 4 weeks watchtower 0 B (virtual 5.871 MB) root@UNRAID:~# df -h | grep docker /dev/loop0 100G 81G 17G 83% /var/lib/docker shm 64M 0 64M 0% /var/lib/docker/containers/1541473b596d056e0303c82d4f2cd713784d413e80640806c0c0108bf9b4ea19/shm shm 64M 0 64M 0% /var/lib/docker/containers/07dec786d85bec48c8ad384f6c2c56591ed846930254ef1c2dfe63d1caa96c4b/shm shm 64M 8.0K 64M 1% /var/lib/docker/containers/3504eaccf15c464b829c30d004ffdf4d1eb20f0c45444849348456b00fb24f1e/shm shm 64M 0 64M 0% /var/lib/docker/containers/ff50f41b2b2d4434381f2f835d83bb0c382e54dc397a75117012bf69ca22c52b/shm shm 64M 0 64M 0% /var/lib/docker/containers/c74048c018822175016a02cd1a42757ab7368efe8a5a7951063bac1297398a6b/shm Edited October 7, 2017 by nathanj Quote Link to comment
Squid Posted October 7, 2017 Share Posted October 7, 2017 (edited) 12 hours ago, nathanj said: docker ps -s You want to use docker ps -s -a By and large, there's only 2 reasons for the image filling up (btw, 100 Gig is way overkill) - Excessive logging from an application du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 | grep .log or - Inadvertently saving downloads, plex's config etc into the image (which it doesn't *appear* that it is) You can delete any dangling images docker rmi $(docker images --quiet --filter "dangling=true") 12 hours ago, nathanj said: that dont involve me deleting my docker file and starting from scratch If you can't find the reason, this is what you have to do. And, its an extremely painless operation. - Stop the service, delete the image, restart the service, Apps tab, Previous apps, Check off your apps, hit reinstall. 2 minutes later you're back up and running with no changes required. Edited October 7, 2017 by Squid 2 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.