manwichmakesameal , 11 months ago (edited 11 months ago)

Also, to add to this: you’re setup sounds almost identical to mine. I have a NAS with multiple TBs of storage and another machine with plenty of CPU and RAM. Using NFS for your docker share is going to be a pain. I “fixed” my pains by also using shares inside my docker-compose files. What I mean by that is specify your share in a volume section:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">volumes:
</span><span style="color:#323232;">  media:
</span><span style="color:#323232;">    driver: local
</span><span style="color:#323232;">    driver_opts:
</span><span style="color:#323232;">      type: "nfs"
</span><span style="color:#323232;">      o: "addr=192.168.0.0,ro"
</span><span style="color:#323232;">      device: ":/mnt/zraid_default/media"
</span>

Then mount that volume when the container comes up:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">services:
</span><span style="color:#323232;">  ...
</span><span style="color:#323232;">  volumes:
</span><span style="color:#323232;">        - type: volume
</span><span style="color:#323232;">        source: media
</span><span style="color:#323232;">        target: /data
</span><span style="color:#323232;">        volume:
</span><span style="color:#323232;">          nocopy: true
</span>

This way, I don’t have to worry as much. I also use local directories for storing all my container info. e.g.: ./container-data:/path/in/container