EDIT (March 9th 2021):
Solved in 6.9 and up. Reformatting the cache to new partition alignment and hosting docker directly on a cache-only directory brought writes down to a bare minimum.
###
Hey Guys,
First of all, I know that you're all very busy on getting version 6.8 out there, something I'm very much waiting on as well. I'm seeing great progress, so thanks so much for that! Furthermore I won't be expecting this to be on top of the priority list, but
Solved
Urgent
Hey man,
If you reboot your server everything will be reset to default and unRaid will mount the normal docker image upon boot.
Assuming you've created the share which I've mentioned, then docker won't be able to see those, since they work created on the path targeted by the symlink and not inside the docker.img file.
So it will see/start whatever container you have created into the docker image, or nothing if you created a new one before starting to work with the symlink a