I see you have 50GB for your docker image. If you have everything configured correctly it is extremely unlikely to ever need even 20G. When a user has such a large docker image, I suspect they have had issues with docker image filling up and they try to fix those issues by making it larger. Making it larger only makes it take longer to fill, it doesn't fix anything.
But it is currently using only 4.7G, which is very reasonable. Have you ever had docker image filling up?
Looks like you do have docker image corruption though:
Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 12288 csum 0x6373a212 expected csum 0x07b4d05b mirror 1
Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 16384 csum 0x11cc18e0 expected csum 0x5ecef011 mirror 1
Mar 25 09:06:04 TOWER kernel: BTRFS warning (device loop2): csum failed root 372 ino 9239 off 12288 csum 0x6373a212 expected csum 0x07b4d05b mirror 1
Delete docker image, recreate it at the more reasonable size of 20G, and then you can reinstall all your dockers exactly as before using the Previous Apps feature on the Apps page.
Not likely related, but are all your plugins up-to-date? I notice Wake-on-LAN is replacing libraries installed by Unassigned Devices with older versions.