UPDATE
Removing #user/Library/Containers/Docker/Data/vms/0/data/Docker.raw allowed Docker to at least open up and run. That said everything is back to factory default and would require a rebuild. Swap the Docker.raw file back an original problem is back…looking for a way to At this point, open to rebuilding as that might be a quick way back to normal - HOWEVER - how would I prevent this from happening again in the future?
UPDATE 2
Moved the Docker.raw file to another drive…started a fresh Docker.raw file. This allowed Docker to at least run where I then went to preferences to increase the disk image size. Quick docker, replace the original Docker.raw file and everything has returned to normal (yea!) - then the prune commands worked as expected.
OPEN QUESTION
Unclear how the raw file is filling up or how to better manage. Any source video files, for example, are stored externally. Looking at the app in question, CPU and memory usage can run high at times and the images themselves clock in collectively at around 1.7gig…certainly not the allocated 64gig (which is now 72) so what is happening here? Docker Desktop has a “Clean Up’ function which then states 'Space to be reclaimed 0 Bytes.”