I’ve got a QNAP NAS and two Linux servers. Whenever the power goes down, the UPS kicks in and shut downs the NAS and the Linux servers, all good. The servers + NAS are automatically started when the power comes back on line using WOL. All good.

The problem is that I have apps running using Docker which heavily rely on connections to the NAS. As the Linux servers boot quicker than the NAS, the mount points are not mounted, and thus everything falls apart. Even when I manually re-mount, it’s not propagated to the Docker instances. All mount points use NFS.

Currently, I just reboot the Linux servers manually, and then all works well.

Probably easiest would be to run a cron job to check the mounts every x minutes, and if they are not mounted, then just reboot. The only issue is that this may cause an infinite loop of reboots if e.g. the NAS has been turned off.

I could also install a monitoring solution, but I’ve seen so many options that I’m not sure which one to do. If it’s easier with a monitoring solution, I’d like the simplest one.

  • @[email protected]OP
    link
    fedilink
    English
    210 months ago

    That’s interesting! I’ve converted all my docker run commands to docker compose, as I found that easier to manage. But, I guess you can’t do the dependencies like you have. Also, yours has the advantage it always pulls the latest.

    • key
      link
      fedilink
      English
      310 months ago

      Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.

      • Avid Amoeba
        link
        fedilink
        English
        1
        edit-2
        9 months ago

        Exactly. In fact I have a few multi-container services with docker-compose that I have to write systemd unit files for.

    • qaz
      link
      English
      110 months ago

      Perhaps you could also add the mounts as dependencies to the Docker daemon.