this post was submitted on 23 Jan 2024
8 points (100.0% liked)

Docker

1091 readers
1 users here now

founded 1 year ago
MODERATORS
 

I just installed Immich and while all my other containers have just required me to add to them to existing yaml, Immich requires its own yaml. That's fine I guess, but for the library, I wanna host it on my NAS and so I made the volume in my main Docker-Compose.yaml, the Immich yaml was all like, "what you talking about Willis?" because in my Immich environment I tried to point to something created in my main yaml. I thought I could work around this by adding an empty volume declaration, but now I can't find my uploads ๐Ÿ˜‚ any idea on the correct methodology/workaround?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 9 months ago* (last edited 9 months ago)

Use a shared on-disk volume mount, i.e.:

volumes:
  - /data/docker/stuff:/whatever

In both compose files.

I use a similar mechanism to enable my media acquisition stack to grab completed files and store them in their permanent location.

Edit: you can just use the same volume in both containers at the same time, but you'd typically use an NFS mount or something if / when you try and scale this out. You probably just got the volume definition a little off (or need to create it outside both containers definitions and use it there)