this post was submitted on 08 Jul 2025
94 points (97.0% liked)

Selfhosted

49240 readers
639 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
94
PSA: If the first Smart Search in Immich takes a while (lemmy.ca)
submitted 1 day ago* (last edited 1 day ago) by avidamoeba@lemmy.ca to c/selfhosted@lemmy.world
38 comments fedilink hide all child comments
 

Your ML model cache volume is getting blown up during restart and the model is being re-downloaded during the first search post-restart. Either set it to a path somewhere on your storage, or ensure you're not blowing up the dynamic volume upon restart.

In my case I changed this:

  immich-machine-learning:
    ...
    volumes:
      - model-cache:/cache

To that:

  immich-machine-learning:
    ...
    volumes:
      - ./cache:/cache

I no longer have to wait uncomfortably long when I'm trying to show off Smart Search to a friend, or just need a meme pronto.

That'll be all.

you are viewing a single comment's thread
view the rest of the comments
[–] wabasso@lemmy.ca 3 points 1 day ago (1 children)

Ok I should know this by now, but what actually is the current “./“ directory when you use that? Is it the docker daemons start dir like /var/docker ?

[–] mhzawadi@lemmy.horwood.cloud 6 points 1 day ago (2 children)

./ will be the directory you run your compose from

[–] elmicha@feddit.org 1 points 16 hours ago

I'm almost sure that ./ is the directory of the compose.yaml.

Normally I just run docker compose up -d in the project directory, but I could run docker compose up -d -f /somewhere/compose.yaml from another directory, and then the ./ would be /somewhere, and not the directory where I started the command.

[–] SheeEttin@lemmy.zip 0 points 1 day ago (3 children)

That seems like a bad idea

[–] MangoPenguin@piefed.social 8 points 1 day ago (1 children)

Its convenient because your data is stored in the same folder that your docker-compose.yaml file is in, making backups or migrations simpler.

[–] avidamoeba@lemmy.ca 2 points 21 hours ago

Yup. Everything is in one place and there's no hardcoded paths outside of the work dir making it trivial to move across storage or even machines.

[–] ohshit604@sh.itjust.works 4 points 20 hours ago* (last edited 20 hours ago) (1 children)

As other stated it’s not a bad way of managing volumes. In my scenario I store all volumes in a /config folder.

For example on my SearXNG instance I have a volume like such:

services:
  searxng:
    …
    volumes:
      - ./config/searx:/etc/searxng:rw

This makes the files for SearXNG two folders away. I also store these in the /home/YourUser directory so docker avoids using sudoers access whenever possible.

[–] SheeEttin@lemmy.zip 1 points 18 hours ago (1 children)

So why would you not write out the full path? I frequently rerun compose commands from various places, if I'm troubleshooting an issue.

[–] ohshit604@sh.itjust.works 3 points 17 hours ago* (last edited 17 hours ago) (1 children)

So why would you not write out the full path?

The other day my raspberry pi decided it didn’t want to boot up, I guess it didn’t like being hosted on an SD card anymore, so I backed up my compose folder and reinstalled Rasp Pi OS under a different username than my last install.

If I specified the full path on every container it would be annoying to have to redo them if I decided I want to move to another directory/drive or change my username.

[–] SheeEttin@lemmy.zip 1 points 17 hours ago

I'd just do it with a simple search and replace. Have done. I feel like relative paths leave too much room for human error.