About my version:
To prepare for the share:
In the Shared Drives dialog, I reset the credentials. I then select the E drive and entered the proper credentials when prompted.
Now everythinkg should be ready to run my docker-compose script which is on E:
version: '2'
services:
mysql:
image: mariadb
environment:
MYSQL_ROOT_PASSWORD: admin
volumes:
- ./data:/var/lib/mysql
ports:
- "3306:3306"
If I try and run it via docker compose:
docker-compose up
I see the “./data” directory is made.
I get errors when accessing files in the volume.
[ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
mysql_1 | 2018-10-02 7:16:07 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
and the container exits.
Now, I can get this to work but it is strange 
…
So let’s start over. I remove the container, delete the data directory and reset the credentials.
I now again bring the container up:
docker-compose up
I now get a message from docker to share E:
I share it! I am then prompted for my credentials.
and … I get the same problems as before.
The data directory is created but not writable.
Here comes the strange part …
If the Share Drives dialog is open, there is nothing selected.
If you either change tabs, if the Setting dialog is open, or close and re-open the setting dialog, you are presented with a “Apply changes” dialog. Select “Apply”. If I now bring the container up again is runs.
If you look and the Share Drives dialog, there is nothing selected.
If I stop the container, check the E drive in the Share Drives dialog, The container won’t start.
If I stop the container, check the E drive and C drive in the Share Drives dialog, The container won’t start.
only if I select the C drive (or leave everything unchecked) in the Share Drives dialog will start.
I have repeated this process many times so (on my machine 
) the process is very repeatable.
Does anyone have any wise words for me? Is this a bug?