-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems to be stuck on checking size of Container Manager? #155
Comments
Went out for a few hours and it was complete, saying that my Container Manager was 2256 GB in size which I think explains the length of time taken. But I don't think that is correct - there are some containers (like Plex) that have folders that will be big (my film library etc) but I'm trying to keep them pointed toward the original HDD volume. Is the size estimation including those folders, and if so will that preclude me from moving the Container Manager to my NVME volume which is only 1000 GB in size? |
The Plex Media folder totals 4.14 TB so I don't think it is included in the 2256 GB that the script thinks my Container Manager is sized at. |
That 2256 GB is the hidden I'll add a progressbar for getting package sizes. |
By the time it removed 'dangling Dockers', Container Manager was only 94 GB in size. |
I should be "Removing dangling docker images" before checking the |
Have successfully moved all my apps bar Container Manager over to my NVME volume. However, it now appears to be stuck on 'Checking size of Container Manager'. It appears to be getting stuck here whether I select move or backup.
There is no progress bar or etc appearing. I have tried several times to move Container Manager using this script with the same problem, although the longest I have let it run is about 1 hour. Should I be leaving it longer?
I have about 25gb in the Docker folder, which I did earlier move to my NVME volume following this guide.
But Container Manager itself remains on the HDD volume Could that be what is causing the problem?
The text was updated successfully, but these errors were encountered: