yendi Posted November 3, 2019 Share Posted November 3, 2019 (edited) EDIT 2: I solved the issue, easy... I clicked on the "Container size" on the bottom of the Docker page. I saw that Radarr was 50GB... I updated it to last version and my issue was solved: 11% docker img utilization... Son't know why Radarr grow that much, will monitor the situation. Hello Everyone, I had Plex DB corruption yesterday after a reboot. I tried to restore all my appdata and plex autobackup but all appears to be corrupted aswell (my server did not restart for 2 months). I ended up install a different plex docker (binhex instead of linux server) to be able to test solution without touching the other docker. I finally made a working Plex docker by repairing the SQLite DB (blobs db was faulty) and had to refresh all metadata (40tb library...) Today I see that my docker image (100GB) if filling up anormaly. I have everything configured correctly so I don't understand what can be filling it. I changed the /transcode directory from plex as it was the default one but as I see the CAdvisor, the problem is not plex related, its widespread. Could you please help me find was is wrong? Here are some screenshots: Docker config: Docker Usage: CAdvisor: Dockers page: NZBGet config: Transmission: Thanks ! EDIT: I had a 17Gb Sonarr log (Debug logging enabled...), I was able to delete it with this command but it does not solve the issue, I still have 50Gb used... echo "" > $(docker inspect --format='{{.LogPath}}' fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6) root@Mercure:~# du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 17G /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6-json.log 17G /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6 114M /var/lib/docker/containers/8d60b1c98afbd3f2c45d1d4525bc5901716d62399e4e163e32a8680ce4de2bdb/8d60b1c98afbd3f2c45d1d4525bc5901716d62399e4e163e32a8680ce4de2bdb-json.log 114M /var/lib/docker/containers/8d60b1c98afbd3f2c45d1d4525bc5901716d62399e4e163e32a8680ce4de2bdb 58M /var/lib/docker/containers/b25cbbb806a80473049080db470be6f6b4755ed674521a5e26cf697f2befde5e/b25cbbb806a80473049080db470be6f6b4755ed674521a5e26cf697f2befde5e-json.log 58M /var/lib/docker/containers/b25cbbb806a80473049080db470be6f6b4755ed674521a5e26cf697f2befde5e 51M /var/lib/docker/containers/3aae22fe6c7ff0a935390e8523b2bf23a5a06afe5c620c27b7aabacb84771333/3aae22fe6c7ff0a935390e8523b2bf23a5a06afe5c620c27b7aabacb84771333-json.log 51M /var/lib/docker/containers/3aae22fe6c7ff0a935390e8523b2bf23a5a06afe5c620c27b7aabacb84771333 32M /var/lib/docker/containers/d053aefdd74c8caceccd18d2f4f6568cb9ea3a3a3c974571adb90efc65c84d40/d053aefdd74c8caceccd18d2f4f6568cb9ea3a3a3c974571adb90efc65c84d40-json.log 32M /var/lib/docker/containers/d053aefdd74c8caceccd18d2f4f6568cb9ea3a3a3c974571adb90efc65c84d40 30M /var/lib/docker/containers/35230c29fd65bde430becab1b53035b1b670aaa40381892bde04b79c68da5c8a/35230c29fd65bde430becab1b53035b1b670aaa40381892bde04b79c68da5c8a-json.log 30M /var/lib/docker/containers/35230c29fd65bde430becab1b53035b1b670aaa40381892bde04b79c68da5c8a 29M /var/lib/docker/containers/57abb32f88a8b5042e936181993f71308b715090d5dfe6702633b196773107f4/57abb32f88a8b5042e936181993f71308b715090d5dfe6702633b196773107f4-json.log 29M /var/lib/docker/containers/57abb32f88a8b5042e936181993f71308b715090d5dfe6702633b196773107f4 17M /var/lib/docker/containers/072b0050b358893efadfccc65ce0d865abd297283697a99d1ed1d52096c31005/072b0050b358893efadfccc65ce0d865abd297283697a99d1ed1d52096c31005-json.log 17M /var/lib/docker/containers/072b0050b358893efadfccc65ce0d865abd297283697a99d1ed1d52096c31005 11M /var/lib/docker/containers/bba2c290af99408729b3abc0c7734e8be90128bbaea4f08021f406f1738ab284/bba2c290af99408729b3abc0c7734e8be90128bbaea4f08021f406f1738ab284-json.log 11M /var/lib/docker/containers/bba2c290af99408729b3abc0c7734e8be90128bbaea4f08021f406f1738ab284 4.9M /var/lib/docker/containers/9c6fcf52bfbe97a6d87634f9e76ee5accedc18a44d2c1911f7c622d025eaa446/9c6fcf52bfbe97a6d87634f9e76ee5accedc18a44d2c1911f7c622d025eaa446-json.log 4.9M /var/lib/docker/containers/9c6fcf52bfbe97a6d87634f9e76ee5accedc18a44d2c1911f7c622d025eaa446 4.5M /var/lib/docker/containers/4218bcedf79528f70c0a0cee86649d81330145a4cdfd2f3abb0791bb5b0f7057/4218bcedf79528f70c0a0cee86649d81330145a4cdfd2f3abb0791bb5b0f7057-json.log 4.5M /var/lib/docker/containers/4218bcedf79528f70c0a0cee86649d81330145a4cdfd2f3abb0791bb5b0f7057 4.4M /var/lib/docker/containers/9d325450554d9997aa09b124149548f4639292db04461e46243b56a7a4b611ec 4.3M /var/lib/docker/containers/9d325450554d9997aa09b124149548f4639292db04461e46243b56a7a4b611ec/9d325450554d9997aa09b124149548f4639292db04461e46243b56a7a4b611ec-json.log 316K /var/lib/docker/containers/a8f0ea007e705e59d8303cbcbbfa42f51c64cbd4ee36e8855792ce8a9f5ed176 292K /var/lib/docker/containers/a8f0ea007e705e59d8303cbcbbfa42f51c64cbd4ee36e8855792ce8a9f5ed176/a8f0ea007e705e59d8303cbcbbfa42f51c64cbd4ee36e8855792ce8a9f5ed176-json.log 208K /var/lib/docker/containers/c8c2035c5328d0b6efbcfe41e55b8aa272b3f5cfdf029898585eeb12cd01594f 180K /var/lib/docker/containers/c8c2035c5328d0b6efbcfe41e55b8aa272b3f5cfdf029898585eeb12cd01594f/c8c2035c5328d0b6efbcfe41e55b8aa272b3f5cfdf029898585eeb12cd01594f-json.log 96K /var/lib/docker/containers/434c82b18a17f1431d28807cd55b046bda41c223bb84a9797fc08b9476916123 72K /var/lib/docker/containers/434c82b18a17f1431d28807cd55b046bda41c223bb84a9797fc08b9476916123/434c82b18a17f1431d28807cd55b046bda41c223bb84a9797fc08b9476916123-json.log 52K /var/lib/docker/containers/665670b96e0320862f1c70e1ce6e83349df691b3d84791d9ca6cd25c8501a569 36K /var/lib/docker/containers/9b10cb71ecb9a7af213655649568cf5d3733c001ab89ee1714fef9db0ddba0f2 32K /var/lib/docker/containers/3b6eca5c6348d76dfb3776358ac7dbeb7b2a2c60977170c58e87d8d41ea69f20 28K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38 28K /var/lib/docker/containers/665670b96e0320862f1c70e1ce6e83349df691b3d84791d9ca6cd25c8501a569/665670b96e0320862f1c70e1ce6e83349df691b3d84791d9ca6cd25c8501a569-json.log 24K /var/lib/docker/containers/bcc3cda2e8ccd7fa57e83ee11dcc26a47604c8dd6a0c4d9155690cce42db14e5 16K /var/lib/docker/containers/9b10cb71ecb9a7af213655649568cf5d3733c001ab89ee1714fef9db0ddba0f2/9b10cb71ecb9a7af213655649568cf5d3733c001ab89ee1714fef9db0ddba0f2-json.log 8.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/config.v2.json 8.0K /var/lib/docker/containers/c8c2035c5328d0b6efbcfe41e55b8aa272b3f5cfdf029898585eeb12cd01594f/config.v2.json 8.0K /var/lib/docker/containers/bcc3cda2e8ccd7fa57e83ee11dcc26a47604c8dd6a0c4d9155690cce42db14e5/config.v2.json 8.0K /var/lib/docker/containers/b25cbbb806a80473049080db470be6f6b4755ed674521a5e26cf697f2befde5e/config.v2.json 8.0K /var/lib/docker/containers/3b6eca5c6348d76dfb3776358ac7dbeb7b2a2c60977170c58e87d8d41ea69f20/mounts/shm 8.0K /var/lib/docker/containers/3b6eca5c6348d76dfb3776358ac7dbeb7b2a2c60977170c58e87d8d41ea69f20/mounts 8.0K /var/lib/docker/containers/35230c29fd65bde430becab1b53035b1b670aaa40381892bde04b79c68da5c8a/config.v2.json 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/resolv.conf.hash 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/resolv.conf 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/hosts 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/hostname 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/hostconfig.json 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38-json.log 4.0K /var/lib/docker/containers/fba15cd5e5e96d9cc68e405a3ef2921043cab05746ae9cd60811041625554c38/config.v2.json 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/resolv.conf.hash 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/resolv.conf 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/mounts/shm/mono.226 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/mounts/shm 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/mounts 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/hosts 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/hostname 4.0K /var/lib/docker/containers/fb959334cdbb75a5c400f2e319c35da75251ef9b070f43ff7a9c454b98171bd6/hostconfig.json 4.0K /var/lib/docker/containers/d053aefdd74c8caceccd18d2f4f6568cb9ea3a3a3c974571adb90efc65c84d40/resolv.conf.hash The ID looks like Sonarr: root@Mercure:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3b6eca5c6348 binhex/arch-plex "/usr/bin/tini -- /b…" 33 minutes ago Up 33 minutes binhex-plex 072b0050b358 titpetric/netdata "/run.sh" 2 days ago Up 46 hours Netdata a8f0ea007e70 linuxserver/bazarr "/init" 2 days ago Up 46 hours 0.0.0.0:6767->6767/tcp bazarr fba15cd5e5e9 google/cadvisor:latest "/usr/bin/cadvisor -…" 2 days ago Up About an hour 0.0.0.0:8082->8080/tcp cadvisor bba2c290af99 linuxserver/jackett "/init" 10 days ago Up 46 hours 0.0.0.0:9117->9117/tcp jackett 434c82b18a17 linuxserver/ddclient "/init" 4 weeks ago Up 46 hours ddclient d053aefdd74c linuxserver/hydra2 "/init" 4 weeks ago Up 46 hours 0.0.0.0:5076->5076/tcp hydra2 3aae22fe6c7f linuxserver/transmission "/init" 4 weeks ago Up 46 hours 0.0.0.0:9091->9091/tcp, 0.0.0.0:51413->51413/tcp transmission 8d60b1c98afb linuxserver/ombi "/init" 4 weeks ago Up 46 hours 0.0.0.0:3579->3579/tcp ombi fb959334cdbb linuxserver/sonarr "/init" 4 weeks ago Up 46 hours 0.0.0.0:8989->8989/tcp sonarr 57abb32f88a8 linuxserver/nzbget "/init" 4 weeks ago Up 46 hours 0.0.0.0:6789->6789/tcp nzbget b25cbbb806a8 linuxserver/radarr "/init" 4 weeks ago Up 46 hours 0.0.0.0:9898->7878/tcp, 0.0.0.0:7979->9899/tcp radarr 9d325450554d eafxx/traktarr:latest "/init" 6 weeks ago Up 46 hours Traktarr 4218bcedf795 linuxserver/tautulli "/init" 6 weeks ago Up 46 hours 0.0.0.0:8181->8181/tcp tautulli 35230c29fd65 binhex/arch-radarr "/usr/bin/tini -- /b…" 6 weeks ago Up 46 hours 0.0.0.0:9797->7878/tcp radarr-uhd-binhex Edited November 5, 2019 by yendi Quote Link to comment
trurl Posted November 3, 2019 Share Posted November 3, 2019 6 hours ago, yendi said: Today I see that my docker image (100GB) I split your post into the Docker FAQ feedback its own thread. As explained in this very first post in the Docker FAQ thread: On 5/8/2017 at 8:40 PM, Squid said: This thread is reserved for Frequently Asked Questions, concerning all things Docker, their setup, operation, management, and troubleshooting. Please do not ask for support here, such requests and anything off-topic will be deleted or moved, probably to the Docker FAQ feedback topic. If you wish to comment on the current FAQ posts, or have suggestions or requests for the Docker FAQ, please put them in the Docker FAQ feedback topic. Thank you! Please don't post in the FAQ thread unless you are posting the ANSWER to a Frequently Asked Question. 6 hours ago, yendi said: Today I see that my docker image (100GB) I always recommend a docker image size of 20GB. There is some slight chance you would need a little more since you have so many dockers. Unless you have one or more of your docker applications misconfigured, you are very unlikely to even need 30G. The most common reason for filling docker image is an application that is writing to storage that isn't mapped. This would be a setting in the application itself. You must make sure that every place the application can be set to write something is set to use a path that corresponds to the container path in the volume mappings configured for the docker. Common mistakes are not using the same upper/lower case as specified in the mapping, or not using an absolute path (must begin with /). Making docker image larger will not fix the problem, it will only make it take longer to fill. 6 hours ago, yendi said: EDIT 2: I solved the issue, easy... I clicked on the "Container size" on the bottom of the Docker page. I saw that Radarr was 50GB... I updated it to last version and my issue was solved: 11% docker img utilization... Son't know why Radarr grow that much, will monitor the situation. When you updated the docker, it was reinstalled, so that would explain why it wasn't using the space any longer. But it is likely it will continue to grow since you didn't actually change anything that was causing it to grow. Check all of the paths specified within the application settings. Quote Link to comment
Squid Posted November 3, 2019 Share Posted November 3, 2019 5 hours ago, yendi said: I saw that Radarr was 50GB... Like @trurl said, the reinstall fixed the problem temporarily. But it would help to solve the issue if we knew what was 50GB (there's 3 columns there) 5 hours ago, yendi said: I had a 17Gb Sonarr log https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564326 Quote Link to comment
yendi Posted November 3, 2019 Author Share Posted November 3, 2019 Thanks for the input guys. For the Sonarr log, thanks I put the extra parameter for the log size. I had the rotation enabled but I did not know that I had to remove the docker to make it work. Regarding Radarr, I dont understand how it can fill up as all the path are mapped correctly. I updated the docker and few hours later it was also 21 Gb large. So I removed it completely and reinstalled it. Strange thing is that my config for all docker is the same since almost 8 months and I downloaded around 10 TB of data using Radarr. So I don't think it's a miss configuration. If the issue happens again, is there a way to list all files from a container ? To know what is exactly filling it ? Thanks again and sorry for the post in the FAQ. Quote Link to comment
yendi Posted November 5, 2019 Author Share Posted November 5, 2019 (edited) Ok I found the real issue, it seems that somehow some files are written in opt/radarr/ inside the docker.img - I'm investigating right now. Edited November 5, 2019 by yendi Quote Link to comment
trurl Posted November 5, 2019 Share Posted November 5, 2019 25 minutes ago, yendi said: Ok I found the real issue, it seems that somehow some files are written in opt/radarr/ inside the docker.img - I'm investigating right now. I don't use radarr, but /opt/radarr would definitely be inside the docker image, unless you have mapped /opt or /opt/radarr to Unraid storage. But I doubt mapping that is the usual way. More likely you are just missing setting some path within the application settings and it is defaulting to that path. Quote Link to comment
yendi Posted November 5, 2019 Author Share Posted November 5, 2019 Yep it seems to be the issue. I assume that during some test that I made somedays I mapped some movies to no path, and the app is defaulting to it... 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.