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 Run a script at the start of Container in Cloud Containers Engine with Kubernetes
  • OpenCV error when Docker container is run on GKE
  • Can I select which services to run with Atlassian's Localstack
  • Docker Remote API - Pull/Create image not working
  • Vagrant and Docker with Microservices
  • Unable to install scala on phusion/baseimage
  • Re-build Go (App Engine) app running inside docker container?
  • Error 'import path does not begin with hostname' when building docker with local package
  • Docker, install postgresql in a container contain “ubuntu:14.04”, lost when out of the container
  • Assign domain name to the container
  • Running xterm in docker without X-server on host machine
  • Running docker container at specific URL(s)
  • 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:

    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.