Docker Volumes not mounted after host reboot

I start various docker containers through docker-compose up -d and they all have the restart always flags enabled.

When I reboot the host machine (Windows 10 Pro), the containers restart but it appears the volumes are not mounted. I know this because I keep the config files on the mounted volume and the services bring up the initial setup screen when I go to the webpages, plex for example does the starting new server. When I run docker-compose stop, and then docker-compose up -d they have the volumes mounted and are using the correct config files. Is there a difference between how the containers get started on a restart versus docker-compose up?

  • How to access Consul used in Docker overlay networks?
  • Chaning tcp_keepalive_* inside a docker container
  • during startup program exited normally. segmentation fault
  • Restoring a local pg_dumpall in a docker container
  • Symfony Process pgrep fails
  • Uninstall weave docker
  • How can I check how many containers are running a certain docker image?
  • Multiple nodejs workers in docker
  • can not push files to remote host
  • Make 2 volumes in docker gcc and java
  • gcloud docker push hanging
  • Spring boot docker plugin requires removing the image everytime
  • One Solution collect form web for “Docker Volumes not mounted after host reboot”

    For host-mounted volumes, it’s a known problem that the volumes are not available immediately after restart: https://github.com/docker/for-win/issues/584#issuecomment-286792858

    I recommend using non-host mounted volumes or other workarounds.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.