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

Selfhosted

40347 readers
397 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
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] SeeJayEmm@lemmy.procrastinati.org 4 points 10 months ago (5 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.

[–] sabreW4K3@lemmy.tf 1 points 10 months ago (4 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?

[–] SeeJayEmm@lemmy.procrastinati.org 2 points 10 months ago (3 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"
[–] sabreW4K3@lemmy.tf 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.

[–] SeeJayEmm@lemmy.procrastinati.org 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.

[–] sabreW4K3@lemmy.tf 2 points 10 months ago
load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)