Hello,

My "Docker" storage usage is almost fully utilized. From my understanding, I likely have a misconfigured Docker container that is saving data to the docker.img file instead of the intended array.

Could you help me figure out how to identify which Docker container is misconfigured?

Thank you!

 

Edited December 3, 20241 yr by Monokel

bumb

diag is only part of the story
when dealing with docker for security as passowrds and private setting can be exposed teh daig done't capture these setting.

my 2 cents first would be 2 clear logs and start all docker you want to keep and run the docker maintence scritps 

Clear all docker logs:
https://forums.unraid.net/topic/178033-bmartino1-user-scripts/#findComment-1478646

Clear docker setting anything that is not in use:

 

Thank you!
Can I try testing each Docker container one by one by reinstalling them according to the suggested scripts? If I happen to reinstall the misconfigured one, will the storage usage go down? Could this approach work in general?

I'm going to say no...

I orginaly designed the docker maintenance script to just run the prune command to delete and remove unnecessary temp data within the docker.img that unraid creates due to testing and building dockers. More with "dangling" docker. (more a issue when using docker compose)

As this script will remove all non-running and unused docker images and volume (this will not delete data from appdata! add container template to bring it back). Then cleans up the docker system as seen in the doc links in the post...

it was also by happen stance that if a docker wasn't running, it would be removed. can it help identify the missing one. Kinda but not in an easy and obvious way.

When troubleshooting, I clear all docker logs and restart the docker 1 at a time and watch the docker log of that docker and other logs it has if any. This way I can easily catch a misbehaving docker. 

Reinstalling dockers is a good approach. I would recommend increasing the docker image a bit. and double check if a docker done't have a /mnt/user or /mnt/Disk path to wat its writing files too. I would suspect a Database docker first.