So here's what I've found so far.
If I start fresh, then bring the system up (
docker-compose up -d), then the volumes are created properly and data I add to the CMS gets written to the database (and on the to local filesystem) as expected.
If I then stop/start the containers, everything persists as it should (
If I down/up the containers, everything persists as it should (
If I then reboot the machine, the volumes are no longer correctly mounted and my changes in the CMS are gone. If at that point I down the containers and bring them back up (
docker-compose up), my changes are restored.
When the containers are working as expected, I see a cifs mount within the container to
//10.0.75.1/C => /var/lib/mysql which is not there after a restart.
So it appears there's some issue with Docker for Windows and resuming containers with volume mounts. I'll see if I can understand what the issue is some more.