Error: ENOENT: no such file or directory, open 'upload/encoded-video/.immich'
- Strange, using docker on windows.
-Upgraded to 1.25.7 a few days ago. No problem.
- Today after a system restart I started getting the folder check error.
- None of my paths have changed.
- Sure enough, /usr/src/app/upload is empty on the container (image 2)
- IDK what to do with my docker-compose.yml (attached). My .env is the same,
Any tips on figuring out what's going wrong? I don't really know what could have changed on my end. All my other docker containers and volumes are fine. These are also on the same drive as UPLOAD_LOCATION in .env.
Would appreciate any help, thank you!
6 Replies
:wave: Hey @warpstone!,
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. :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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Hi sorry, also tried creating a new instance pointing to upload with a new pgdata folder. This allowed Immich to startup with a new db. Then restarted with the old DB and unfortunately no luck. Every image link is broken, including the admin account avatar.
I'm mystified because I feel like it must be a simple string issue but I can't put my finger on it.
I have backups of the pre-failure postgres and upload directory. I've tried creating new instances with .env and docker-compose variations but either a) Immich dies on launch as original failure or b) loads with the old DB but can't see any media. For (b), would it help to exec into the container to see if the mount is behaving as expected?
Aah, nothing is mounting. Not even the external libraries:
All of this worked last week 🤔
Weird. I think I fixed it. Was not immich but rather docker itself. The WSL disk image file under
C:\Users\username\AppData\Local\Docker\wsl\disk had ballooned to 250+gb
I purged it, restarted docker and surprisingly everything works with the original DB + upload directory.
I wish I had a better explanation that docker weirdness, sorry. Will monitor this week and close if everything survives. Hopefully this helps someone else who gets similarly stumped but what looks like a file integrity issue that isn't Immich's fault
If you update and never purge old images docker storage will balloon massively over time