The January 2024 source post is mostly an introduction and external tutorial link. It says BigBearCasaOS can install Immich—a self-hosted photo and video backup platform—on CasaOS, but the forum body does not preserve the full Compose definition, storage paths, database configuration, or image versions used in that video.
That means the safest long-lived page is not to reconstruct a two-year-old stack from memory. Preserve the historical source, then use the current Big Bear store and current Immich package definition for the actual installation.
This Is a Historical CasaOS Source
The post dates from January 2024 and belongs to the CasaOS category. CasaOS, ZimaOS, Big Bear, and Immich have all changed significantly since then.
Do not copy a 2024 image tag, port, or database layout into a current installation without checking the maintained package.
Big Bear Still Maintains Its Own App Store
The Big Bear CasaOS repository remains active and describes itself as an independently maintained app store for CasaOS and ZimaOS. It is not funded or operated as an IceWhale project, even though it is commonly available in the IceWhale ecosystem.
Review the current Big Bear app store before installing Immich.
Immich Is a Multi-Container Application
A real Immich deployment can include the main server, PostgreSQL, machine-learning service, and a Redis-compatible service such as Valkey. These services have different persistent-data requirements.
Moving only the photo folder while leaving the database and AppData on a small system disk can create a future capacity problem.
Plan Photo Storage Before the First Upload
The media library should live on the storage device intended to hold photos for years, not inside the disposable container layer. If the package exposes a host-side upload/library path, point that host side to the correct CasaOS storage before importing a large phone library.
Keep the container-side path exactly what the current package expects.
Protect PostgreSQL Separately from the Photo Files
Immich's database contains metadata that cannot be reconstructed perfectly from image files alone. A backup plan should therefore include both the photo library and the database/persistent app state.
A folder full of JPGs is valuable, but it is not a complete Immich restore point.
Machine-Learning Cache Is Another Storage Consumer
Facial recognition and search models can consume extra disk space through downloaded model files and caches. On small CasaOS system drives, this is another reason to check every service volume instead of only the upload folder.
Treat Major Immich Updates as Application Migrations
Immich moves quickly. Before updating a multi-container deployment, review release notes, back up database and media, and keep a copy of the current Compose/app definition. Do not assume every major release is a drop-in image-tag replacement.
If the Target System Is ZimaOS, Use a ZimaOS-Specific Immich Workflow
This source is CasaOS-specific. Current ZimaOS has its own App Store, storage controls, YAML editing, and Immich storage/migration guidance. Do not use the CasaOS tutorial as evidence that ZimaOS uses the same package layout today.
Immich on CasaOS FAQ
Does the original forum post preserve the full installation settings?
No. It mainly links to the external Big Bear tutorial.
Is Big Bear an IceWhale-owned app store?
No. The current repository states that it is independently maintained.
What should be backed up besides the photos?
The PostgreSQL database and other persistent Immich application state are also important.
