For posterity...
Assuming Docker is running, the docker.img vdisk mount point can be found by issuing the following command from the command line.
mount |grep docker.img
Which (on my system) shows:
/mnt/pool-a/docker/docker.img on /var/lib/docker type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/)
/mnt/pool-a/docker/docker.img on /var/lib/docker/btrfs type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/)
Once the mount point is found, take a look at the contents:
root@beast:/mnt/disk1# ls -l /var/lib/docker
total 16
drwx--x--- 1 root root 20 Feb 6 12:32 btrfs/
drwx--x--x 1 root root 152 Feb 6 12:30 buildkit/
drwx--x--x 1 root root 12 Feb 6 12:30 containerd/
drwx--x--- 1 root root 2816 Feb 13 18:30 containers/
-rw------- 1 root root 36 Feb 6 12:30 engine-id
drwx------ 1 root root 10 Feb 6 12:30 image/
drwxr-x--- 1 root root 10 Feb 6 12:30 network/
drwx------ 1 root root 20 Feb 6 12:30 plugins/
drwx------ 1 root root 0 Feb 13 18:27 runtimes/
drwx------ 1 root root 0 Feb 6 12:30 swarm/
drwx------ 1 root root 44 Feb 13 18:27 tmp/
drwxr-xr-x 1 root root 12 Feb 6 12:40 unraid/
-rw-r--r-- 1 root root 154 Feb 13 16:53 unraid-autostart
-rw-r--r-- 1 root root 5366 Feb 13 17:52 unraid-update-status.json
drwx-----x 1 root root 184 Feb 13 18:27 volumes/
The directories and files listed can be safely removed from the previous path. On my server, this was everything under /mnt/pool-a/docker EXCEPT for docker.img.
Bottom line... I was unaware that migrating from a directory based Docker data-root to a vdisk Docker data-root would leave behind so many unneeded files and directories.