What is easiest solution to automatically resolve missing mounts due to e.g. a power outage?

Comments

• freeearth@discuss.tchncs.de ⁨4⁩ ⁨months⁩ ago

  Just specaluting… is it possible to mount NFS through systemd and make docker service dependent from that mount?

  source

  • avidamoeba@lemmy.ca ⁨4⁩ ⁨months⁩ ago

    This is the answer. You can straight up make things dependent on .mount units that represent stuff in fstab. To add, you can create any number of systemd services that just check if something is “as you want it” and only then “start”. You simply make the Exec line “/bin/bash -c ‘your script here’”. Then you make whatever else you want dependent on it. For example I have such a unit that monitors for Internet connection by checking some public DNS servers. Then I have services that depend on Internet connection dependent on that.

    source

    • samwwwblack@lemm.ee ⁨4⁩ ⁨months⁩ ago

      You can use RequiresMountsFor= (eg RequiresMountsFor=/media/storage-volume1) instead of manually adding .mount to After/Requires - you can then use .mount files or fstab as you’re stipulating the path rather than a potentially changeable systemd unit name.

      The systemd.mount manpage also strongly recommends using fstab for human added mount points over .mount files.

      source

      • -> View More Comments
    • sylverstream@lemmy.nz ⁨4⁩ ⁨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.

      source

      • -> View More Comments
  • sylverstream@lemmy.nz ⁨4⁩ ⁨months⁩ ago

    Sorry, I’m absolutely not a Linux expert :) I use /etc/fstab for the mounts, and to manually re-mount I run “mount -a”.

    source

    • avidamoeba@lemmy.ca ⁨4⁩ ⁨months⁩ ago

      This is a great opportunity to learn a bit of systemd then. Look at my other comment.

      source

      • -> View More Comments
• h3ndrik@feddit.de ⁨4⁩ ⁨months⁩ ago

  I think that is a good question to write something positive about SystemD.

  I start my services with SystemD. I also moved my containers and docker-compose stack to be started by systemd. And it does mounting and bind-mounts, too. So I removed everything from /etc/fstab and created the files for systemd to mount the network mounts. And then you can edit the service file that starts the docker-container and say it relies on the mount. SystemD will figure it out and start them in the correct order, wait until the network and the mounts are there.

  You have to put some effort in but it’s not that hard. And for me it’s turned out to be pretty reliable and low maintenance.

  source
• Nollij@sopuli.xyz ⁨4⁩ ⁨months⁩ ago

  The absolute easiest and simplest would be to modify your grub config to have a longer timer on the boot menu, effectively delaying them until the NAS is up.

  That doesn’t necessarily mean it’s the best option- there are ways to make the actual boot process wait for mounts, or to stagger the WOL signals, or the solutions others have mentioned. But changing grub is quick and easy.

  source
• MangoPenguin@lemmy.blahaj.zone ⁨4⁩ ⁨months⁩ ago

  Best option is to delay docker startup until the mounts are ready.

  source
• monkeyman512@lemmy.world ⁨4⁩ ⁨months⁩ ago

  Try looking into “autofs”.

  source

  • sylverstream@lemmy.nz ⁨4⁩ ⁨months⁩ ago

    Thanks! I’ve just set that up. That would seem to solve the solution, right, without reboots?

    source

    • monkeyman512@lemmy.world ⁨4⁩ ⁨months⁩ ago

      Yes. The important detail is that it remounts the path once the path gets called. So I setup a cron job to “ls” the path every few minutes to make sure it’s always remounted quickly.

      source
• Cookie1990@lemmy.world ⁨4⁩ ⁨months⁩ ago

  Read systemd mounts and systemd dependencies.

  source
• grayaytrox@lemmy.world ⁨4⁩ ⁨months⁩ ago

  It’s been a while since I set it up, but from memory my mount point was set to be owned by root and immutable. That stopped any of my docker containers making new files and folders if the mounted drive or network location was not mounted or unavailable.

  source

  • sylverstream@lemmy.nz ⁨4⁩ ⁨months⁩ ago

    Yeah I used /etc/fstab which are static mounts.

    I switched to autofs and that seems to be much better, as it does the mounts “at runtime”, ie when requested.

    source
• Decronym@lemmy.decronym.xyz ⁨4⁩ ⁨months⁩ ago

  Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

  Fewer Letters	More Letters
  DNS	Domain Name Service/System
  NAS	Network-Attached Storage
  Plex	Brand of media server package

  ---

  [Thread #509 for this sub, first seen 13th Feb 2024, 14:05] [FAQ] [Full list] [Contact] [Source code]

  source
• lemmyvore@feddit.nl ⁨4⁩ ⁨months⁩ ago

  You can use bind mounts instead of volumes to prevent the container to start when the target is missing.

  docs.docker.com/storage/bind-mounts/

  I’m not sure what happens if the target goes down while the container is running. And you would still need a monitoring solution for telling the container to start when the target comes up.

  source
• ShellMonkey@lemmy.socdojo.com ⁨4⁩ ⁨months⁩ ago

  The other options of making the containers dependent on mounts or similar are all really better, but a simple enough one is to use SMB/CIFS rather than NFS. It’s a lot more transactional in design so the drive vanishing for a bit will just come back when the drive is available. It’s also a fair bit heavier on the overhead.

  Using NFSv4 seems to work in similar fashion without the overhead though I haven’t dug into the exact back and forth of the system to know how it differs from the v3 to accomplish that.

  source