Replies: 2 comments
-
You can mount your TrueNAS shares in two ways, bind mount from the host (simpler) or mount directly in Compose using driver_opts. Below are some examples.
Point Compose volumes to the host paths:
Tips: |
Beta Was this translation helpful? Give feedback.
-
Thank you a lot.. one little step forward. Mounting manually is fine, fstab is ignored but mount -a works ..._devnet or delay_conenct arent helping either... and deploying brings up chown issues, but i guess i will have to ask somwhere else as in the portainer threads :-) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, i am clueless for two days now.
i am trying to setup paperlessngx. My setup is proxmox -> portainer on alpine linux VM -> paperlessngx via stack
Running it locally with a shared consumefolder is no problem at all but now i am trying to get those four datafolders onto my TrueNAS.
my shares are nfs and cifs. user, pwd, uid, guid (user paperless) are matching on truenas and the portainer vm
Short question: what is the best/recommended way to do it and can you help me?
most propably i am just too stupid ...
long story
what i have tried so far:
create volumes in portainer using cifs or nfs works fine (creation successful) , but when browsing it appears the shares are empty (placed some files in it to check) ... and even if i put in the wrong IP, volume creation is "successful" ... so i have never tried deploying
creating volumes in portainer on the mounted directory ... -> i am too stupid to find the correct "Driver Options"
defining cifs or nfs credentials on volumes (not service) in stack compose
mounting shares via cifs or nfs on the host is working fine so
at the moment i am concentrating on mounting the nfs share in the usually created folder in /var/lib/docker/volumes and mount the nfs share into it ... but deploying isnt working either.
Edit --- i dont know who to post code... tried the "code" above, but it squeezed all in one line :-/ sorry mates
deploying regularly, those volumes are created in /var/lib/docker/volumes/paperless_xyz
on the share side i tried different owner/group combinations ... root/root, paperless/root, paperless/paperless
After mounting, the owner/group from the created dir are overwritten by the one of the shares.
Error when deploying:
Failed to deploy a stack: Network paperless_default Creating Network paperless_default Created external volume "xyz" not found
whereas xyz is one of the volumes... seems random whichone failes, the errormessage stays the same
can you help me out ? What information do you like to have on top?
Beta Was this translation helpful? Give feedback.
All reactions