Immich•4mo ago

Can't get my Upload Library to the right NFS share

So, requested some brief help the other day. I'm very slow at finding time to do this so bear with me. I am also still new to this. I got Immich running (yay!), and now I'm trying to get my uploads folder to work with an NFS share on my NAS instead of on the mini NUC computer I'm using to run Immich. On my NAS, my preferred folder is located at the :/immich and created an NFS share in Portainer using the Volumes tab. The share should have multiple TB's worth of storage options. Portainer says that the NFS is now stored here: /var/snap/docker/common/var-lib-docker/volumes/immich/_data In the .env file I've got UPLOAD_LOCATION = /var/snap/docker/common/var-lib-docker/volumes/immich/_data Now, I've re-started the containers, and immich is working, but, I'm still showing as only having 29GB of space. And, portainer is telling me that the NFS volume I created is unused. I'm too new to Portainer to understand what I've done wrong, but I've tried following a few other examples like the one shown here: https://immich.app/docs/guides/custom-locations/ Any help appreciated on pointing out my error.

16 Replies

Immich•4mo ago

:wave: Hey @Geoffrey, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

Immich•4mo ago

Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed.

GitHub

immich-app immich · Discussions

Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.

FAQ | Immich

User

GitHub

Issues · immich-app/immich

High performance self-hosted photo and video management solution. - Issues · immich-app/immich

GeoffreyOP•4mo ago

message.txt

GeoffreyOP•4mo ago

yml file.

UPLOAD_LOCATION=/var/snap/docker/common/var-lib-docker/volumes/immich/_data
DB_DATA_LOCATION=./postgres
IMMICH_VERSION=release
DB_PASSWORD=immichportainer
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

UPLOAD_LOCATION=/var/snap/docker/common/var-lib-docker/volumes/immich/_data
DB_DATA_LOCATION=./postgres
IMMICH_VERSION=release
DB_PASSWORD=immichportainer
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

.env

Immich•4mo ago

Successfully submitted, a tag has been added to inform contributors. :white_check_mark:

GeoffreyOP•4mo ago

Haven't gotten a response. Hoping someone can help me out

Zeus•4mo ago

Your upload location doesn’t make any sense tbh You should mount the NFS on the host, then use that path Such as /mnt/immich

GeoffreyOP•4mo ago

I've mounted the NFS into portainer though, should that not do the same? The point was that I don't want to give my proxmox instance access to the NFS, only Immich.

GeoffreyOP•4mo ago

When I mount into Portainer as a volume, it tells me it's mounteded here. Which, is why I put that into the .env for Upload Location

Zeus•4mo ago

I’m not sure, This sounds like a Portainer specific question

GeoffreyOP•4mo ago

hmm mmk. I guess, aside from the Volume issue, it sounds like I'm putting it into the Immich .env right :/

Zeus•4mo ago

Yes , other than the fact that the path itself doesn’t make any sense to me haha If it’s a docker volume presumably it has a name, but I’m not sure how portainer handles those It wouldn’t be a path

GeoffreyOP•4mo ago

Well, thats encouraging that I'm not goofing up completely.

Zeus•4mo ago

Maybe it’s Immich-NFS. not sure

GeoffreyOP•4mo ago

Ya, I'm going to look at how to reference portainer volumes. That could very well be it. Confirmed the issue is Portainer Stacks don't allow for Volumes to be mounteded. Only through containers. The solution I am going to try is mounting the NFS directly to the Ubuntu server host within the /mnt/ folder, and then directing the Immich Stack to that instead.

GeoffreyOP•4mo ago

Going to drop this here for anyone else that stumbles into the same issue. The following worked for me, based on this comment from Reddit. https://www.reddit.com/r/portainer/comments/170vu05/comment/k3w0nzb/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

It is actually pretty easy:

Install NFS and connect the NAS to the OS (VM hosting docker):

    sudo apt install nfs-common

    sudo mkdir -p /mnt/somedir

    sudo mount 192.168.1.xxx:/volume1/somedir /mnt/somedir

    sudo nano /etc/fstab

    192.168.1.xxx:/volume1/somedir /mnt/somedir nfs defaults 0 0

Now you can use /mnt/somedir in your docker containers (as volumes) and the data will be stored in your NAS.

Also remember to enable NFS in DSM and allow the IP of the OS.

It is actually pretty easy:

Install NFS and connect the NAS to the OS (VM hosting docker):

    sudo apt install nfs-common

    sudo mkdir -p /mnt/somedir

    sudo mount 192.168.1.xxx:/volume1/somedir /mnt/somedir

    sudo nano /etc/fstab

    192.168.1.xxx:/volume1/somedir /mnt/somedir nfs defaults 0 0

Now you can use /mnt/somedir in your docker containers (as volumes) and the data will be stored in your NAS.

Also remember to enable NFS in DSM and allow the IP of the OS.

davidht0's comment on "Noob here: mounting NFS share from synology"

Explore this conversation and more from the portainer community

Gaming

Programming

Can't get my Upload Library to the right NFS share

Did you find this page helpful?