Immich•11mo ago

Problem with bind mount

I am running immich using portainer the compose file is unaltered:
_
volumes:

${UPLOADLOCATION}:/usr/src/app

The env table is
_
UPLOADLOCATION=/mnt/photos-immich

I get a series of these errors and the server cannot start:

[Nest] 7 - 01/27/2025, 8:36:43 PM ERROR [Microservices:StorageService] Failed to read upload/encoded-video/.immich: Error: ENOENT: no such file or directory, open 'upload/encoded-video/.immich'

The /mnt/photos-immich is mounted and being used by other containers in the same instance of portainer.

Any help would be appreciated.

Immich•1/28/25, 4:41 AM

:wave: Hey @Lutetium,

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
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
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•1/28/25, 4:41 AM

Checklist

I have...

:blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
:blue_square: read applicable release notes.
:blue_square: reviewed the FAQs for known issues.
:blue_square: reviewed Github for known issues.
:blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
:blue_square: uploaded the relevant information (see below).
: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
```
```
fdisk -l
```
and
```
df -h
```
```
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

/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

LutetiumOP•1/28/25, 8:35 PM

Im using the default docker compose file, the only modification to the env file is the UPLOAD location - the error included it the error stopping the server from running, if the UPLOAD location is set back to "./Library" everything works fine. I can see the mnt/photos-immich file fine on the host and that location is working fine for other containers on the same server. Ive tried moving the location of the mount and renaming to see if there were any issues - i just cannot get immach to see that location at all

Mraedis•1/28/25, 8:37 PM

${UPLOAD_LOCATION}:/usr/src/app/upload

${UPLOAD_LOCATION}:/usr/src/app/upload

is the correct form

Mraedis•1/28/25, 8:37 PM

you can't just willy nilly rename that

Mraedis•1/28/25, 8:38 PM

"If the UPLOAD location is set back to "./Library" everything works fine"

Mraedis•1/28/25, 8:39 PM

If you want to change the upload location then you need to

cp -a

cp -a

the folders to the new location, or start fresh

Mraedis•1/28/25, 8:39 PM

You can't change it after initial startup

Mraedis•1/28/25, 8:39 PM

(without also moving the files)

LutetiumOP•1/28/25, 8:47 PM

i blow the containers away, delete the volumes, change the env file, pull new images and start all the containers. Is that not how to do this?

Mraedis•1/28/25, 8:49 PM

Sure but you still need to use

${UPLOAD_LOCATION}:/usr/src/app/upload

${UPLOAD_LOCATION}:/usr/src/app/upload

LutetiumOP•1/28/25, 8:50 PM

yes - that hasnt changed at all - im using the default compose file

Zeus•1/28/25, 8:50 PM

Please post your full compose and env

Mraedis•1/28/25, 8:51 PM

Did you blast the database folder as well?

Mraedis•1/28/25, 8:51 PM

because it's neither a container nor a volume

LutetiumOP•1/28/25, 8:52 PM

Hmmm - I am not sure then - I get rid of the volumes, destroy the containers and delete the images. Is that not destroying the database?

Mraedis•1/28/25, 8:53 PM

LutetiumOP•1/28/25, 8:53 PM

Is the database on the host?

Mraedis•1/28/25, 8:53 PM

Yes

Mraedis•1/28/25, 8:53 PM

DB_DATA_LOCATION

LutetiumOP•1/28/25, 8:54 PM

Wow - ok thanks - ill take a look - i thought that was part of a volume?

Mraedis•1/28/25, 8:54 PM

No, the . in

./library

./library

and

./database

./database

is "current folder" so it's wherever the compose file is

LutetiumOP•1/28/25, 9:00 PM

You just saved me weeks of frustration! Thank you so much!

Mraedis•1/28/25, 9:01 PM

Always happy to help

LutetiumOP•1/28/25, 9:02 PM

Its the only container that I use that does this. For anyone who may have this issue - since i am using portainer - the files that need to be deleted for a complete reset are under /data/compose/. There is a folder in there (mine was called "15") that will need top be deleted.

Mraedis•1/28/25, 9:05 PM

It's because the other containers you use don't care about the data

Mraedis•1/28/25, 9:06 PM

If they were in volumes you are one

docker compose down -v

docker compose down -v

away from deleting everything ever

SolarCzar•1/30/25, 9:12 PM

I'm glad I found this, as I've been fighting the same problem for a couple of weeks

SolarCzar•1/30/25, 10:02 PM

So here's a question...why is it when I have a working container. If I upgrade to the next version of immich, I can't simply stop the stack, repull the image, and restart? I get these Nest errors and it can't find the database.

Or mildly...what is the right way to upgrade the stack from within Portainer?

Mraedis•1/30/25, 10:08 PM

I just force recreate from portainer

Mraedis•1/30/25, 10:08 PM

What is your compose/env?

SolarCzar•1/30/25, 10:19 PM

it's just the standard one off the Immich website. The only difference I made to it was to add a volume pointing to my pictures folder....

/home/solarczar/Pictures:/mnt/old_photos

env...

UPLOAD_LOCATION=/home/solarczar/Pictures/rev_011625
DB_DATA_LOCATION=/home/solarczar/immich_dbase
IMMICH_VERSION=release
DB_PASSWORD=password
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Early days of Immich, I'd just stop the stack, update the stack - selecting re-pull the image, and all was good. Now if I do that, I get Nest errors, delete the stack, delete the DB, and restart, reload all my pics.

SolarCzar•1/30/25, 10:20 PM

I'm looking through the /data/compose folder and not sure which one is to be deleted on my side. Do the numbers reference a tie back

bo0tzz•1/30/25, 10:20 PM

Are you mounting that whole folder as an external library?

Mraedis•1/30/25, 10:21 PM

Looks like you have nested mounts which is always a bad, bad, bad idea

Bbo0tzz Are you mounting that whole folder as an external library?

SolarCzar•1/30/25, 10:22 PM

I guess that's the right definition. I had trouble pointing Immich at the files downloaded from Google Photos. This is the direction I landed after much confusion

MMraedis Looks like you have nested mounts which is always a bad, *bad,* **bad** idea

SolarCzar•1/30/25, 10:22 PM

Ok, I don't know what that means exactly, but happy to read up

Mraedis•1/30/25, 10:23 PM

This directory:

UPLOAD_LOCATION=/home/solarczar/Pictures/rev_011625

UPLOAD_LOCATION=/home/solarczar/Pictures/rev_011625

is inside of this directory:

/home/solarczar/Pictures:/mnt/old_photos

/home/solarczar/Pictures:/mnt/old_photos

Mraedis•1/30/25, 10:23 PM

You can't do that

Mraedis•1/30/25, 10:23 PM

And also not the other way around

SolarCzar•1/30/25, 10:23 PM

Ahh, didn't know that

Mraedis•1/30/25, 10:23 PM

imagine you create a new thumbnail

Mraedis•1/30/25, 10:23 PM

It goes in

/home/solarczar/Pictures/rev_011625

/home/solarczar/Pictures/rev_011625

Mraedis•1/30/25, 10:24 PM

external library sees a new picture!

Mraedis•1/30/25, 10:24 PM

it creates a new thumbnail

Mraedis•1/30/25, 10:24 PM

it goes in

/home/solarczar/Pictures/rev_011625

/home/solarczar/Pictures/rev_011625

Mraedis•1/30/25, 10:24 PM

You get the idea.

SolarCzar•1/30/25, 10:24 PM

Yes I do. thanks.

MMraedis imagine you create a new thumbnail

SolarCzar•2/5/25, 5:13 PM

Thanks for the assist...I'm running smooth as glass now.

Problem with bind mount

References

Checklist

Information

Similar Threads

Similar Threads

References

Checklist

Information

Similar Threads