this post was submitted on 07 Jan 2024
7 points (100.0% liked)

Selfhosted

39435 readers
15 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
7
Best Way To Mount A Directory on Boot (lemmy.tf)
submitted 10 months ago by [email protected] to c/[email protected]
17 comments fedilink hide all child comments
 

Basically I have a Navidrome container and it's pointing at my music in a network mounted folder, what's the best way to ensure that it's always there, even after a reboot of my Pi?

top 17 comments
sorted by: hot top controversial new old
[–] [email protected] 12 points 10 months ago

Add it to your fstab

[–] [email protected] 7 points 10 months ago* (last edited 10 months ago) (1 children)

Assuming systemd, create a file like

/etc/systemd/system/dir-to-mount.mount

And then configure it per the systemd docs:

https://www.freedesktop.org/software/systemd/man/latest/systemd.mount.html

Then modify the docker unit file to have a dependency on the mount unit so it's guaranteed to be up before docker starts.

[–] [email protected] 1 points 10 months ago (2 children)

Is this method superior to fstab?

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago)

It has the benefit that the container can't start before the mount point is up without any additional scripts or kludges, so no race conditions or surprise behaviour. Using fstab alone can't provide that guarantee. The other option is Autofs but it's messier to configure and may not ship out of the box on modern distros.

[–] [email protected] 2 points 10 months ago

I'll let you in on a little secret: Fstab gets converted to mount units anyways.

[–] [email protected] 4 points 10 months ago (1 children)

fstab will do it, but the more important question is, what do you want to happen when it doesn't mount properly? Do you want the system to fail to boot? Do you want navidrome to not run?

[–] [email protected] 1 points 10 months ago (1 children)

Navidrome to not run would be optimal

[–] [email protected] 3 points 10 months ago (1 children)

It's probably best to wrap navidrome in a script that checks for the mount then.

[–] [email protected] 1 points 10 months ago

Thanks for the advice, I'll look into it.

[–] [email protected] 4 points 10 months ago (1 children)

Everyone's saying fstab but if Navidrome is in a docker container, just mount it as a volume on your container. I found this guide that seems to document it fairly well.

https://phoenixnap.com/kb/nfs-docker-volumes

This is how I'm handling NFS mounts in my docker stacks.

[–] [email protected] 1 points 10 months ago (1 children)

So this is my preferred method, but I found the blog post really confusing. Subsequently, it failed.

  navidrome:
    container_name: navidrome
    image: deluan/navidrome:latest
    ports:
      - "4533:4533"
    environment:
      ND_SCANSCHEDULE: 1h
      ND_LOGLEVEL: info
    volumes:
      - "/opt/navidrome/data:/data"
      - "/nfs/Shared Music:/music:ro"
      - type: volume
      - source: nfs
      - target: /nfs
      - volume:
        nocopy: true
  volumes:
    nfs:
      driver: local
      driver_opts:
        type: nfs
        o: "addr=XXX.XXX.XXX.XXX,nolock,soft,rw"
        device: ":/mnt/HD/Public"

What am I doing wrong?

[–] [email protected] 2 points 10 months ago (1 children)

I'm rather confused by the config you posted. The NFS config should all be down in the volumes: section the only thing you reference in the service section is the name of the volume you define and the path to mount in the container. Something like this (tho I'm guessing as to what should be what with your setup).

services:
  navidrome:
    container_name: navidrome
    image: deluan/navidrome:latest
    ports:
      - "4533:4533"
    environment:
      ND_SCANSCHEDULE: 1h
      ND_LOGLEVEL: info
    volumes:
      - /opt/navidrome/data:/data
      - music:/music
volumes:
  music:
    driver_opts:
      type: nfs
      o: "addr=XXX.XXX.XXX.XXX,nolock,soft,ro"
      device: ":/nfs/Shared Music"
[–] [email protected] 1 points 10 months ago (1 children)

Thank you so much.

One more question, do I have to point it directly at the directory I want or can I point it at one above? Reason being, I have a film directory which I will point Jellyfin to too.

[–] [email protected] 2 points 10 months ago (1 children)

You can point it to any nfs file system you have exported on the file server. That's entirely up to you.

[–] [email protected] 2 points 10 months ago

Thank you

[–] [email protected] 2 points 10 months ago

It sounds like you’ve got your solution already, but just in case someone stumbles on this later, I thought I’d mention autofs.

I’m coming to prefer it over fstab entries because it handles disconnections nicely and attempts to reconnect. Worth checking out for those who haven’t played with it.

[–] [email protected] 2 points 10 months ago

Call me old fashioned, but fstab...