this post was submitted on 19 Nov 2025
38 points (100.0% liked)

Selfhosted

53070 readers
638 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 2 years ago
MODERATORS
 

I'm new to Docker, but I'm trying to deploy some containers that will need to read and write to a network shared volume. I'm hoping to run things like Navidrome, Immich, and an Arr Stack. The containers are on Ubuntu and my network volume is on a qnap machine. It is discoverable from Ubuntu without issue.

Do I need to mount the shared volume in Ubuntu or can I just refer to it in the Docker Compose file?

I know I need to mention the location of the volume in the Docker Compose file, but I'm not sure how to write that. How do I include the un/pw information for the NAS?

I read about bind mounts in Docker's documentation. Is that what I want to use? Again, how do I include the un/pw information? I'm not sure how to use the commands.

The volume path for the navidrome folder is //tiger-nas/music/music for example.

I appreciate any help.

you are viewing a single comment's thread
view the rest of the comments
[–] roofuskit@lemmy.world 11 points 2 days ago (2 children)

Mount it locally. Then reference the local mount in your docker command or compose file.

[–] spiffpitt@lemmy.world 4 points 2 days ago (1 children)

I'm constantly seeing this advice, dispite docker supporting nfs volumes. How do you handle docker starting containers before the shares are mounted? making the docker service as a whole wait for network mounts? what about containers that dont need to wait for a network drive?

[–] roofuskit@lemmy.world 2 points 2 days ago

Honestly I've never had that issue, but if you use compose you can delay the start of a container and use the "depends-on" function to hold any other containers. But yes docker supports both NFS and SMB.

[–] modus@lemmy.world 1 points 2 days ago

Thank you. I'll try.