the docker compose files do not integrate well with your pre-existing docker compose setup #13842
Replies: 3 comments
-
Docker is designed to have a separate docker-compose.yml per service/stack. While I run my services "aggregated" like yours, if you are not confident in Docker setup, it's best to segregate them like designed. |
Beta Was this translation helpful? Give feedback.
-
ok thanks I will try that implementation instead. |
Beta Was this translation helpful? Give feedback.
-
Since you've renamed the
I personally then just made sure every immich container had the model-cache mounted in their respect volumes section by adding |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The bug
The included docker compose files are too complicated and are configured as if they are the only docker compose files you are going to be running on our system. For example, they make use of a
.env
file with extremely common variables such asDB_PASSWORD
,DB_USERNAME
, and the services in the docker-compose.yml file have overly generic service names such as "database", "redis", and the volume is labeled "model-cache".It does not seem like its possible to use this at all if you already have a pretty hefty stack of other docker compose YAML files and services in your current docker compose configuration. For example, I already have multiple docker compose services that utilize databases, so a service from Immich labeled as
database
is not acceptable for use. Neither is a .env value ofDB_PASSWORD
since I already have other database passwords.I made an attempt at trying to re-write the docker compose YAML from the latest release in a fashion that might work and be merged in with my current existing docker compose setup, however, it just ended up breaking everything. Keep in mind that in docker compose, you can only have a single
.env
file, so this means that if you have pre-existing configurations, you have no choice but to re-write the entire Immich docker compose setup in order to not have conflicts. Which is a pretty big blocker to usability.This is something that I have only ever experienced with Immich. Other services were all pretty easy to add to my existing docker compose setup, for example you can see a ton of services available here https://docs.linuxserver.io/images/docker-flexget/ all with docker compose YAML's that dont need to be completely re-written to make them work with your existing docker compose stack.
The OS that Immich Server is running on
Debian GNU/Linux 12 (bookworm)
Version of Immich Server
release
Version of Immich Mobile App
none
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
docker compose up -d
immich-server
is broken and does not workRelevant log output
Beta Was this translation helpful? Give feedback.
All reactions