coolman2170

Great, thanks everyone who responded, I'm a dummy.

Probably another stupid question, but is that UI referring to the container size button on the docker tab?

Oh wow no wonder. I'm an idiot. So when people complain that their docker.img is filling up, how do they determine that?

Oh okay, so the docker.img is actually empty? Is it just a matter of giving it time to set up or will it not change to a smaller size until I save something to it?

I understand that you're saying the incorrect mapping path could be within the application itself. I guess I don't know how to write that coherently in a sentence, but I get you're saying with regards to deluge for instance, my downloads are supposed to go to completed, incomplete, or unzipped_torrents. If I don't have those shares in the downloads folder, or deluge can't find them because there is an error with the spelling of the downloads or data path, it will save to docker image. I'm not saying that what I've done have been fixes, I get that removing appdata and expanding the docker image will not solve the problem. All I'm trying to do is figure out which container is causing the problem. I was under the impression that if my array has no appdata, and my docker has no containers, that the docker.img couldn't be filled from apps/containers such as deluge. I could be misunderstanding "fill" and "growing". Currently, I have no appdata and no containers in my docker. No apps, nothing. If I disable docker through settings>docker>no, delete the current docker image, and then re-enable docker, the docker image will immediately be full. I assume this is what you mean when you say fill, but if you're referring to whether it grows after initially enabling it, I can't tell because the moment docker is enabled, the docker.img share maxes out to whatever I set it at.

trurl, I have no doubt that one or more of my apps is improperly mapped, but I'm not sure how to figure out which one. I spent the better half of yesterday checking each container and I couldn't find anything. I'm also not sure how the docker image can be blowing up due to an app after removing all appdata and deleting all containers from docker. Do certain apps function outside of docker? I think it may be Plex as I don't think the transcoding was initially mapped correctly and it was the only app malfunctioning. However, even after deleting it entirely, the docker image still blows up.

Apologies. Here's a screenshot of the container size with docker enabled and appdata deleted.

Which part is inconsistent? Yesterday, before I deleted my appdata, I deleted the docker image, reinstalled it, then reinstalled my apps. Let the containers run one at a time, checked the container sizes, and nothing got larger than 1gb. Since I have backups of my apps and have no VMs, decided to delete all my appdata and see if it would make a difference. After deleting the appdata, I deleted the docker image, reinstalled it at 20gb and it maxed out. Out of curiosity, I deleted that docker image, set the new size to 2900gb (my largest disc is 3tb), and reinstalled the docker image, still with no appdata. Once again, docker image maxed out. Repeated the process again right now, same result.

Yep, disabled them individually and let them run. Nothing got larger than 1gb. Currently there is nothing in docker as I deleted all my appdata, although there are zipped backups in disk1.

I tried remapping everything using mnt/cache/appdata instead of mnt/user as recommended by squid in the FAQ (although I read other posts he recommends /user), didn't make a difference. Then I used cleanup appdata plugin and wiped all my apps out, no difference. Also wiped the rest of my cache for good measure. Just to see how big the docker image was, I put it on a 3tb disc and it still maxed it out. Currently running docker not enabled with no containers and no appdata. Not sure what's left other than my media folder. Let me know what my next step should be.

Thanks for the responses. The docker image is typically at 20gb, I only expanded it temporarily to see if that would prevent corruption and I could look inside it. I did as suggested and disabled autostart / deleted docker.img and restarted docker and looked at each container, but the sizes didn't grow significantly. I use radarr, sonarr, plex, jackett, and syncthing. I've since deleted syncthing and deleted its data from /appdata, but that didn't do anything. I disabled downloading from deluge, removed the entire queue, and disabled it as a downloader within radarr and sonarr. I also noticed the libvirt image is corrupt, although I don't have any VMs installed. I've run the extended test of fix common problems with no results either. I based my container mapping schemes on the ones done by spaceinvader, so I think they're right, but obviously somethings wrong.

Diagnostics attached. Have already tried disabling docker and deleting image file. When I re-enable it, docker image file is immediately maxed out, even expanding Vdisk to 400gb. Tried scrubbing, rebooting, no difference. Read through docker FAQ, can't find a container being the issue. Container sizes are all >400mb, and docker image file maxes out without re-installing them. When I click on the file it says, "the disc image file is corrupted." Using two 480gb SSDs in a pool. New to unraid, any help would be greatly appreciated. tower-diagnostics-20200118-0106.zip