August 9, 20214 yr Community Expert Corrupt docker.img. I notice you have given it 50G. Have you had problems filling it? 20G is usually more than enough and making it larger won't fix filling it, it will only make it take longer to fill. I recommend setting it to 20G when you recreate it. Read all this: https://wiki.unraid.net/Manual/Troubleshooting#Docker
August 9, 20214 yr Author Ah I see.. thanks for the info! Yes I had this problem once before, long time I think. But I just went to click Container Size, and it says Total Size of 8.49GB, not 50GB though...Writeable is nan, so not sure which I should be seeing.. Also I went to Settings, Docker, I am seeing this: btrfs filesystem show: Label: none uuid: 82c80fd8-8bfa-4379-9cfa-37a7ca41205f Total devices 1 FS bytes used 13.34GiB devid 1 size 50.00GiB used 30.57GiB path /dev/loop2 which seems like it's not filled up yet as well. I can follow the wiki to delete and recreate but this might happen again without hitting 50GB... Any idea what is happening?
August 10, 20214 yr Author I also just noticed that the logs are now 100% full and hence the logs are not showing anything, any idea how to clear it the proper way from the system? Seems like log are empty right now... Seems like something is bugged with the system Edited August 10, 20214 yr by CyberMew
August 12, 20214 yr Author On 8/10/2021 at 12:21 PM, trurl said: reboot Thanks. Reboot works. No need for me to touch the docker image, it wasn't filled (30GB out of 50GB). Log usage is fine now. Not sure what was up initially that caused it to error/lock up.. Also checked the container size, and they seems ok (not sure why the docker image is 30GB though) Edited August 12, 20214 yr by CyberMew
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.