Why are you allocating 120G to docker.img? Have you had problems filling it? 20G is often more than enough, unless you have something misconfigured, and making it larger won't fix those problems, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive, so any path configured within an application must match a container path, case-sensitive.
Also, why do you have your appdata, domains, system shares configured to be moved to the array? If these are on the array, dockers/VMs will have performance impacted by slower parity, and will keep array disks spunup since these files are always open.