documentation - in custom-locations guide - note .immich folder requirement #5447

Closed
opened 2026-02-05 11:28:06 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @Aevaris on GitHub (Feb 23, 2025).

The bug

Hi, unsure if documentation 'bugs' get logged here, apologies if not.

Background
I spent awhile trying to migrate from a centralized storage strategy to splitting where my metadata goes vs source data. I followed the custom-locations guide:
https://immich.app/docs/guides/custom-locations

Goal
My plan was to have Immich rebuild the metadata (encoded videos and thumbnails) knowing that regeneration was going to be faster than copying.

Issue
I found Immich wouldnt boot with issues that looked like permissions. After awhile (longer than I want to admit), I identified that the hidden .immich folder needed to exist to boot. This makes sense in retrospect (and is a neat safety feature), but based on the documentation I didn't know it existed.

Fix Recommendation:
In the custom-locations guide, add a note that if you're migrating to custom locations, you will need to either copy the previous directory prior to composing up or at a minimum create/move the .immich directory.

The OS that Immich Server is running on

Ubuntu

Version of Immich Server

1.126.1

Version of Immich Mobile App

N/A

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

N/A

Your .env content

N/A

Reproduction steps

Described above

Relevant log output


Additional information

No response

Originally created by @Aevaris on GitHub (Feb 23, 2025). ### The bug Hi, unsure if documentation 'bugs' get logged here, apologies if not. **Background** I spent awhile trying to migrate from a centralized storage strategy to splitting where my metadata goes vs source data. I followed the custom-locations guide: https://immich.app/docs/guides/custom-locations **Goal** My plan was to have Immich rebuild the metadata (encoded videos and thumbnails) knowing that regeneration was going to be faster than copying. **Issue** I found Immich wouldnt boot with issues that looked like permissions. After awhile (longer than I want to admit), I identified that the hidden .immich folder needed to exist to boot. This makes sense in retrospect (and is a neat safety feature), but based on the documentation I didn't know it existed. **Fix Recommendation:** In the custom-locations guide, add a note that if you're migrating to custom locations, you will need to either copy the previous directory prior to composing up or at a minimum create/move the .immich directory. ### The OS that Immich Server is running on Ubuntu ### Version of Immich Server 1.126.1 ### Version of Immich Mobile App N/A ### Platform with the issue - [x] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML N/A ``` ### Your .env content ```Shell N/A ``` ### Reproduction steps Described above ### Relevant log output ```shell ``` ### Additional information _No response_
Author
Owner

@bo0tzz commented on GitHub (Feb 23, 2025):

That note is already added but not yet released. You can see it in the preview for the main branch: https://main.preview.immich.app/docs/guides/custom-locations/

@bo0tzz commented on GitHub (Feb 23, 2025): That note is already added but not yet released. You can see it in the preview for the main branch: https://main.preview.immich.app/docs/guides/custom-locations/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#5447