- Minor
I had a leading space in my 'Docker vDisk location:', which caused the docker image to be located on root / in a directory called ' ' (space). Since root is memory, it empty on each reboot. It was quite difficult for me to figure out that was the file being written.
It is easy to get into that situation, just stop the docker, add a leading space, and apply and enable docker.
It is difficult to get out of the situation because the GUI will not let me remove the space or change it to a valid location, UNLESS i use the GUI folder popup navigation. If I click my way to the correct folder then the GUI updates the location.
I suspect the issue surfaced after i changed my docker image to be located on an external USB mounted with unassigned devices.
Background: I'm running a QNAP hardware with unRaid, I don't have room for SSD, and don't want disks spinning up. Hence plugged in an extra USB, used unassigned devices (thank you devs) to auto-mount usb, and moved the docker image there.
---
So my suggestion is to do a simple trim of the path on apply. Or something like that.