Move library and upload to NAS share
Hey everyone, trying to get this done. I changed the env for the immach-server containter but it still users the default path. What am I missing?
Env:
DB_DATABASE_NAME=immich
LIBRARY_LOCATION=/photostorage/_library
UPLOAD_LOCATION=/photostorage/_uploads
Volume:
host: /mnt/main/_photostorage
container: /photostorage
40 Replies
:wave: Hey @DasVekman,
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
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.We will really need more info. Please post your compose and env. What steps you actually performed and such.
it's the default yaml config. I only changed what I mentioned. Trying to get it to export now
What's the error the container is outputting? Did you move all the directories from their original location
no error, it doesn't follow the path I set. when I upload and then run the storage migration, the path is the default /data
Did your docker compose down, change, then up?
yes, I use portainer. I rebult the immich-server container after the change
You are using stack.env correct?
it was built using https://immich.app/docs/install/docker-compose/
I downloaded the .env file
my docker is pretty rusty, haven't used it since I went to proxmox and lxc containers
If you are using portainer you should see here: https://immich.app/docs/install/portainer
so I should remove it and redo it?
If you are just starting I would yes. You need to use
stack.env
in the compose and create a env section in the portainer ui.ty, I'll try that now
for the upload folder, it says absolute path. That's the path on the docker host?
or do I need to add a volume first?
Yes the path on the host
unable to upload file
š
Should check the error log and see what it says
[Nest] 18 - 08/25/2025, 5:55:31 PM ERROR [Api:AssetMediaService~hxz07j8j] Error uploading file Error: EPERM: operation not permitted, utime '/data/upload/f491743a-e9cf-42c3-b904-9a99eb8cea2e/b0/58/b058d3f9-9823-4a79-bd32-5ac05cc2e2a0.jpg'
permissions look ok, I can write to the folder that's mounted in the containter from the host
Still a permissions issue or an issue with the filesystem or network mount you're using
I have the mount point passed through from proxmox to the docker host, no issues creating files
I'm ready to give up š
Are you using bind mounts to the VM or using a virtual disk?
bind mount
Thats experimental, probably doesnt implement all features
mp0: /mnt/main,mp=/mnt/main
mp1: /mnt/backup,mp=/mnt/backup
mp2: /mnt/Volume-2,mp=/mnt/Volume-2
I can write files from the docker host
Idk im just telling you there are permission issues as in the log
yeah I can see that as well, I just don't know where the break is
Its not an immich issue, thats all i can really say
I had the same issue with the lxc container, even with full rights
Yep we specifically say not to use LXC
Whats the underlying filesystem?
ntfs over samba
Ntfs over samba then passed via proxmox?
Thats really not good
Ntfs is bad, and nested mounts are also very bad
proxmox connecting to samba share
bind mount to docker host
Yep, too many layers
can I just do direct to the samba share?
Sure you can do whatever you want in the VM
I tried to do symlinks in the lxc but it didn't work
@Zeus I got it somewhat working but the symlinks are not being followed in the container
nevermind, the permission issue is back
you can't run a storage template on an external drive right?
Yes you can
oh?
I didn't think that would work.
I will still need to get the upload folder moved to another share
Don't confuse external drive and external library
at this point, I just want it to work
I don't have enough space to keep the upload and library on the docker host, so I need to move them to the NAS
This thread has been closed. To re-open, use the button below.