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 save my databases between restart mysql in Docker container
  • Remote debugging NodeJS in Docker with Visual Studio Code
  • Use perf inside a docker container without --privileged
  • How can I specify the machine in docker swarm mode?
  • ImportError: cannot import name <package> in pods while restarting pod fixes
  • Running a single Docker Cloud's HAProxy container with SSL and non-SSL simultaneously
  • Setting ssh public keys on Docker image
  • Sentry Docker Port 80
  • Restarting named container assigns different IP
  • docker run command output
  • Too many docker mounts
  • Docker daemon start error on ubuntu 12.04
  • 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.