Reclaiming disk space after PAW upgrade

[gtonkin]

Just finished upgrading PAW 2.0.39 to 2.0.43 and it worked although I nearly ran out of disk space again and am very low after the upgrade.

Subsequent to the testing of PAW, I did go back to the PAW 2.0.39 scripts folder and run the Clean.ps1 script which also for the first time removed some cruft and cleared up about 7Gb of space (702Mb reported by the script).

Before the upgrade my WindowsFilter folder consumed 34GB on disk, after upgrade and clean, it now consumes 54GB.
I have 22 folders with folder dates coinciding with my previous installation and consuming 20GB - seems very much like the extra 20GB I am not expecting.

Running "docker image ls" and "docker container ls" show only what seems to be necessary - previously I have had duplicate images/services.
As PAW was up and running, I crossed fingers and ran "docker system prune" - nothing found/removed/purged/space freed up.

I then ran "docker image prune -a -f" which reclaimed 3.905GB and seems to have removed all but 1 old folder in the WindowsFilter folder.

After a bit more reading, I looked for Orphaned docker images but none found/removed.
Docker leak check returned No errors found.

My remaining old folder contains 11.5GB (for those doing the maths, 11.5+3.9 does not equal 20 - but those are the numbers I have)

Any tips for cleaning up further would be greatly appreciated.

[dr.nybble]

There will be some image layers from an older install as the large Windows base image layer will not change.

You can also run 'Disk Management' to see the size of the 'sandbox' virtual hard drives allocated for each container. Are any using a suspiciously large amount of space? Recently had someone's AV software touching every file in the virtual hard drives causing them to be copied up into the sandbox.

[gtonkin]

Thanks for the reply Dr Nybble.
Disk Management shows 23 sandboxes/portable base layers - all are 19.87GB capacity and all are roughly 19 GB free (995 free) - Nothing untoward here.
What is not shown is any description for each sandbox, the volume is just blank so cannot glean much more.

[Drg]

We are faced with such a situation that the docker does not see containers that have remained a rudiment from previous versions.
The only solution that I found is to completely delete the folder manually using utilities. docker creates files that cannot be deleted using standard windows methods.

Any solution?

[gtonkin]

The only way I have cleaned up stubborn containers in the past has been a sledge-hammer approach i.e. docker-ci-zap
Unfortunately this removes ALL containers in the WindowsFilters folder but is useful when you have broken your PAW beyond repair.

[Drg]

The only way I have cleaned up stubborn containers in the past has been a sledge-hammer approach i.e. docker-ci-zap
Unfortunately this removes ALL containers in the WindowsFilters folder but is useful when you have broken your PAW beyond repair.

Oh nice, thx i try it!