this post was submitted on 07 Nov 2024
30 points (89.5% liked)

Selfhosted

40296 readers
271 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
 

Hi folks,

You all have been instrumental to my self-hosting journey, both as inspiration and as a knowledge base when I'm stumped despite my research.

I am finding various different opinions on this and I'm curious what folks here have to say.

I'm running a Debian server accessible only within the home with a number of docker images like paperless-ngx, jellyfin, focalboard, etc. Most of the data actually resides on my NAS via NFS.

  1. Is /mnt or /media the correct place to mount the directories. Is mounting it on the host and mapping the mount point to docker with a bind the best path here?

  2. Additionally, where is the best place to keep my docker-compose? I understand that things will work even if I pick weird locations, but I also believe in the importance of convention. Should this be in the home directory of the server user? I've seen a number of locations mentioned in search results.

  3. Do I have to change the file perms in the locations where I store the docker compose or any config files that don't sit on the other end of NFS?

Any other resources you wish to share are appreciated. I appreciate the helpfulness of this community.

you are viewing a single comment's thread
view the rest of the comments
[–] KyuubiNoKitsune@lemmy.blahaj.zone 1 points 2 weeks ago* (last edited 1 week ago) (4 children)

I found this to be extremely underperforming. If you plan on doing anything that requires high throughput, don't use the docker NFS operator.

[–] mbirth@lemmy.ml 2 points 2 weeks ago (3 children)

There’s no difference between using a volume in Compose to mount a share or your server’s fstab file. Both do the same kind of mount.

[–] KyuubiNoKitsune@lemmy.blahaj.zone 1 points 1 week ago (2 children)

It's doing something different, I was using to mount an AWS FSx for ZFS share on a beefy machine (1.2GB/s network throughput) and was getting less than 50MB/s throughput using docker to mount it, but getting the full 1.2GB/s when mounted outside and mapped to a volume in the container.

[–] mbirth@lemmy.ml 1 points 1 week ago (1 children)

How did you mount it outside the cluster? Did you have a look at the mtab and used the exact same options in the compose file?

It's been a few months but I as far as I remember used all the same mounting options