The current docker-compose.yaml included in the project will put all expensive data in the container's writable layer which gets destroyed when the container is reconfigured or rebuilt. So I tried to find a setup that persists expensive-to-create data outside
A container configured as follows won't start up since you cannot have docker create files. 0-byte files won't be accepted by the app (for e.g. faiss_index.bin).
The current docker-compose.yaml included in the project will put all expensive data in the container's writable layer which gets destroyed when the container is reconfigured or rebuilt. So I tried to find a setup that persists expensive-to-create data outside
A container configured as follows won't start up since you cannot have docker create files. 0-byte files won't be accepted by the app (for e.g.
faiss_index.bin
).The solution is to put all permanent data files currently in
/immich_duplicate_finder
in a directory and have a single bind-mount.